(2013-10-04) Nothing's happening after start Topic is solved

Locked
hamishmb
Site Admin
Posts: 147
Joined: Sun Oct 28, 2018 10:47 am
Contact:

(2013-10-04) Nothing's happening after start

Post by hamishmb »

Original post from "jlx solutions" (2013-10-04):

DDRescue-GUI Version 1.1 Starting...
Saving Options...
Not overwriting output file...
Set to do all copy operations in normal direction...
Set to preallocate disk space...
Set to split bad areas of disk...
Using -b 512 as blocksize
Set to retry bad sectors -r 1 times...
Set to allow an infinite number of errors before exiting...
Set to copy 128 clusters at a time...
Using 600 seconds as timeout value...
Finished saving options...
Closing Preferences Window...
DDRescue is about to copy
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "./DDRescue-GUI.py", line 575, in run
ProgressBar.SetRange(int(datatorecover))
ValueError: invalid literal for int() with base 10: ''
hamishmb
Site Admin
Posts: 147
Joined: Sun Oct 28, 2018 10:47 am
Contact:

Re: (2013-10-04) Nothing's happening after start

Post by hamishmb »

Reply from "hamishmb" (2013-10-08):

Please note: it is a common problem to not be able to mount your finished image, se here are some instructions for future reference:

So if you made a complete image of all your HDD (say /dev/sda), including the partition table, you can follow the instructions here to mount it:

http://major.io/2010/12/14/mounting-a-raw-partition-file-made-with-dd-or-dd_rescue-in-linux/

So you need to present the image as if it were your hard drive, so using
the instructions I've sent, this should work, and then you can mount
/dev/loop2 as if it were your HDD, and copy files.

If you imaged only one partition of your HDD (say /dev/sda2), it should mount as is.

Hope this helps,
Hamish
hamishmb
Site Admin
Posts: 147
Joined: Sun Oct 28, 2018 10:47 am
Contact:

Re: (2013-10-04) Nothing's happening after start

Post by hamishmb »

Reply from "hamishmb" (2013-11-14):

Update: The likelyhood of this ever occuring has now been reduced massively (more intelligent backend) with version 1.2, so if recovering on systems under heavy load (bad idea), it has a greater chance of working, but you'd be unwise to try it under those circumstances.
Locked