I'm working through verification of this fix, and one thing that I've come across is that if the raid was setup using the older version of grub/grub-installer (e.g. off of 8.04.1 media), grub-install is not re- invoked and so the second disk still does not have a grub stage 1 in its MBR. Thus, if the first disk of a raid1 set fails, the system will still not boot at all.
In talking with Dustin about this on IRC, he suggested that it's probably best handled as a documentation issue. I think it would be useful to to at least warn via debconf/update-notifier if /boot is on an md device and grub is being updated from a version that did not support "grub-install /dev/mdX" properly. Also, for testing the update to grub-installer, it would be useful if we could do a one-off spin of the hardy images for testing in prep for 8.04.2. (That's the only issue I've come across so far; now that I've manually run 'grub-install /dev/md0', I'm able to boot in degraded mode off of either disk). -- SRU: Backport of Boot Degraded RAID functionality from Intrepid to Hardy https://bugs.launchpad.net/bugs/290885 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
