bruce
Joined: 13 Jan 2010
Perth, Western Australia | | Hi all.
I'm attempting to recover a 130MB database file from a failing hard disk drive. Unstoppable copied the first 96 MB in no time flat, but after that ran into (presumably) bad sectors.
For each 512 bytes after the first 96 MB, it takes a long time, and eventually racks up a read error, and the total corrupt bytes copied goes up by one. So far it's being going for nearly 24 hours and it's taken that long to get through 1.08MB (I have the reliability slider set to "best data recovery").
So my questions:
1) What exactly is a Read Error? Does this mean that Unstoppable tried to copy the sector many, many times with no success? When a read error happens, does it just write zeroes into the output file? Or does it does it do some kind of "best guess" based on the many failed reads from the bad sector?
2) Should I allow this copy to continue, or stop it and try again with some different settings? In the worst case, if the copy speed stays like this for the rest of the file, I'll be waiting for about a month...
Thank you! |
|
