DDRescue-GUI

(Parted Magic, warning when putting log file on desktop) error writing logfile

Asked by Heidi

when running ddrescue - i received an the message "error writing logfile '/root/Desktop/hg09072015log': no space left on device

this happened within the first 1 or 2 minutes after starting. i selected abort - but nothing happened and it seems to be still running ... CPU use is high ... but not sure if it is making progress.

I considered closing the program but it said I could not while ddrescue was running.

should i just let it run?

time remaining does not seem to be updating but time elapsed is updating.

my image destination is an external hdd.
Thanks for any help

Question information

Language:
English Edit question
Status:
Answered
For:
DDRescue-GUI Edit question
Assignee:
Hamish McIntyre-Bhatty Edit question
Last query:
Last reply:
Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said : 		#1

Hi,

That sounds annoying!
Before I can help, I need to know what OS you're running, and what version of my GUI you're running,
but in the mean time, you can close it by using the task manager or activity monitor, selecting DDRescue-GUI and killing the process. You might need to kill ddrescue as well.

Before a reboot could you please upload the log file at /tmp/ddrescue-GUI.log for me?

Thanks,
Hamish

Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said : 		#2

Whoops! I gave an answer instead of making an info request.

Revision history for this message
Heidi (heidi-granken) said : 		#3

Hi
DDrescue version is 1.4
it is windows 7
I did kill the process, but I am unsure how to resume.

Did I select an incorrect log file name/location? I had assumed I could just save it to the desk top.

The laptop is not working at all - I can only access via parted magic loaded into memory. when i try to turn on the laptop if errors unable to locate the hdd - so i booted from cdrom using parted magic and am trying to use ddrescue to see if any files can be saved/found.

I am pretty new to all this - so not sure I am approaching this correctly.

I have an external 500 gb hdd attached (failed hdd is 250Gb)
Image Source : /dev/sda 232 GiB (250 Gb)
Image Destination: /dev/sdb 465 GiB (500 GB)

Thanks for any more help you can provide - very appreciated!

Revision history for this message
Heidi (heidi-granken) said : 		#4

I was able to get it to run - I was incorrectly trying to save the log file to the desktop and there was not enough space. I changed the save location to the external hdd and everything seems to be running now.

It's been running for 1.8 hrs with remaining time of 11.6hrs

by the way - are these statistics from the Detailed Info concerning ( as in looks unlikely I will be able to recover files from the failed hdd ... or I have a chance ... or too soon to tell)

Recovered Data 33659.0 MB
Unreadable Data 207MB
Current Read rate 66121 B/s
Average Read Rate 5098 B/s
Bad sectors 672
Input position 34015MB
Output position 34015MB

Thanks so much for your response and feedback

Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said : 		#5

Hi,

When you changed the log file location to the external drive, did you make sure it was in a different place than where you're recovering to? Otherwise you might lose it.

I thought that was the problem, but I'll make sure I look at it later to see why it crashed. I'm glad you've got it working though :)

Your stats look pretty good to me, but as you said, only time will tell. So far it looks promising to me though :)

Thanks for letting me know about this glitch,
Hamish

Can you help with this problem?

Provide an answer of your own, or ask Heidi for more information if necessary.

To post a message you must log in.