GUI won't start

[easegill]

Kia ora Hamish

I have installed DDRescue-GUI 2.1.1 and python3-getdevinfo v2.0 but I can't get the GUI to start. A link appears in my start menu and there is a (system) timer icon starting when I click the link but after about 30 seconds it drops off. Don't see anything that I'm doing wrong.

Linux Mint 20.3
gddrescue 1.23-2

Thanks, Nigel

[hamishmb]

Hi there Nigel,

Thanks for reporting this. I myself use Linux Mint 20.3 I need some more information to help diagnose this issue.

Could you send me the output from:

Code: Select all

/usr/share/ddrescue-gui/DDRescue_GUI.py

And attach as a file here please?

Thanks,
Hamish

[easegill]

Hi Hamish

Thanks for looking at this. Text file attached.

Nigel

[hamishmb]

Hmm, looks like python3-bs4 isn't installed correctly, or one of its dependencies.

Have you got any custom python packages installed with pip?

[easegill]

Synaptic shows python3-bs4 v4.8.2-1 and soupsieve 1.9.5+dfsg-1 installed. Not sure how to tell if anything is installed with pip. Nearly anything I install comes through software centre. I did a reinstall of bs4 from Synaptic but no difference.

[easegill]

Apparently I can find out what has been installed with PIP!
List with pip freeze and smaller list with freeze --user.
Nothing jumps out at me.

[easegill]

Further info. I booted the computer from a USB and installed GDDRescue and DDRescue-GUI. The GUI started fine and I was able to run it. I left it overnight so it has done 14 hours. Hasn't recovered anything at all so far. Has flagged 2 bad sectors. Previously SMART had said 'Disk OK. 1 bad sector'.
When I tried to abort, the GUI wouldn't respond. The terminal window showed that it was still active but abort had no effect. Tried several times over half an hour and eventually closed the GUI from the eXit button. Had a look at the disk that I am recovering to and there is no log file there. I think I might have a permissions issue on the disk so going to investigate that.

Fixed the permissions on the disk and ran again overnight. 11 hours, 0Mb recovered, 17Mb unreadable. I'll continue tonight and hopefully at some point it will start finding some readable data.

[hamishmb]

(reply to previous posts)

Okay, I think your local install of bs4 (BeautifulSoup 4) is causing issues - maybe remove it?

[hamishmb]

(reply to latest post)

Hmm, that's interesting. Sometimes ddrescue can get itself into a stuck state if the drive completely stops responding, but I haven't seen this issue for a while. You should have had an immediate error if ddrescue's map file couldn't be written too, so that's strange. What OS are you running on your USB stick?

It might be worth trying to use the "read backwards" option as per the user manual at: https://www.hamishmb.com/files/support/ddrescue-gui/advancedsettings.html#idm394.

Hope this helps,
Hamish

[easegill]

Found time to get back to this. Thanks for the previous messages. I removed the older version of bs4 and that has fixed the ddrescue start. Means I can now run it without having to close everything and reboot to usb.

Ran ddrescue backwards for 24 hrs and no data recovered. Then ran it overnight with 'soft run' selected as thought that may make it at least search out somewhere that was readable but still no luck.

I realise that recovering data is a long process. Should there be some indication that there is data available to recover? Do I just leave ddrescue running for weeks?

Disks on Mint says "Disk is OK, one bad sector". States size as 4.1 Gb although it is a 3Tb disk.

Opening GParted hits repeated errors for the disk eg fsyncing/closing /dev/sde: Input/output error and then a set of i/o errors during read or write. Once it has run through these it shows the disk as 3.86Gb with all space unallocated and no partition table. Would creating a new table help?

I also realise that you aren't a data recovery service so I appreciate the help you've given so far.

Cheers,
Nigel