On 02/12/2014 12:19 AM, Felix Miata wrote:
I seem to have a failing STB HD, a "refurb" Samsung HD155UI relabeled as Seagate ST1500DL004 Barracuda Green, bought 11 months ago. Log from latest rsync retry: http://fm.no-ip.com/Tmp/Hardware/Disk/rsync0211d.txt
I didn't know in advance of any problem, but started out making a backup to freshly formatted and partitioned newer HD. Yesterday I mistakenly made the target partition too small and it filled up before completing. In that process only one file, the smallest of the three now failing, failed to copy. For it I had no log made.
After repartitioning/reformatting I redid the rsync, and found 3 instead of 1 failed file, 7.7 hours later. http://fm.no-ip.com/Tmp/Hardware/Disk/rsync0211b.txt
I retried after a couple of hours idle time with no apparent difference. http://fm.no-ip.com/Tmp/Hardware/Disk/rsync0211c.txt
Latest try I did after shutdown and putting the failing HD in front of a fan long enough to bring it thoroughly down to room temperature. I now have it in a plastic baggie in the freezer.
What should I try next? Another rsync right after removing HD from freezer? Ddrescue right after removing from freezer? Ddrescue after letting HD return to room temp?
Anyone here familiar with ddrescue know what I should expect of it? Suggestions?
I'd suggest looking for a program that allows you to control its reaction to I/O errors that occur during read operations on failed disks. Various ddrescue (and other *rescue) programs are meant mainly for rescuing deleted or otherwise lost data -- they are very useful in carving artifacts of lost files and try to recover them into whole files. They act as a sort of digital forensic tools. Using them on damaged disks might help but is very likely to make even more damage. If they encounter any I/O errors, they go to a loop of retries, which is OK on a sane disk, but not on a damaged one. On damaged disk you need as little retries as possible. The best is to copy everything that can be copied without retries first and then to repeat copying incomplete files with increased number of retries, etc. It might surprise you, but simple xcopy command in Windows might be of good help. Check this link: http://djlab.com/2010/12/windows-ignore-errors-with-xcopy-and-robocopy/ HTH R.Soskic -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org