help fixing corrupted RAID array
From: Reuben D. Budiardja (techlist_at_voyager.phys.utk.edu)
Date: 06/21/05
- Previous message: Clark: "Adaptec ATA Raid 2400A in RHEL 3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: redhat-list@redhat.com Date: Tue, 21 Jun 2005 11:11:57 -0400
Hello,
I have a machine with software RAID5 enabled. After a power failure, the raid
wont start, and during booting, this message appears:
---
Starting up RAID devices : raid5 : failed to run raid set md0
Checking filesystems
/boot : clean, ...
fsck.ext3 : /dev/md0 :
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2 filesystem
(and not swap or ufs or something else), then the superblock is corrupt, and
you might try running e2fsck with an alternate superblock :
e2fsck -b 8193 <device>
Invalid argument while trying to open /dev/md0 [Failed]
---
In the "repair filesystem" mode, I tried to use "e2fsck /dev/md0" but it gives
me the same message. I tried running "mke2fs -n /dev/md0" to give me the
backup superblock and it says that "device size is reported to be zero ... "
I suspect this is because /dev/md0 doesn't actually exists since raidstart
failed ?
I tried "mke2fs -n /dev/hde1" to see the individual partitions that make up
the RAID and it gives me the backup superblock info. But when I feed that to
e2fsck it complains that the partition is not ext2 (which is correct since
it's a RAID partition, I thought).
So now I am confused as to what to do. Is there anyway I can recover the data
in my RAID array ? Below is my /etc/raidtab. Any help is greatly appreciated.
----------- /etc/raidtab------------
raiddev /dev/md0
raid-level 5
nr-raid-disks 3
chunk-size 64k
persistent-superblock 1
nr-spare-disks 0
device /dev/hde1
raid-disk 0
device /dev/hdg1
raid-disk 1
device /dev/hdi1
raid-disk 2
Thanks.
RDB
--
Reuben D. Budiardja
Dept. Physics and Astronomy
University of Tennessee, Knoxville, TN
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/M/MU/P/S d-(++) s: a-- C++(+++) UL++++ P-- L+++>++++ E- W+++
N+ o? K- w--- !O M- V? !PS !PE Y PGP- t+ 5 X R- tv+
b++>+++ DI D(+) G e++>++++ h+(*) r++ y->++++
------END GEEK CODE BLOCK------
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
- Previous message: Clark: "Adaptec ATA Raid 2400A in RHEL 3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- About RHEL 3 Software RAID 5 cant boot? (superblock)
... I have a machine with RHEL 3 software RAID 5 enabled. ... The superblock
could not be read or does not describe a correct ext2 ... If the device is valid and it really
contains an ext2 filesystem ... (linux.redhat) - Re: URGENT: RAID5 Ext3 superblock corruption
... > seems that the previous card corrupted the filesystem somehow. ... >
Luckily the root partition RAID is alive and working. ... > filesystem, then the superblock
... > is corrupt, and you might try running e2fsck with an alternate superblock: ...
(comp.os.linux.misc) - Help fixing corrupted RAID5 partition
... I have a machine running software RAID5 using: ... After a power failure, RAID
failed to start. ... The superblock could not be read or does not describe a correct
ext2 ... (Fedora) - Re: URGENT: RAID5 Ext3 superblock corruption
... > 7500-8 cards in our filserver bonked out. ... > seems that the previous
card corrupted the filesystem somehow. ... > Luckily the root partition RAID
is alive and working. ... > filesystem, then the superblock ... (comp.os.linux.setup) - RE: my first raid disaster on reboot :o( update2
... Either the superblock or the partition table is likely to be corrupt!
... when a raid is created with mdadm, does it automatically overwrite the last ...
(Debian-User)