![]() > """We didn't get ddrescue's initial status! This probably means ddrescue > beginning on top of my existing backup with old log file: ![]() > Here is the full error message I get when trying to start from the > Unknown Person gave more information on the question: Glad you have your files back, and hopefully this answers your query, If you're sure you picked the right file, enable the "overwrite output file" option and try again. :)ĭid you select the same output file? The force (overwrite output file in GUI) option is a safety mechanism to stop you accidentally writing to a device, it stopping the recovery implies you selected the wrong output file that time. I'll fix the semantics in the next release, hope that clears it up for you. When closing the GUI, it asks to save DDRescue-GUI's log file - nothing to do with the recovery log file, you can decline to save that one. Yep, you need to select to save the log file when choosing it from the choice box, that's just an issue of semantics, sorry about that, but it won't destroy your log file. can you give a brief view of how to run with the log file, and what I can expect using the log file. Do I need to re-run the image with soft run OFF a second time? If I include the log file, will it go faster? Or will it just re-ignore bad sectors? So after this soft run, does it mean it will not record bad sectors, or it was able to read all bad sectors? Can take the drive as fully imaged? > blocks were re-allocated and I guess it cant do any more, so I am > From the SMART report - using a different utility - I get that ~4000 > Unknown Person is still having a problem: > Question #296261 on DDRescue-GUI changed: Starting again with the same input, output, and log files but with soft run disabled will be fine, and is probably what you want to do :) The other options remain the same, but using the log file allows ddrescue to remember where it got to. Without a log file, you have to start from scratch every time. ![]() The reason for using the log file is that you can stop and start the recovery as you please, starting where you left off. It skips over the bad sectors when using the soft run option, so to read them, you need to restart the recovery with it disabled. ![]() > You received this question notification because you are an answer Do I have to force it to read bad sectors so that it can report them to me? ![]() Because although it has run slow in between, the bad sector count is "0" and bad data size is also "0". In soft run mode, will the GUI still tell me when it encounters bad sectors and the size of them although it is not going to try to read them. I am running a soft run, on about 500 GB of data and have completed 150 GB. > A question about the soft run: I know my drive has bad sectors. I am trying to come out of a bad drive right now as I type, so I must thank you for your effort !! > Firstly, this is a wonderful GUI component to a very much needed program. If you didn't don't stop the recovery because you might not be able to continue where you left off. If you turn off the soft run, it should start reporting the bad areas either way, as long as you used a log file. It could change from version to version, so what OS are you running on? I'm not sure, but I am a bit surprised it isn't giving you at least a rough estimate. You're very welcome, I'm glad you like it! ![]()
0 Comments
Leave a Reply. |