Am 06.11.2013 um 14:10 schrieb Niklas: Florian Sedivy <address@hidden> writes:
First, you could use -A (—try-again) together with an approximate -i 500G.
This should reset the last 250200MB in the log file from
"*" (non-trimmed) to "?" (non-tried).
Hey yall,
thanks for all of your advice, I busted out a new configuration:
sudo ddrescue -i 506G -A -f -n -c 1Ki /dev/rdisk3 /dev/rdisk1 nsclone.log
and it started running again so it would seem that yall are correct
in the idea it just skipped the last 230g.
-------------------------------------------
GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued: 44488 kB, errsize: 323 kB, errors: 211
Current status
rescued: 16075 MB, errsize: 38099 kB, current rate: 149 kB/s
ipos: 541068 MB, errors: 289, average rate: 466 kB/s
opos: 541068 MB, time since last successful read: 0 s
Copying non-tried blocks...
-----------------------------------------------
so, further questions....
From reading all of the information from you guys,
the -A made all the Blocks after 506G "unread".
So if I it stops or I have to stop it, can I just run it without the -A
and it will pick up wherever it left off / at the first non-tried block,
or would I need to run it from a specific position using -A -i ###G?
is there anything I should be wary of to avoid gorking it?
i.e If I ran it -A without an -i position, would it like.... explode,
overwrite or combine further recovered information with the current data?
I also forgot to run it a -c 256 - fail.
Thanks Yall,
Niklas.
You can stop ddrescue any time with ctrl-c and it will resume where you left off, as long as you use a log file.
You don't need to specify -A together with -i again, unless the same thing happens again (rest of drive reported as one big error). Generally speaking, if your command includes a one-time-option (-A, -M or -t), you should remove that option when you just want to resume.
-c 1Ki is fine, as it will run at the same speed as -c 256, only with less frequent status updates. At the "current rate" displayed above, -c 1Ki will update the status every 4 seconds, compared to every second with -c 256.
In sum, if you interrupt, you might simply continue with: sudo ddrescue -f -n -c 256 /dev/rdisk3 /dev/rdisk1 nsclone.log
Once that has finished without any more "too big errors", you might want to repeat the trimming phase, [optionally only for the area before the big error], because when the disk presumably disappeared, ddrescue may have tried to trim, but only got errors. sudo ddrescue [-i 506G] —retrim -f -n /dev/rdisk3 /dev/rdisk1 nsclone.log
Finally, remove the -n option and let ddrescue complete its work, [optionally with as many retries as you like]. sudo ddrescue -f [-r 3] /dev/rdisk3 /dev/rdisk1 nsclone.log
You're welcome, Florian |