>From your description, I'd guess that one of the heads on your drive is having trouble, while the other ones work ok.
There are commercial recovery tools that can work out the mapping from LBA number to head number for a drive, and then you can skip any broken/slow heads to read the rest of the data. It'd be really useful if ddrescue (or some other Linux tool) could create such a map. Regards, Ketil On 14 August 2017 at 01:51, Ole Tange <[email protected]> wrote: > My current dead disk is quite interesting: It has a lot of "tar pits" > where the speed drops dramatically. Reading at 3000KB/s it hits a tar > pit, and after 30MB of 10KB/s it suddenly goes back to 3000KB/s and > stays there until the next tar pit a few 100MB later. > > It is currently scraping, and it would be very useful if I could tell > ddrescue to skip the next 1MB if the read speed went below 1MB/s. It > might make sense to skip X bytes if speed drops below X bytes/s. I do > not want ddrescue to stop if the speed goes below the limit, but I > want it to skip forwards. > > I have tried -a 1000000, but that does not seem to do this. > > /Ole > > _______________________________________________ > Bug-ddrescue mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/bug-ddrescue > -- -Ketil <http://ketil.froyn.name/> _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
