Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
help fixing corrupted RAID array

help fixing corrupted RAID array

2005-06-22       - By Reuben D. Budiardja

 Back
Reply:     1     2     3  


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

Earn $52 per hosting referral at Lunarpages.