The position you marked (0x41A4D10000) is 282GB, but you said it had copied about 750GB when you stopped, so it can't be the position you stopped at.
I think Antonio is right, ddrescue finished the first pass in the "several hours" after restarting, and when you checked it had already gone on to trimming (which is slower), processing position 282GB when you copied the mapfile. Greetings, Florian > Am 18.10.2016 um 17:47 schrieb Antonio Diaz Diaz <anto...@gnu.org>: > > Hello, > > David Morrison wrote: >> So instead of getting non-split and bad sectors, I am getting >> non-trimmed failures. I am unsure what this means, other than that I >> have another 55 hours to go when I thought I had only about 8. :-( > > It may be because of the days passed between the two runs. OTOH, the first > part looks as if it had been already trimmed. Is ddrescue trimming just now? > > What version of ddrescue are you using? > Did you use the same version both times? > > > Best regards, > Antonio. > > _______________________________________________ > Bug-ddrescue mailing list > Bug-ddrescue@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-ddrescue _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue
