Kevin, ddrescue -v -f /dev/sdb3 /dev/sdc1 /media/(user)/log
Personally I prefer to save the recovered data as 'images' on an existing filesystem, that way it's a bit easier to manipulate them, and you can always load them up via the loopback if you want to fake a physical drive; ie
($pwd is some path where you have enough room to store the image/clone of /dev/sdb3)
ddrescue -v -f /dev/sdb3 sdb3.img sdb3.log Hope that helps On 06/09/16 23:11, Kevin Okie wrote:
Dear All, I'm attempting to clone a corrutped Windows partition from bad disk/partition sdb3 to external HD device/partition sdc1 The command I am using is: ddrescue -v -n /dev/sdb3 /dev/sdc1 /media/(user)/recoverylogfile.txt --force (doing '-n' at first to skip errors so i can return to them later) (added '--force' because without it I get the message "output file exists and is not a regular file". '--force' allows me to overwrite what is on the target device). Even if I shorten up the logfile part of the command to just 'logfile.txt' with no path, I get the same error. However, if I omit the logfile part of the command, the utility runs. However, I need the logfile to go back and try to recover parts of the drive with errors later. Any assistance much appreciated! Thanks! Kevin _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue
_______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue