So far, no errors are reported and the image is up to 8 Gigs. I've had to stop and restart several times over the past few days and at one point I somehow overwrote the log file with one that had less data retrieved from an earlier practice run.
Initial status (read from logfile) rescued: 7759 MB, errsize: 0 B, errors: 0 Current status rescued: 8634 MB, errsize: 0 B, current rate: 131 kB/s ipos: 8634 MB, errors: 0, average rate: 132 kB/s opos: 8634 MB Copying data... I made a copy of the image when it was only 4 Gigs and used it to learn how to use photorec. It retrieved several mp3s that will not play. I am assuming this is because the mp3s were fragmented across the drive so when I retrieved them it didn't have the complete files. Is this a correct assumption that I will need to try again on the complete image after ddrescue it finished? Is there a way to tell when all the actual data is rescued and stop it so it isn't just rescuing empty sectors? Thanks for the help. I will go and read the web pages you suggested. On Sat, 2008-07-26 at 09:19 -0700, andrew zajac wrote: > > > --- On Sat, 7/26/08, Ian Simmons <[EMAIL PROTECTED]> wrote: > From: Ian Simmons <[EMAIL PROTECTED]> > Subject: Re: [Bug-ddrescue] how big should my MBR rescue be? > To: "James Bardin" <[EMAIL PROTECTED]> > Cc: "ddrescueQuestions" <[email protected]> > Received: Saturday, July 26, 2008, 12:09 AM > > > Does this mean the file system is corrupted and needs to be restored > in > the image? How do I go about getting the image to a state where I can > mount it to get the files from it? Will the linux file recovery tools > mentioned such as photorec/testdisk fix the ntfs of the image? > > > How much of the image contains errors? > > You are able to work on the image (or a > copy of the image, since trying to fix a broken filesystem may result in > further data loss) using linux. It's easier than working on another drive, > actually. > > You may be able to repair the ntfs filesystem, but if you can't, you can use > file-carving software like photorec or foremost. > > You can get more details here: > > https://help.ubuntu.com/community/DataRecovery > > > You can also try fixing the NTFS boot sector. Again, you don't need to write > the image back a a hard drive to do this. > > http://ubuntu-rescue-remix.org/node/57 > > > Good Luck. > > > > ______________________________________________________________________ > Now with a new friend-happy design! Try the new Yahoo! Canada > Messenger _______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
