Strange Screws

So either you have a pathetically inadequate
small sample or you are killing all your drives.

So you obviously should refrain from commen-
ting as if you are the resident expert on this.

As if that can't happen to IDE drives.

In your case.
You are known as a 'pathetically inadequate sample'.

 

Interesting but the drive is running on borrowed time. Perhaps you
should store all your critical data on it and see how long it continues
to operate like that.

 

Strange how you have no such concerns with risking your data on a new drive
without checking your powersupply/supply of power first.

 

The exact same thing happened to me. I was copying stuff off one of my old
Seagate HDD, and there is one file that XP can't read, saying ECC error. I
ran Seatools <http://www.seagate.com/support/seatools/> on the drive and it
identified 2 bad sectors with full diagnostic. I was able to get the file
off the drive by having Seatools force a remapping of the bad sectors.

The remapped sectors are zeroed, so you're getting the file damaged, but it
is better than not getting anything at all. The good thing is Seatools
tries to identify and tell you which file is affected (although in short 8.3
name only), so you can decide if you want to risk it or not.

As for whether it will get worse, it depends on what caused the error. If
it was just a transient glitch that caused the drive to make a bad write, it
could be that it will develop no more error afterwards. If, say, the drive
electronics is failing, you'll see more and more bad sectors (thus more
clicking when you access previously-okay files). HDDs are cheap enough
nowadays that I wouldn't risk my data on such a drive, but YMMV.

Stephen