On Tue, 2013-01-15 at 15:40 +0100, Christopher Huhn wrote: > Hi, > > On 15.01.2013 14:26, Ben Hutchings wrote: > > This is Debian - we carry on supporting hardware until it's turned to > > rust (well almost). Anyway if GRUB is complaining then the kernel isn't > > running yet, is it? > > No, it was not. > > >> Because of this, you need to make sure you're running the LATEST VERSION of > >> GRUB before you report a bug. Use grub-install to update it, and then > >> check > >> if the bug still applies. Debugging problems we already fixed makes us > >> waste > >> valuable time, so please try to avoid it. > > This exactly was not the case - and fixed my problem. Shame on me. > > I still think it's strange that the old grub could run 3.2.0-3 but not > 3.2.0-4. That's why the kernel was my first suspect. > > Unfortunately this means that I may have to update grub with each > release (or kernel?) upgrade on a couple of servers (~ 1000), > automatically choosing the proper boot device, which is normally handled > for me by FAI at install time and may be cumbersome eg. for software RAIDs.
This should be remembered by debconf (grub-pc/install_devices variable). I'm not sure whether there's a good way to get that information outside of a package maintainer script, though. > Please close this bug. Sorry for the inconvenience. Well, if this is a widespread problem then I think grub-pc must reinstall when the package is upgraded from a version has this bug. We cannot have upgrades resulting in an unbootable system. Were these systems initially installed with squeeze, or an earlier version? Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got.
signature.asc
Description: This is a digitally signed message part
