One thing I've noticed with almost all drives that I copy from old
machines is that frequently there are zones where the bitrate drops notably but
doesn't get classed as an error in ddrescue ( which is fine ). Would it be
possible to add a feature to ddrescue that lets you mark such zones in a log -
or, more generically, log the whole copy process to another file for later
review/examination?
I admit that I've already kludged a copy of 1.16 to dump the verbose
info to stderr so I can then capture to a logfile. I've also looked at the -a
option but it seems that it invariably triggers on the start of the ddrescue
process for some reason (ie, if I do ddrescue -v -f /dev/sda /dev/null on a
USB3 device it'll start with a low read rate for the first second and thus
it'll trip almost immediately with the -a option.
I appologise if this is completely outside of the scope of ddrescue, as
I agree I'm trying to turn it into a bit of a 'disk testing' tool in this
instance.
Regards,
Paul.
--
PLDaniels - http://pldaniels.com
Computer Repairs for Charters towers - http://ctpc.biz
PGP Public Key - http://pldaniels.com/gpg-keys.pld
A.B.N. 19 500 721 806
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
