Neil Brown wrote: > On Tuesday October 31, [EMAIL PROTECTED] wrote: >> Well I have the following mdadm.conf: >> >> DEVICE /dev/hda /dev/hdc /dev/sd* >> ARRAY /dev/md1 level=raid5 num-devices=4 UID=8ed64073:04d21e1c:33660158: >> a5bc892f >> ARRAY /dev/md0 level=raid1 num-devices=2 UID=cab9de58:d20bffae:654d1910: >> 6f440136 >> > Try > sh -x /etc/init.d/mdadm-raid start > and see what it does. > If have created /etc/mdadm/mdadm.conf rather than /etc/mdadm.conf have > you? Debian decided the config file should be in a directory > /etc/mdadm, and so are different from everyone else... > > NeilBrown
Neil, I ran the sh -x /etc/init.d/mdadm-raid start command and it is starting the arrays through mdadm -A -s and not by running mdrun. All in all, I'd tried the following before checking mdadm-raid: removing /sbin/mdrun removing my mdadm.conf placing my mdadm.conf in /etc instead of /etc/mdadm/ It just seems to be linked to the kernel.. since when booting from 2.6.12 my initscripts and config just work, while when using 2.6.15 without changing anything else. -- Peb - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
