One of the things I struggle with is knowing where ddrescue is up
to. The display shows quite a lot of information in the initial scan
(ipos/opos go up), and even in the first attempt to scrape the bad
blocks from the first pass (non-scraped counts down to zero, read
errors and bad areas go up). However, in its retries of the bad
blocks, there is not really much indication of where it is up to.
Read errors continue to go up, and ipos/opos change, but these are
not helpful unless you know how many bad blocks it has yet to scan.
Is there some way to know how far through a retry it has got? (Yes,
the mapfile would probably say, but as I described earlier, I do not
have a mapfile due to an oversight. :-(
Never mind. I remember now I could have specified a log file to be
created containing all this information.
This episode teaches me that I need to concentrate more and look at
all the options before kicking off a copy.
David
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
