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. > Running mkinitrd when you have boot problems is always a good idea. Maybe > that was all it took to fix your problem ?? > > >> >> I had to run the above commands, and then make sure I ran >> update-initramfs -v -u for it to stick after reboot. >> >> My issue is solved, but I would like to understand what the root cause >> is, and why the above solution worked. Can someone elaborate on what >> super-minor is? This is a home system and I had backups so I was >> comfortable trying the above, but I don't typically like running >> commands on faith I don't understand fully, especially in Linux. >> >> Can anyone shed some light on this? I can provide further OS and >> array details if necessary, but it sounds like this issue has occurred >> for others in the past. > > Now that the problem is fixed it is very hard to figure out what was happening > before. My best guess is that someone was wrong with mdadm.conf in the > initrd, but I don't know what. > > NeilBrown > > -- 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
