Hi Antonio, Thanks for the reply.
On Tuesday, 12 June 2012, Antonio Diaz Diaz wrote: > > > Trimming is slow (it reads backwards one sector at a time). In your case > it seems there are a lot of blocks to trim. > > I would try the following: > > 1) stop the rescue and move the logfile to a safe and non-volatile place. > > 2) run ddrescue with the --direct option. This should avoid caching and > increase speed of trimming. > > 3) if 2 fails, try the option --try-again. > Thanks, I'll try that. My question is: if I interrupt the process at this point, can I mount & >> CHKDSK the destination drive and expect to see usable data? Or will the >> partition structure not yet be complete? >> > > This will modify the destination filesystem, and then you won't be able to > resume the copy meaningfully. > OK. But if I decide that I've already retrieved 'enough' data (for a friend, btw), then I can interrupt the copy at this point and have target disk that has all the existing data on it? It doesn't need to run to completion to be useable? Jessica
_______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
