Hi Jason. The command you ran does the following:
It will read the sda2 partition and write it to the sda3 partition. You did not specify where you want to the log file to be saved other than the same working directory from where you are running the command. By default, a shell opens up in the /home/ubuntu folder when you run from the live cd. This is why it is writing it there. In your case, the sdb3 partition must be the same size or larger than the sda2 partition here. If it is not, you will run out of space. The filesystem on sdb3 is irrelevant since you are imaging the sda2 partition (therefore copying the filesystem) onto it. You imply that the log file should go there, but how can a file be written to a filesystem that is in the process of being copied? What you would need to do it create another partition on the destination drive, format it to any filesystem you like, mount it and write the log file there. For example, let's say you created a 100 meg partition /dev/sdb9. sudo mkfs.msdos /dev/sdb9 mkdir mountpoint sudo mount /dev/sdb9 mountpoint sudo ddrescue -r3 -v /dev/sda2 /dev/sdb3 mountpoint/logfile (same as sudo ddrescue -r3 -v /dev/sda2 /dev/sdb3 /home/ubuntu/mountpoint/logfile or cd mountpoint sudo ddrescue -r3 -v /dev/sda2 /dev/sdb3 logfile) I must point out that I doubt that the logfile size is what is causing you to run out of space. It would take longer than 20 minutes to fill up the ramdisk on a modern computer. Just sayin'. Are you sure the destination partition (/dev/sdb3) is larger than sda2? If you cannot play around with the partitions on the destination drive, I can show you how to image the source partition to a file and then mount that file as if it were a real hard drive. I hope this helps. Andrew Zajac AndrewZajac.ca --- On Sat, 1/1/11, Jason Hemminger <[email protected]> wrote: From: Jason Hemminger <[email protected]> Subject: [Bug-ddrescue] gddrescue puts logfile into ubuntu home folder not 2nd hard drive To: [email protected] Received: Saturday, January 1, 2011, 2:58 PM I am new to Linux/Ubuntu and am using it to clone/recover information from a NTFS drive that the MBR became corrupt on. I feel like I am on the right track and have installed a 2nd drive that is recognized by Ubuntu and is larger but when I start the sudo ddrescue -r3 /dev/sda2 /dev/sdb3 log command it crashes after about 20 min. due to the drive being out of space. I am running this from a Ubuntu live CD and it appears to be creating the log file in the Ubuntu home directory. I am stumped. Does my syntax to reach the output drive not make sense? Is there a way to point/redirect the file that is being written to the home directory to instead go to the 2nd hard drive? Does it matter if the 2nd hard drive is mounted or not? Or formatted or not? I feel like I have tried every available combinations such as formatting the 2nd drive as ext3/ext4/and NTFS. I have also tried to leave it as an unformatted drive. I think I am close to pulling this off but I can't get the output log file correct. Any thoughts would be appreciated. Thank you- Jason -----Inline Attachment Follows----- _______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
_______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
