My suggestion would be that a running counts of "Errored blocks skipped"
Have you tried ddrescue 1.22 or later? It shows a count of read errors:
Ah, I was using 1.21 since that's what came with the "System Rescue CD"
that I used as my Unix environment to run ddrescue. From the sample
output you showed it looks like it addresses my suggestion to a large
extent--thanks!
2. -A OPTION DOESN'T SEEM TO DO ANYTHING
You need to use -M in addition to -A:
Ah, thanks, I missed that. In fact, based on the description of -M
"-M / --retrim / Mark all failed blocks inside the rescue domain as
non-trimmed before beginning the rescue. The effect is similar to
'--retry-passes=1', but the bad sectors are tried in a different order,
making perhaps possible to rescue some of them."
it seems that -M is what I really wanted instead of -A (I was misled by
a blog post somewhere that suggested -A). From my reading of the above,
though, it seems like -M alone is what I would need (i.e., without -A),
no? What's the difference between -M alone and -M -A together?
Thanks again for taking the time to respond, Antonio.
Regards,
Shahrukh
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
