[SOLVED] [squeeze]Log of old dd_rescue (1.14): success?

Weapon S · 11-15-2013, 09:33 AM

It seems the version of dd_rescue in old-stable is not so well documented.
I ran dd_rescue to clone a failing disk to a file, but when I returned the PC crashed. Now I'm not sure which options I used (i.e. sparse file) and whether it matters. If the log shows that it finished before it crashed, the options are of no concern.
The produced log differs greatly from what I read in the current manual.

Code:

dd_rescue: (info): ipos:  30028224.0k, opos:  30028224.0k, xferd:  30028224.0k
                   errs:      0, errxfer:         0.0k, succxfer:  24293184.0k
             +curr.rate:    11362kB/s, avg.rate:    11475kB/s, avg.load:  9.4%
dd_rescue: (info): /dev/sda (30028271.5k): EOF
Summary for /dev/sda -> /media/HUGE/T/dd_linux_fail_system.bin:
dd_rescue: (info): ipos:  30028271.5k, opos:  30028271.5k, xferd:  30028271.5k
                   errs:      0, errxfer:         0.0k, succxfer:  24293184.0k
             +curr.rate:   181298kB/s, avg.rate:    11475kB/s, avg.load:  9.4%

Does this log show a succesful copy? If not, can I resume data extraction using this log?

unSpawn · 11-16-2013, 03:56 AM

Quote:

Originally Posted by Weapon S

Does this log show a succesful copy?

Yes because "xferd" equals "ipos". It just didn't copy everything. What's more is you can always verify the result by comparing the hash of the source and destination. Should a hash incidentally not match then it's good to know there's the md5deep (sha1deep, etc.) tools which help you figure out at which point a file differs (use piece-wise mode and set the size to a relevant block size).

Weapon S · 11-16-2013, 11:06 PM

Thanks for that explanation and extra info.
I reran dd_rescue succesfully and got a similar resulting log (and a identical disk image). Thereafter writing out to the final destination, it did go as far as the 30GB. I assume the difference in size is due to the sparse file.