Hi Dylan, On 05/28/2011 06:15 PM, Dylan Distasio wrote: > Thanks, Neil. > > I think running mkinitrd was probably the only thing required for a > fix after reading your response. I had an older array on the same box > that was completely removed, but maybe something was leftover in > initrd. > > My detailed understanding of the initrd process is fairly limited. I > didn't realize there was a separate mdadm.conf that was used when > booting that is separate from the one in /etc. Many people miss this. Modern linux distributions, with few exceptions, use a three stage boot process: 1) kernel, 2) initramfs, then 3) real root FS. If there is no mdadm.conf in an initramfs at all, but the initramfs has raid support, mdadm will assemble everything it finds. It will assign the first array to md127 and count backwards from there. You might like this description of the process from the kernel docs: http://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt The money quote: "An initramfs archive is a complete self-contained root filesystem for Linux." If you change anything on your system that might impact the boot process, you're probably going to need to run "update-initramfs", or your distribution's equivalent. HTH, Phil -- 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
