I am finding that in trying to use ddrescue, the source disk will
eventually get into a state where the machine it's in needs to be
restarted (hard -- with a full power-down/up).

But when the disk gets into this state while ddrescue is running it
continues to try to read from the disk and fails.  Presumably all of
the blocks it tried to read while the disk was in this needing-a-reset
state are being flagged as bad.

Is my understanding correct about this?

But maybe those blocks that were attempted after the disk got fubar'd
(and the machine needed a power down/up) are not bad.  Maybe once the
disk is reset they would be readable.

What is the best way to handle this situation so that those potentially
readable blocks are actually re-attempted after the machine is


Reply via email to