 | | | help fixing corrupted RAID array | help fixing corrupted RAID array 2005-06-24 - By Sandhya Suman
Back
Hi,
/dev/md0 doesnt seems to be started successfully.
Data can be recovered in following way.
comment out/remove the entry for /dev/md0.
Then try rebooting the m/c.
Create new file system on constituent devices being used in raid array
> device /dev/hde1
> raid-disk 0
> device /dev/hdg1
> raid-disk 1
> device /dev/hdi1
> raid-disk 2
Mount the file system and recover the data.Hope it will help you.
Regards
Sandhya Suman
> Message: 7
> Date: Wed, 22 Jun 2005 06:31:31 -0400
> From: "Reuben D. Budiardja" <techlist@(protected)>
> Subject: help fixing corrupted RAID array
> To: taroon-list@(protected)
> Message-ID: <200506220631.32090.techlist@(protected)>
> Content-Type: text/plain; charset="us-ascii"
>
>
> 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-- ---
>
>
>
> -- ---- ---- ---- ---- ---- --
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
> http://www.redhat.com/mailman/listinfo/taroon-list
>
> End of Taroon-list Digest, Vol 16, Issue 36
> *******************************************
>
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|