Hello all, As you can see below, I also posted this message to the linux-raid mailing list. At this point, I am most concerned with data recovery. First, read the forwarded messages. I have added some additional data beneath the message.
--- Jimmy Gatt <[EMAIL PROTECTED]> wrote: > Date: Sat, 5 Jan 2002 16:07:21 -0800 (PST) > From: Jimmy Gatt <[EMAIL PROTECTED]> > Subject: I think I ruined my RAID, please help > To: [EMAIL PROTECTED] > > Hello all, > > I have a Linux fileserver running 3 120-Gig drives using > raid 5. I have run into problems and I need help. Let > me > give the background -- it's a bit long, so bear with me. > > I wanted to set up a fileserver with raid 5 and I did so > using a modified version of RedHat 7.0 that had reiserfs > support built in (because I wanted a journalized FS, and > RedHat 7.0 (the latest release at the time) did not > support > any journalized filesystems). So here was my setup: > > /dev/hda OS Disk > /dev/hdc RAID disk 0 > /dev/hde RAID disk 1 > /dev/hdg RAID disk 2 > > The raid worked fine and everyone in the house used it > ... > until today. > > Today, the OS disk died. After a power failure (I had > accidentally plugged the computer into the UPS plug that > *wasn't* connected to the battery!), the disk would only > boot into the dreaded "LIL-" when lilo tried to start. > > So I thought that today would be a great day to upgrade > the > OS to RedHat 7.2. I went through the RedHat installer > from > the CD, and I decided not to initialize the raid device > with the installer because redhat still does not support > reiserfs on installation. So I left it as is, and > figured > that I'd set up the raid device manually. The > installation > went without problems. > > Then, once I had a shell prompt, I set up my /etc/raidtab > as follows: > > --BEGIN /etc/raidtab-- > raiddev /dev/md0 > raid-level 5 > nr-raid-disks 3 > nr-spare-disks 0 > persistent-superblock 1 > parity-algorithm left-symmetric > chunk-size 32 > device /dev/hdc > raid-disk 0 > device /dev/hde > raid-disk 1 > device /dev/hdg > raid-disk 2 > --END /etc/raidtab-- > > I pretty much typed in exactly what was in the > Software-RAID-HOWTO. I then executed the following > commands: > > # /sbin/mkraid /dev/md0 > # /sbin/raidstart > > It turns out that the second command was superfluous. > The > hard drives started spinning, and /proc/mdstat told me > that > the raid was doing something. I figured it was > reconstructing the array. When that was done, I then > tried > the following: > > # mount -t reiserfs /dev/md0 /raid > > mount responded with this: > > mount: wrong fs type, bad option, bad superblock on > /dev/md0, or too many mounted file systems > > The exit code from mount was 32. Messages written to > syslog were the following: > > Jan 5 20:00:42 yuriy kernel: read_super_block: can't > find > a reiserfs filesystem on dev 09:00 > Jan 5 20:00:42 yuriy kernel: read_old_super_block: try > to > find super block in old location > Jan 5 20:00:42 yuriy kernel: read_old_super_block: can't > find a reiserfs filesystem on dev 09:00. > > Additional notes: > > 1. I do *not* have my original /etc/raidtab > 2. I *do* have the reiserfs module loaded into the kernel > > And here are my questions: > > 1. Can my RAID be restored? If so, how? > 2. If not, can my data be recovered? > 3. If there is no fix, will someone tell me what I > *should* > have done? Apparently, I did it all wrong. > > I appreciate y'all's time and assistance. Let me know if > I > didn't provide enough information. > > Regards, > Jimmy Gatt > I have not yet received any meaningful or helpful responses from the linux-raid mailing list. I have since done a "cat /dev/md0" and saw some recognizable strings (such as "ReIsEr2Fs") so I know that there is still data on the drive, and it is still in "reiserfs format." There is, however, no filesystem on the drive. Can y'all help? Let me know if I need to give more information. Regards, Jimmy __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
