Joe Landman wrote:
Ok. This is where it gets interesting. If the /etc/mdadm.conf is on the RAID, you have a bit of a "chicken and egg" problem to deal with here. How does the system find /etc/mdadm.conf to make the RAID when /etc/mdadm.conf is on the RAID? This implies that /etc/mdadm.conf is in the initrd. Peeking inside the default centos one, I can see that this is not true. Which implies that it doesn't see /etc/mdadm.conf before it assembles the array, as the /etc/mdadm.conf is on the array, and not in the initrd image. Is there a way to include the /etc/mdadm.conf into the initrd?
This is almost certainly your problem. If / is a RAID volume, the initrd itself needs to have an /etc/mdadm.conf that reflects how it is constructed. This is something that mkinitrd should be doing for you. I'll second the suggestion of running mkinitrd with sh's -x option to see why it's not doing this for you. Good luck.
-- Brendan Conoboy / Red Hat, Inc. / blc@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
