On Wed, Jul 15, 2009 at 12:26 PM, Antonio Diaz Diaz
<address@hidden> wrote:
James Watts wrote:
I am currently rescuing a 500GB drive. When I first started ddrescue, the
routine began recovering data at the blistering rate of 18-20 MB/s. Then it
encountered an error (after recovering about 20GB) and the drive got hung-up
and did not respond to commands. So I had to turn off the drive, turn it on
again, and restart ddrescue. Now, it's been going for two days holding at a
rate of 300-500 KB/s. It has not encountered any more errors according to
the on-screen info and the log (see below). So why will it not ramp up to
the high-speed from before? At this rate, it could take weeks to complete.
Did you only reset the drive (/dev/sdb) instead of rebooting the whole computer? Maybe the controller or even the kernel switched to a slower mode after the error.
Thoughts? Am I doing something wrong? What would you do differently?
If the reboot doesn't work, I would try to stop ddrescue and restart it at the next multiple of 64KiB. (The next position with four trailing zeros: 0xD2C290600 ==> 0xD2C2A0000).
Regards,
Antonio.