Hi, * Veek M [Thu Dec 21, 2017 at 03:45:15PM +0530]:
> This is important. My disk had crashed and about 132KB of sectors were > damaged: > http://pix.toile-libre.org/upload/original/1513821694.png > I decided to recover my data, partition by partition sdc4, sdc3, sdc2, etc > I passed the ddrescue_log file as an option, every time I ran the command. > Then I decided to RMA the disk and ran this command > ddrescue --fill-mode=+ --force /dev/zero /dev/sdc ddrescue_GNU.log > It finished almost immediately - it did not register in my head at that > moment, that the disk was > substantially NOT ERASED. If you look at the log file IMAGE you see why. > While recovering my data - at some point, probably for sdc1, I must have > interrupter the program. > Then when I tried to zero the entire disk it just used the 'faulty' log and > blanked out a portion > assuming that's what I wanted. > The log appears to be not cummulative across runs - ddrescue needs some > mechanism for either > informing the user when it fails to blank the entire disk. Do you have the output of the ddrescue command line (and its execution) available? Can you attach the ddrescue_GNU.log to the bug report? And did you check the exit code of the ddrescue process? regards, -mika-
signature.asc
Description: Digital signature
