Hey Antonio, > Ddrescue tends to become more intelligent after every interesting report sent > to this list
That's what I was hoping! Sending you the image on a separate, personal email with the log file next up. > The size of each error seems to be large (about 10MB), so the '--try-again' > option may read all those non-trimmed blocks fast. I'm not too sure about that, actually. When I tell ddrescueview to give me the details on each block, it lists the bad sector as 512 Bytes, with about 200megs of non-trimmed data around that. Or maybe that's what you meant? So would I simply extend my current command to be from now on: ddrescue -f -n -d -A /dev/sdf /dev/sde logfile ? (or just once?) And finally: My absolute pleasure! -David On Fri, Jan 31, 2014 at 6:31 PM, Antonio Diaz Diaz <[email protected]> wrote: > Hello David. > > > David Deutsch wrote: >> >> The curious thing (well, to me at least, you guys might've seen it all >> before) is that there seems to be a pattern to the bad sectors. Here >> is a screenshot of ddrescueview: > > > Nice image. Maybe ddrescue could trim drives like this more efficiently, or > even try to predict the size of the next bad area. Ddrescue tends to become > more intelligent after every interesting report sent to this list. :-) > > Could you send me the (compressed) logfile? I'll try to improve the trimming > algorithm with it. Thanks. > > > >> So - if somebody knows anything I can do to speed this up, I would be >> very greatful for suggestions! > > > The size of each error seems to be large (about 10MB), so the '--try-again' > option may read all those non-trimmed blocks fast. > > > Good luck and best regards, > Antonio. _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
