Hello,
I've searched the forums here but have not found anything similar.
I'm in the process of trying to recover data from a failing HD. I'm recovering about 250 GB of data.
OpenSuperClone was suggested as a live boot solution so as to avoid any writing to the disk.
I've used DDRescue to get an .img file from the disk.
DDRescue is reporting back 99.99% recovery with about 8 MB of "bad" data.
I've tried mounting and accessing the .img file as a loop device and also mounting it as a drive. I can browse a few directories via the File Manager application but quickly get to a directory that is 'unreadable'.
From the command line I can do ls -al on these same 'unreadable' directories and get a list of files. The files I wish to rescue.
R-Linux was suggested as a tool for me to be able to access those files.
I installed R-Linux in the OpenSuperClone environment and ran the program. I've tried double-clicking on the image file, I've tried running the Scan. In both cases, the scan moves along nicely and then just abruptly closes. There are no messages or errors relayed to the user via the interface.
What can I do to either see what the problem is so that I can try to resolve it? Is there a log file that I can access to help me determine what is happening?
Thank you all in advance for your time.
Edit: I went back through the manual and found a statement about stopping the scan early (if you have too many files). I attempted to do this before the 80% mark, and it abruptly closes the program as soon as I answer Yes. I tried stopping earlier ~50%, and had the same behavior.
R-Linux Scans ~ 80% then closes abruptly.
Re: R-Linux Scans ~ 80% then closes abruptly.
Are you sure that the image isn't damaged?
Re: R-Linux Scans ~ 80% then closes abruptly.
I have to be honest and say I don't know how to know if it is damaged.
R-Linux was recommended to me as a solution to recover files from the image.
The drive was supposedly failing. So I'm guessing there's _some_ incongruous data there, but I thought that was what R-Linux was supposed to resolve, or at least attempt to resolve. Maybe I'm misunderstanding the tool's function, or maybe the person who suggested it misunderstands what the tool is capable of doing...
How would one know if the image is damaged?
Thank you for your patience.
R-Linux was recommended to me as a solution to recover files from the image.
The drive was supposedly failing. So I'm guessing there's _some_ incongruous data there, but I thought that was what R-Linux was supposed to resolve, or at least attempt to resolve. Maybe I'm misunderstanding the tool's function, or maybe the person who suggested it misunderstands what the tool is capable of doing...
How would one know if the image is damaged?
Thank you for your patience.