#SDNY he's all yours. -- Michael Steele 5110 Posts 3/03
Posted - Sep 9 2014 : 8:10PM
I haven't tried to. If for some reason it doesn't work, I would suggest going to the website of the drive manufacturer and downloading whatever diagnostic utility program they provide.
checkdisk (if you mean the windows tool) does a check on the file system, not on the disc. Which means if you have garbled up file system structures, the chkdsk will help. If there are errors on the hard disk (corrupt sectors, which don't affect the file system structures), chkdsk won't complain. Tools from hard disk manufacturers OTOH test for errors on the file system, but probably won't be of much help for damaged file system structures. Chkdsk will create files in your %temp% directory while it is running, it could well be that somehow it runs out of space when checking such a large device. BTW: you can also run chkdsk with the /r parameter, then it checks for faulty sectors (just as the manufacturer's tools would do). But I guess if chkdsk doesn't even go through the normal test, it won't perform the other test, either. You should try making sure there is enough space in your %temp% before running chkdsk.
you are correct with everything you say but the problem is ... the drive "kinda" falls asleep. The external housing has a blue LED and after some time it will goto "sleep" mode and the CMD window ... in which chkdsk is running ... stops working. I then found a tool that is supposed to dis-able "Sleepmode" but the problem still persists. And i guess i´m right with checking for filesystem errors befor going to surface checking tasks Cube
^ in that case, (if you have a normal computer, not a laptop), you might want to try to remove the hard disk from the USB enclosure and put it directly into your computer via S-ATA. This way, the power management should work differently. At work, I have some enclosures who always shut down the hard disks after a certain time, something that never happens when the disk is connected directly to the mainboard. Don't know about E-SATA, though. Power management could be similar to that of USB.
So that's completely independent from the O/S? I.e. it overrides the O/S control regardless of what you may have it set to? If so--that blows. That seems like a "feature" that creates problems instead of solving them (like upper-management).
I'm not sure about that, but I could not yet find an option to change the timeout when the operating system would shut the device down. So I don't know if the device respects such settings or not...