Florian Sedivy <sedivy@...> 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. _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
