On Mon, Aug 27, 2012 at 18:06:05 +0200, Thomas Bächler wrote: > Can you run add 'break=premount' to the kernel command line and try to > get some mdadm output? I don't know exactly what to look for, but maybe > try to assemble the array with verbose output. By using break=premount, > you hook into the boot process _before_ anything has been written to > your disk, so you don't destroy the consistency of your RAID. > > Also, can we see your mdadm.conf? Which mdadm hook are you using, mdadm > or mdadm_udev (I use mdadm_udev btw)? break=premount breaks after RAID+LVM assembly, so doesn't really help. :-) But I get dropped to a shell prompt anyway when the raid can't be assembled. I forgot to mention, "mdassemble" always works fine from there (no "mdadm" command in the initrd). Could it be a timing related issue/race condition? My mdadm.conf is attached. I don't know whether that uses mdad_udev or not? Geert -- geert.hendrickx.be :: geert@xxxxxxxxxxxx :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
### obtain the following with `mdadm --examine --scan` ### RAID-1 DEVICE /dev/hd*[0-9] /dev/sd*[0-9] ARRAY /dev/md0 UUID=d3922590:e3cb6140:a860122c:a592f098 ARRAY /dev/md1 metadata=1.2 UUID=a00a0fc2:43a84051:d4e59313:a75d70bf name=boris.ghen.be:1 ### MONITOR MAILADDR root
Attachment:
pgpemlSNOVLAI.pgp
Description: PGP signature
