I get the following error upon completion of clone with errors.


I tested a clone on an error free drive and I do not get the above logfile error. It just defaults back to the root prompt.

I've been using ddrescue from a live SystemRescueCd, but recently I made a SystemRescueCd bootable flash drive and still got the logfile error. There is about 500Mb free on the flash drive.

Anyone know why I get the logfile error?

If I type where would the log file be stored?

The log file is stored in the directory in which you run the command, unless you specify another location.

_________________
Luke
Recovery Force Data Recovery

Gotcha. So in the case of a live cd it tries to store it on the cd, which is why I get the error.

In the case of my flash drive though...is 500Mb enough for a logfile? Maybe I need a larger flashdrive.

With the live CD, it would depend on how much space it sets aside in memory...but, you would lose the log file if you need to reboot. As for the thumb drive, I suggest you use something larger.

_________________
Luke
Recovery Force Data Recovery

Out of 1300 log files I have the biggest is 77MB

^^ cool, thanks. I just ordered a 16Gb thumb drive anyways.

The one I was originally using was 1Gb with 500Mb of free space.

So to confirm...when I run the command from the thumb drive as is... ...the logfile should be on the root of the thumb drive.

Ok so I ran ddrescue on a bad drive again using the thumb drive with 500Mb free space and still gave me the logfile error.

From my understanding if I run the command from the flash drive...

...it should save it to the flash drive right?

If the flash drive is /dev/sdc then maybe I have to do...



Maybe I'll have to setup a dual boot for linux to make this work so it saves it on the hard drive.

No. Due to the clever tricks used on LiveCD/USB images (e.g. UnionFS), you cannot assume the behaviour you describe above. In some cases, files saved will probably go to the RAM disk (as lcoughey mentioned above). Other filesystems may be read-only (which is what I suspect is happening to you).

Your issues now are with SysRescue & Linux and not with ddrescue or data recovery, and this is not a SysRescue or Linux forum, so don't expect exhaustive help here. This is one of the problems with trying to use ddrescue on Linux, without having Linux experience. You may want to do more general learning & practice about using Linux, and SysRescue behaviour / functionality (without touching your "problem" disk until you are more confident). I don't use SysRescue myself.


No. That's the wrong syntax / approach - you need to save the logfile to a filesystem, not to a raw device.


I can't judge whether that's sensible for you, on your system, and with whatever your skill level is. Without setting-up a dual-boot system, there are several possible approaches you could take, including either:

a) Researching the use of "backing store" (sometimes called "backstore") on SysRescue.

or

b) Using an extra, formatted USB memory stick to hold the ddrescue logfile. This needs to be mounted read/write in Linux before you run ddrescue, and then your ddrescue logfile parameter needs to point to a filename on that filesystem.

Of those two, I expect (b) will be easier for you. Personally I doubt you're running out of space on your original USB memory stick, and I expect that the error message is due to where you are telling ddrescue to try to write the logfile, and how SysRescue is designed to treat that filesystem.

sshfs is your friend