Hello Wolfgang,
[EMAIL PROTECTED] wrote:
I tried to save a partition /dev/hda1 into a file /media/hdb1/imagefile.
Logfile is also there /media/hdb1/logfile. This worked fine until the error in
the 25 GByte Parition at nearly 9GByte. At the error of course the data
transferrate broke down from about 8 MByte/s to 35 kByte/s. Thats ok. A
long time I was waiting for the transferrate to increase again, because there
are no more errors in the partition as far as I know. But after 4 hours and
about 0,5 Gbyte the datarate didn't increase. So it would take about 4 days for
the rest of the partition and I interrupted with Ctrl-C at first.
I think you are a bit impatient. 4 hours is normally little time to
rescue a damaged drive. Depending of the state of the drive, several
days may be expected. If it is a temperature problem, stop and let the
drive to cool down, then run ddrescue again.
My question is: is this behavior normal or could I call a commandline option so
that ddrescue will adapt the datatrate to the errorrate.
Ddrescue always reads data as fast as the drive can supply it. there is
no "datarate" to adjust. If ddrescue reads slowly it is because the
drive is having a hard time to deliver the requested data.
You may try stopping ddrescue and running it again from beyond the
error, but using always the same files, like this:
ddrescue -i errorpos+errorlenght /dev/hda1 /media/hdb1/imagefile
/media/hdb1/logfile
Regards,
Antonio.
_______________________________________________
Bug-ddrescue mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-ddrescue
