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
 
mdadm won 't start RAID5 array

mdadm won 't start RAID5 array

2005-10-21       - By Jos Vos

 Back
Hi,

When trying to re-assemble a RAID5 array of a disk cabinet with 8
disks (RAID5, 6 + 1 redundant + 1 spare) after a system crash,
using "mdadm -v --assemble /dev/md4 /dev/sda[m-t]1", I get:

mdadm: looking for devices for /dev/md4
mdadm: /dev/sdam1 is identified as a member of /dev/md4, slot 7.
mdadm: /dev/sdan1 is identified as a member of /dev/md4, slot 5.
mdadm: /dev/sdao1 is identified as a member of /dev/md4, slot 2.
mdadm: /dev/sdap1 is identified as a member of /dev/md4, slot 3.
mdadm: /dev/sdaq1 is identified as a member of /dev/md4, slot 4.
mdadm: /dev/sdar1 is identified as a member of /dev/md4, slot 0.
mdadm: /dev/sdas1 is identified as a member of /dev/md4, slot 6.
mdadm: /dev/sdat1 is identified as a member of /dev/md4, slot 1.
mdadm: added /dev/sdat1 to /dev/md4 as 1
mdadm: added /dev/sdao1 to /dev/md4 as 2
mdadm: added /dev/sdap1 to /dev/md4 as 3
mdadm: added /dev/sdaq1 to /dev/md4 as 4
mdadm: added /dev/sdan1 to /dev/md4 as 5
mdadm: added /dev/sdas1 to /dev/md4 as 6
mdadm: added /dev/sdam1 to /dev/md4 as 7
mdadm: added /dev/sdar1 to /dev/md4 as 0
mdadm: failed to RUN_ARRAY /dev/md4: Invalid argument

Also with --force it doesn't work.   Doing "mdadm -E /dev/sda..." also
looks good for the disks involved, the only problem seems to be that
the array won't start.

Any ideas?

--
--    Jos Vos <jos@(protected)>
--    X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--    Amsterdam, The Netherlands        |     Fax: +31 20 6948204

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list