Re: (clug-talk) Partition Disaster!!!!!!

[J. Rafael S�nchez]

Hey Johnny, I don't have an extremely technical based suggestion for you, but I'll share something I did one of these days that I had something similar happened to me on a 160GB U160 scsi hard drive.   At first I freaked when I tried the first combination/alternative of superblock number and it did not work. Like you I had very important data on that drive. Surprisingly enough I kept trying every single one of those superblock numbers, and to my surprise really, one of the last ones worked for me. I'm not sure if this means that some of the first supperblocks copies of my hard drive were corrupted as well or what. I cannot tell ya.   $ mke2fs -n /dev/hdb1 # pretend command.   After that I was able to mount it and back it up unto another hard drive. I also should mentioned that I did all this on a separate system all together.   This may not work for you, but it happened to be successful for me. Also I'm not sure if you specifically have to use the fsck.ext3 command or if you simply used the fsck or the e2fsck commands, they would automatically default to the file system type that you have on your hard drive. That I cannot tell you either.   Best of wishes. Rafael.          ----- Original Message ----- From: Johnny Stork To: CLUG Sent: Tuesday, November 19, 2002 8:59 AM Subject: (clug-talk) Partition Disaster!!!!!! It looks like I have done some serious damage to a 50gb partition on a new 60gb IDE drive. Around a week ago I noticed some errors showing up on the console. Basically that hdb "lost interupt" or something simliar (didnt get logged to /var/log/messages). There were also some messages from the drive about seek_error etc and then "resetting" and then all would be ok. I was so busy it took me a day or so before I had the chance to look at it, but by then that drive seemed to lock up. Since it was a new drive I figured it was a loose/bad cable or power connector (seen simliar behavior from such a cause) and so shut down the machine and re-connected/checked all cables. One was pulled out a little. But on re-boot I got the "Bad magic number in super-block while trying to open /dev/hdb1" etc etc And no combination of fsck.ext3 -b 8193 /dev/hdb1 (with16385, 24577 etc superblock) will work. I was about a week before mirroring this partition, and had not setup any sort of backup routine so right now I have lost over 4000 MP3's which were all ripped from my own CD's. An incredible amout of time and effort. So does anyone have any other suggestions on how I could recover this partition? btw: No errors have showed up since from that drive and so I beleive it is NOT a hard drive problem and was related to the loose cable. ________________________________ Open Enterprise Solutions Open Solutions for an Open World Johnny Stork, BA Calgary, AB Canada http://www.openenterprise.ca http://www.open-solutions.ca