Most of my own programming job concerns dealing with many different interfaces and quite an extraordinary variety of business logic cases. So trust me: I can relate. ;-)
And: This is the reason why I share so much information here. Maybe it will help another poor sap who comes here crawling the history for information on rescuing his own WD Green Line drive. I will leave it running for a while and see where we are in three days. I can see from the visualization that the current area is kind of complicated, so I would have to go through it at some point... -David On Fri, Feb 7, 2014 at 7:23 PM, Antonio Diaz Diaz <[email protected]> wrote: > David Deutsch wrote: >> >> After about 18 hours of reading in -R mode: >> [...] >> >> So it currently runs an order of magnitude slower than before. Or was >> that to be expected for the area that I'm reading? > > > One never knows what to expect from a failing drive. :-) > > It seemed that the end of the disc had fewer errors, but they may be harder > to recover. > > You may resume the rescue from where you were before with: > > ddrescue your_options_and_files -i 791401MB > > or you may leave it working and it will arrive there in 2.6 days or so. > > > Now imagine how difficult it is to develop an algorithm that works > reasonably well on all drives. _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
