MBR Problems and Using Linux to Recover external Hard Drives
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
MBR Problems and Using Linux to Recover external Hard Drives
I have a situation. I have an external hard drive that is used strictly for media storage. It is a 250GB Lacie Porshe USB drive. Recently it is no longer accessible in windows. It is detected, but viewed as an unformatted disk. I have tried running the SystemRecoveryCD and have found that there are errors in the BootSector. I am a noob at this and don't want to go writing new MBR or anything because I'm afraid of making the disk further inaccessible. When booting to the SystemRecoveryCD using the TestDisk and Gparted application, I can see my drive listed at /dev/sda however it shows up as an unknown filesystem. It is a FAT32 system. I ran FDisk from terminal and this is what it shows:
Disk /dev/sda: 250.0 GB, 250059350016 Bytes
255 Heads, 63 sectors/trac, 30401 cylinders
Units= cylinders of 16065*512 = 8225280 butes
Device Boot Start End Blocks ID System
/dev/sda1 * 1 30401 244196001 c W95 FAT32 (LBA)
I've also tried mounting the disk on Knoppix when booting via livecd and was unable to mount the disk.
When running Testdisk on analyze, it has a read error at 0/1/7 (lba=69)
I have Window's XP and Debian and if I can't recover the drive would like to just be able to copy the directories to another external drive but don't know how to go about it.
I know I'm probably not covering all the necessary information, but if theres anything further that would help let me know.
Thanks
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
if you have another drive, bigger than 250 megs, use dd to copy the damaged drive to the good one. then you can use filesystem repair stuff on the new drive to get what you can off of it.
Thread: MBR Problems and Using Linux to Recover external Hard Drives
Quote:
Originally Posted by whansard
if you have another drive, bigger than 250 megs, use dd to copy the damaged drive to the good one. then you can use filesystem repair stuff on the new drive to get what you can off of it.
Should I copy to a new directory in the new drive? Otherwise wouldn't I create the same problem on the new disk? Or is that why I need a disk bigger than the original disk?
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
you will be making a duplicate of the old drive, bad data and good data, that you might be able to repair if the drive can be written to without errors. trying to fix the data structures on the bad drive may make things worse.
obviously this will take a crap load of hard drive space and time, and luck, but otherwise the stuff is all gone now anyway.
With all the stuff dd'd to a new drive, you can at least try different ways of fixing things on the new drive without further destroying more data on the original bad drive.
no directory for copying, and yes, that's why the destination drive needs to be bigger. neither the source or destination drive should have any partitions mounted, and the command would be something like # dd if=/dev/sda of=/dev/hdc.
I'm just guessing at the device names.
find and use schily's sdd instead of dd if you want a progress report while copying. he wrote cdrtools also.
Last edited by whansard; 10-24-2007 at 01:49 PM.
Reason: forgot something.
you will be making a duplicate of the old drive, bad data and good data, that you might be able to repair if the drive can be written to without errors. trying to fix the data structures on the bad drive may make things worse.
obviously this will take a crap load of hard drive space and time, and luck, but otherwise the stuff is all gone now anyway.
With all the stuff dd'd to a new drive, you can at least try different ways of fixing things on the new drive without further destroying more data on the original bad drive.
no directory for copying, and yes, that's why the destination drive needs to be bigger. neither the source or destination drive should have any partitions mounted, and the command would be something like # dd if=/dev/sda of=/dev/hdc.
I'm just guessing at the device names.
find and use schily's sdd instead of dd if you want a progress report while copying. he wrote cdrtools also.
After running dd_rescue /dev/sda /dev/sdb I booted into windows, as the disk was a FAT32 and fdsk appears to work on ext3 filesystems and the drive isn't recognized as It now has the same errors on it. I run chkdsk /r/f and it repairs the errors and the drive works but there is nothing on it. What happened to the data I copied from the failed drive? Does chkdsk erase that when I run it? Sorry, I'm an amateur.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.