Package: mdadm Version: 1.8.1 Severity: normal Tags: patch mdadm installed, I built two RAID0s (md0, md1) with two discs each. Now I build a RAID5 out of these RAID0s and two additional "real" discs (md2) (yes, performance not good, but cheap ;). But when booting up, a "mdadm -A -s" only finds the two RAID0s, I have to run "mdadm -A -s" manually again to have the RAID5 activated. I suppose this is because of the "search order" of mdadm - if it assembled md0 and md1 first, it would find md2, but it doesn't ...
I wrote an email to Neil Brown, programmer of the original mdadm tool. He said, there's a bug in the 1.8.1 release that prevents mdadm from building all defined RAIDs to be assembled correctly. He sent me a patch that worked for me perfectly: http://neilb.web.cse.unsw.edu.au/~neilb/source/mdadm/patch/patch-1.9.0-pre1 (Thanks, Neil! :) For diagnosis, my config: munin:~# cat /proc/mdstat Personalities : [raid0] [raid5] md2 : active raid5 md0[0] hdg1[3] hde1[2] md1[1] 591868416 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] md1 : active raid0 hdc1[0] hdd1[1] 197289536 blocks 64k chunks md0 : active raid0 hda1[0] hdb1[1] 197289536 blocks 64k chunks unused devices: <none> munin:~# cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md0 level=raid0 num-devices=2 UUID=c96c2ddc:b0ce5e2a:ccdf137c:05e0343f devices=/dev/hda1,/dev/hdb1 ARRAY /dev/md1 level=raid0 num-devices=2 UUID=0badc57b:37e026e6:6d51311f:2aa8aee4 devices=/dev/hdc1,/dev/hdd1 ARRAY /dev/md2 level=raid5 num-devices=4 UUID=6b8b4567:327b23c6:643c9869:66334873 devices=/dev/md0,/dev/md1,/dev/hde1,/dev/hdg1 So far, this bug is almost solved ... :) Thanks! Thomas -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (100, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages mdadm depends on: ii debconf 1.4.40 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii makedev 2.3.1-75 Creates device files in /dev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
