Hi, I this would also be beneficial being able to use with --retrim, which I currently can't use to go backwards past the last lockpoint on the drive.
Thanks! Mike On Fri, Feb 6, 2009 at 11:22 AM, Michael Darling <[email protected]> wrote: > Hi, > > First, thank you very much for your continued work on this program! I have > already gotten a lot of data off of my drive. It had a head problem that > caused some platter damage. After swapping the head in a cleanroom, I'm in > the process of still getting data off. > > There are a few spots on the drive that when attempted to be read cause the > disk to lock up. Nothing can see the drive anymore until I reboot. Trying > the spot(s) again cause another lockup. > > Right now, I'm keeping track of different --input-position's, and rebooting > a lot. For example, If I have a lockup at 2516M, I'll reboot and try at > 2550M and search backward how close I can get before locking up. > > Now let's say that I have some errors between 2000M and 2516M that I want > to retry. I already know that hitting 2516M would cause a lockup. If I > could specify to stop program execution at 2515M, that would save me a few > additional reboots. I don't see a way to do this with existing options. I > can't use --max-size because I don't know how many if any errors between > 2000M and 2515M will be read. > > Thanks! > > Mike >
_______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
