DDRescue-GUI

Hang at "StartingDDRescue..."

Asked by Richard Travers

Running DDRescueGUI.dmg 1.3 downloaded today. OSX is 10.6.8 Server. Restarted server then ran DDRescue. No apps running except Finder and Activity Monitor. DDRescue Preferences set to Default. Source is mounted and mostly readable internal non-startup data disk (500 GB). Destination is external 6 TB empty partition via Firewire. GUI shows only"StartingDDRescue..." for past 60 minutes (no other output or evidence of activity in GUI). Log file has not yet appeared. No terminal output. Activity Monitor says 3 threads, 32.2 MB RAM, and mostly 0.0 % CPU, and occasionally 0.1 %.
How long should I wait for evidence of activity?

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,

Sorry to hear about that! I'll convert this into a bug.
Strange I never found out about that.
OS X 10.6.8 should be okay, though, mind, I didn't have access to any server releases, and seeing as your HDD isn't completely trashed, you should probably have gotten some activity instantly!

Do you mean the log file that you specified for ddrescue?
You should probably kill the process with Activity Monitor, and then could you open Console and post any output you find here?

Thanks,
Hamish

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

Wait a second, you are running this on an Intel Mac aren't you?

Thanks,
Hamish

Revision history for this message
Richard Travers (rich5rd) said : 		#3

Hi Hamish,
Thanks for your reply. Yes, I mean the log file I specified for ddrescue. Yes, I'm running on Intel Mac. Since posting I have discovered the drive's SMART is reporting around 4000 bad sectors reallocated. Perhaps that's the problem? I killed process shortly after posting using Activity Monitor. I will try again in morning and post Console output.
Thanks!

Revision history for this message
Richard Travers (rich5rd) said : 		#4

Hello, I tried again but this time ran the attempt on a single 4KB file. It aborted after 12 seconds. Here is console output:

01/04/2015 10:40:31 [0x0-0xba0ba].org.pythonmac.unspecified.DDRescue-GUI /Volumes/DDRESCUEGUI/DDRescue-GUI.app/Contents/Resources/startddrescue.sh: line 42: /usr/share/ddrescue-gui/ddrescue: No such file or directory
01/04/2015 10:40:43 [0x0-0xba0ba].org.pythonmac.unspecified.DDRescue-GUI Exception in thread Thread-1:
01/04/2015 10:40:43 [0x0-0xba0ba].org.pythonmac.unspecified.DDRescue-GUI Traceback (most recent call last):
01/04/2015 10:40:43 [0x0-0xba0ba].org.pythonmac.unspecified.DDRescue-GUI File "threading.pyc", line 810, in __bootstrap_inner
01/04/2015 10:40:43 [0x0-0xba0ba].org.pythonmac.unspecified.DDRescue-GUI File "/Volumes/DDRESCUEGUI/DDRescue-GUI.app/Contents/Resources/DDRescue-GUI.py", line 1099, in run
01/04/2015 10:40:43 [0x0-0xba0ba].org.pythonmac.unspecified.DDRescue-GUI AttributeError: 'StartBackend' object has no attribute 'exit'

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

Okay, thanks, this confirms the existence of a possible bug I found on the 30th of March,
although I'm certain that I checked this at the time...

Right, I'm on it, and I'll have a fix out soon, probably Saturday or Sunday, but this suggests to me that the download files have been tampered with, so I'll check them ASAP.

Hamish

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

Nope, the digital signatures are all fine, forutnately.

I'll go fix this bug then :)

Hamish

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

Hi,

I think I've fixed it, it now seems to work for me.

Could you try this new file I've uploaded please? (Look at the related bug at the top of the page, you'll find it there)
If it works, I'll add it to the release page.

Thanks,
Hamish

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

Okay, I will now assume this is fine; there are no changes since the last version for OS X, with this being the exception, and I've done basic testing, so it should be fine.

Thanks for your help,
Hamish

Can you help with this problem?

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

To post a message you must log in.