It may be that the drive is spending lots of time doing error correction. I usually run Steve Gibson's SpinRite to recover and remap sectors from a failing drive before I proceed to image it. If it is unsafe for SpinRite to run it will generate a warning to that effect. Best software I've ever purchased.
https://www.grc.com/sr/spinrite.htm On Mon, Aug 14, 2017 at 10:51 AM, Ole Tange <[email protected]> wrote: > On Mon, Aug 14, 2017 at 7:01 PM, Ole Tange <[email protected]> wrote: > > On Mon, Aug 14, 2017 at 9:56 AM, Ketil Froyn <[email protected]> wrote: > > > >> From your description, I'd guess that one of the heads on your drive is > >> having trouble, while the other ones work ok. > > > > In that case we should expect the problem to arise at a fairly > predictable rate. > > It looks like Ketil is right: I get around ~50 MB of tar pit and ~150 > MB of smooth sailing. Then ~50 MB of tar pit again. The drive is > hts545050b9a300 and has 250 GB/platter + 4 heads according to > https://www.hgst.com/sites/default/files/resources/TS5K500B_DS_final.pdf > > Given that I have finite amount of time what is the most efficient way > of getting all the data, that is fast to copy, and skip the data, that > is in the tarpit? > > > /Ole > > _______________________________________________ > Bug-ddrescue mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/bug-ddrescue > -- Lou Bilancia, P.E. Synnovation Engineering Inc. cell: (503)572-5519 _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
