restarting ddrescue gui after accidental abort...

Hi,

Thanks, and I'm glad you like it. You didn't need to change the log file's name, it appears as a text file because essentially that what it is.

Only thing is make sure you don't save the GUI's log file (it prompts you to save this when you close the GUI) over the recovery log, but if you haven't done that you're fine :)

Nah, you should leave it checked, it's fine. The log file allows ddrescue to pick up where it left off, so it won't change any data that was already recovered.

Hope this helps,
Hamish

Thanks for your response! I started it again with your suggestions and it started right from where it had left off last time. I suppose that was supposed to have been a no-brainer but when everything takes so much time (it would have taken two full days to have formatted the destination drive if I had restarted the recovery from scratch) it was worth asking.

The reason why I added .log was because it wouldn't let me select a file if it didn't have that ending; it wasn't a .log file by default and so it wouldn't show up as a selectable option.

Many thanks,
Chris

Hi Chris
Can I ask when you aborted - did you select Resest, mount image, or Quit? Do you remember?
I've accidentally aborted and I want to continue the recovery from the same place as last time using the log file but I'm worried if I choose the wrong option it will wipe out what I've done so far.
Hope you can help
Thanks.
Jonathan

Hi Jon,

-- Answered as part of the other bug report at https://answers.launchpad.net/ddrescue-gui/+question/452008

Hamish

Hello Jon,

It's been a while so please forgive me if I'm not completely sure about what happened, but I believe the first time around, the USB cable on my failing/inaccessible hard drive (it's external) lost connection, aborting the process (which I estimated would take months). I started from scratch and before I could do this I had to reformat the receiving hard drive (also external), which took about 2 days.

So the second time this happened I asked Hamish what I should do. I believe I "quit", WITHOUT resetting or mounting. If I recall, even if you say "no" when it asks you something along the lines of if you want to "save changes to the logfile" or something, it still saves the logfile as it looked at the time it was aborted.

I then tried again with the same recovery settings and selecting the logfile from the previous attempt, and I believe the recovery restarted from where it had last left off.

I hope this helps,
Chris

Hi,

To clarify, that issue was resolved in the other thread. Also, the log file to save when closing, is the logfile for the GUI, not for the recovery, and it is important that you don't save it over the recovery log file.

The recovery should have started where it left off, but wiping your drive in between runs wasn't really necessary, just so you know :) If you wiped your destination drive mid-recovery, you'll have to start from scratch, as the data you recovered before would have been wiped.

^ All of this, is why ddrescue (the commandline program this is a GUI for) is awesome: it's easy to resume a recovery again after stopping it.

Hamish

I see, I see. Thank you for the clarification. I think that at the time, I was just confused about the "two logfiles".

Yeah, I didn't want to wipe the destination drive again so that's why I asked for your help to clarify what I should do.

Thanks and please keep up the good work :),
Chris

Hi,

Ah okay, I get it now. Since this report, I changed the wording, and made it impossible to overwrite the recovery log with the GUI's log, so it should be hard to make a mistake accidentally now :)

Thank you, I shall try XD

Hamish