dpkg-reconfigure mdadm did not work for me. It turns out that *somehow* the UUID on my raid array changed and the mdadm.conf never got updated (possibly when I grew the array with mdadm -grow?) and the change wasn't obvious, because the first two segments were identical. I only noticed it when I ran out of other options and compared them side by side... Anyhow, once the UUID was updated in mdadm.conf and initrd.img was regenerated, I was able to boot 2.6.22-14.
The only thing I can think is that the mdadm script in 2.6.20-16 must be *much* more forgiving, because by all rights, that should have never booted either. -- gutsy md module not present in ramdisk https://bugs.launchpad.net/bugs/133765 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
