<p dir="ltr">yes. store image file and log file on known good disk. try with -n first to grab as much good data as possible first in the case of the drive getting worse over time. afterwards try without -n and then play with other parameters. use a logical data recovery tool on the resulting image if there was moderate physical damage and the image file is incomplete. </p>
<p dir="ltr">Sent from my mobile. Please excuse the brevity, spelling, and punctuation. </p>
<div class="gmail_extra"><br><div class="gmail_quote">On Aug 9, 2016 11:46 PM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ok, having to rescue a disk because it failed before I had an<br>
opportunity to back it up. So I'm going to try the gddrescue route<br>
because it looks like it hit the limit of reallocatable sectors and now<br>
just spews logical block errors and sense errors.<br>
<br>
My reading of gddrescue is almost a set-and-wait approach. It behaves<br>
automagically tearing through the faulty drive scraping up whatever it<br>
can. Is that a reasonable assessment?<br>
<br>
I am generating an image file using it so I presume I could just mount<br>
the image file as if it were a disk in order to get to the data.<br>
______________________________<wbr>_________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo</a><br>
</blockquote></div></div>