On Mon, 2007-06-04 at 22:30 +0200, maximilian attems wrote: > please keep the bug report on cc for future mails, thanks.
Sorry, I always forget about that :) > hmm the question is if sda and sdb come up early enough for mdadm, > did you try to boot with rootdelay=11 and no break arg? Yes they do, as /dev/md0 is created before the boot stops in busybox. And this happens without rootdelay too, so I guess the problem does not lie there. I compared the output before /sbin/init in 2.6.20 and 2.6.21 and they look absolutely the same. > mdadm --examine --scan ARRAY /dev/md0 level=raid1 num-devices=2 UUID=877c34c4:dfed29c7:4338e75f:35082da1 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6f583480:58ae2560:eac2cfa7:882022da ARRAY /dev/md2 level=raid1 num-devices=2 UUID=9dae3f6b:a3e79fbb:6044c75b:9f1939bd The UUID match the ones in mdadm.conf, so I guess there's nothing corrupted. > mdadm --assemble --scan --run --auto=yes md: md2 stopped md: bind <sdb3> md: bind <sda3> raid1: raid set md2 active with 2 out of 2 mirrors mdadm: /dev/md2 has been started with 2 drives md: md1 stopped md: bind <sdb2> md: bind <sda2> raid1: raid set md1 active with 2 out of 2 mirrors mdadm: /dev/md1 has been started with 2 drives And at this point in the initramfs I have /dev/md[0-2] ready to go... how could I mount them manually and resume the boot procedure? I tried to mount /dev/md0 /root but it does not work. -- Others will look to you for stability, so hide when you bite your nails. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]