[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-ddrescue] how big should my MBR rescue be?

From: andrew zajac
Subject: Re: [Bug-ddrescue] how big should my MBR rescue be?
Date: Sat, 26 Jul 2008 09:19:26 -0700 (PDT)

--- On Sat, 7/26/08, Ian Simmons <address@hidden> wrote:
From: Ian Simmons <address@hidden>
Subject: Re: [Bug-ddrescue] how big should my MBR rescue be?
To: "James Bardin" <address@hidden>
Cc: "ddrescueQuestions" <address@hidden>
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:


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.


Good Luck.

Now with a new friend-happy design! Try the new Yahoo! Canada Messenger
reply via email to

[Prev in Thread] Current Thread [Next in Thread]