i have a WD 40gb HDD that ive been using for about a month now with no problems
the other day i started WinME up and it tried to run WinME scandisk. part way through the scandisk I got a blue screen that said something like:
Could not write to C:
Data or Files may be lost
this was concerning because I rarely use that computer and nothing had changed from the last time it worked fine,
everytime i tried to restart it gave me the same result
so i determined that something may be corrupted on drive (i dont know much about HDDs), and thought a format might be the best way to go
on this restart, i noticed that S.M.A.R.T. in the bios boot up said the drive was something along the lines of: Capable but not responding to command
i had never seen this report before from the drive (although i never specifically looked before so it may or may not have been happening before)
already suspicious now of the integrity of the drive, i did a format c: in dos. it got through the long format process, but choked as soon as it tried to create the FAT
now i was convinced that the drive was bad, but not eager to go through a return process, I downloaded the latest set of diagnostics from WD's website (Data Lifeguard Tools 2.8)
on this next restart, S.M.A.R.T. reported the drive as Capable and Status OK. i then ran all 3 tests supplied by WD (Quick Test which takes 90 seconds, Extended Test which takes about 20 mins, and then finally the Write to 0's test which destroys all data on the HDD and takes about 4 hours). all the tests came up negative. perplexed now, I formatted the HDD with the WD tools with no problem, and am now installing WinME again
im still worried about this drive though. any comments? what would u do with this drive?
someone said it could be the cable (which is ata100), and that is one thing that changed between errors and no errors - not the cable, but i removed the drive from it cage to visually inspect it, and its now just lying on top of the computer, so the positioning of the cable has changed. this however, seems to be an unlikely cause of the problem, even though as i said i know little about HDDs and their cables
UPDATE: see latest post at bottom
the other day i started WinME up and it tried to run WinME scandisk. part way through the scandisk I got a blue screen that said something like:
Could not write to C:
Data or Files may be lost
this was concerning because I rarely use that computer and nothing had changed from the last time it worked fine,
everytime i tried to restart it gave me the same result
so i determined that something may be corrupted on drive (i dont know much about HDDs), and thought a format might be the best way to go
on this restart, i noticed that S.M.A.R.T. in the bios boot up said the drive was something along the lines of: Capable but not responding to command
i had never seen this report before from the drive (although i never specifically looked before so it may or may not have been happening before)
already suspicious now of the integrity of the drive, i did a format c: in dos. it got through the long format process, but choked as soon as it tried to create the FAT
now i was convinced that the drive was bad, but not eager to go through a return process, I downloaded the latest set of diagnostics from WD's website (Data Lifeguard Tools 2.8)
on this next restart, S.M.A.R.T. reported the drive as Capable and Status OK. i then ran all 3 tests supplied by WD (Quick Test which takes 90 seconds, Extended Test which takes about 20 mins, and then finally the Write to 0's test which destroys all data on the HDD and takes about 4 hours). all the tests came up negative. perplexed now, I formatted the HDD with the WD tools with no problem, and am now installing WinME again
im still worried about this drive though. any comments? what would u do with this drive?
someone said it could be the cable (which is ata100), and that is one thing that changed between errors and no errors - not the cable, but i removed the drive from it cage to visually inspect it, and its now just lying on top of the computer, so the positioning of the cable has changed. this however, seems to be an unlikely cause of the problem, even though as i said i know little about HDDs and their cables
UPDATE: see latest post at bottom