[Bug 290885] Re: SRU: Backport of Boot Degraded RAID functionality from Intrepid to Hardy

Dustin Kirkland dustin.kirkland at gmail.com
Fri Dec 5 16:41:45 UTC 2008


I consciously did *not* edit the postinst to do the grub install, in
order to keep with the rule of "least surprise".

I agree with Steve's comments that it would be quite nice if this
could be done automatically, but I don't think messing with every RAID
user's MBR is something that we should/could do automatically.

In any other circumstance, upgrading the grub package installs new
binaries to the system, but it doesn't reinstall the bootloader.

One thing I've learned over the last 6 months developing, testing, and
debugging this work is that there are some varied and unique RAID
setups out there.  It's impossible to catch all of them.

As I said before, I think this part of the "enable my Hardy system for
booting degraded RAID" should be handled via documentation.  There is
a server-guide task attached to this bug.  We need to add a bit there.
 Probably something in the Community documentation would be good.  And
I can certainly blog about it.

Beyond that, code-wise, perhaps we could emit a warning in the
grub-install postinst, that detects if /boot is on a RAID, and
recommend that the user investigate the situation and perhaps run
grub-install on the device.  Steve mentioned update-notifier, which
might be interesting on some desktop systems running RAID, but it's
not present on the server.


SRU: Backport of Boot Degraded RAID functionality from Intrepid to Hardy
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to initramfs-tools in ubuntu.

More information about the kernel-bugs mailing list