Hello everyone,
I have a 1.5 year old Samsung HD 153 WI that I bought second-hand half a year ago. In spite of it being an internal hard drive I used it as an external storage unit (inside a casing). A month ago I accidentaly dropped the drive in it's casing, from a small height (the height of the PC tower on which it stood). The drive wasn't operating at the moment, and when I switched my PC back on it continued to work flawlessly (I've successfully added and read a number of files).
Fast forward to a day before yesterday... while deleting some data, there was a directory that couldn't be erased as Windows kept complaining that it wasn't empty. So I run chkdsk /f and got first 8 KBs of bad sectors . After that I could proceed with deleting the directory. But a thought kept nagging at me so I did a chkdsk /b to rescan the entire drive for bad sectors... and that operation never completed as it got stuck at some point.
Unfortunetaly that was probably my last chance to back up the files as tomorrow they were all unreadable (perhaps due to broken indexes from an incomplete CHKDSK operation). What's more I cannot reformat the disk or zero-fill it as it gets stuck at around 15th gigabyte reporting more than 2048 bad sectors. After some experimentation I created an empty partition to take up the first 250 GBs of space and then proceeded to zero fill from there, this operation is still running and it seems that this will complete okay.
So it seems I have two options, I could RMA the drive or I could perhaps keep it and use it from the 250th gigabyte onward, knowing full well that it is probably unreliable. I don't feel completely okay about RMAing the drive as it well be my fault - the drive WAS dropped, after all, albeit a month ago.
Does this description sound like what usually happens with dropped drives, or does it perhaps sound more like an spontaneous failure?
I have a 1.5 year old Samsung HD 153 WI that I bought second-hand half a year ago. In spite of it being an internal hard drive I used it as an external storage unit (inside a casing). A month ago I accidentaly dropped the drive in it's casing, from a small height (the height of the PC tower on which it stood). The drive wasn't operating at the moment, and when I switched my PC back on it continued to work flawlessly (I've successfully added and read a number of files).
Fast forward to a day before yesterday... while deleting some data, there was a directory that couldn't be erased as Windows kept complaining that it wasn't empty. So I run chkdsk /f and got first 8 KBs of bad sectors . After that I could proceed with deleting the directory. But a thought kept nagging at me so I did a chkdsk /b to rescan the entire drive for bad sectors... and that operation never completed as it got stuck at some point.
Unfortunetaly that was probably my last chance to back up the files as tomorrow they were all unreadable (perhaps due to broken indexes from an incomplete CHKDSK operation). What's more I cannot reformat the disk or zero-fill it as it gets stuck at around 15th gigabyte reporting more than 2048 bad sectors. After some experimentation I created an empty partition to take up the first 250 GBs of space and then proceeded to zero fill from there, this operation is still running and it seems that this will complete okay.
So it seems I have two options, I could RMA the drive or I could perhaps keep it and use it from the 250th gigabyte onward, knowing full well that it is probably unreliable. I don't feel completely okay about RMAing the drive as it well be my fault - the drive WAS dropped, after all, albeit a month ago.
Does this description sound like what usually happens with dropped drives, or does it perhaps sound more like an spontaneous failure?