[Bug 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic

[Marcus Tomlinson]

This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.

** Changed in: grub2 (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/454418

Title:
  grub misconfigured after upgrade to linux-image-2.6.31-14-generic

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: grub-pc

  What happened:

  I was running linux-image-2.6.31-13-generic. I upgraded to linux-image-2.6.31-14-generic using
    sudo aptitude safe-upgrade
  There was a minor issue with linux-firmware which might be related, but a second safe-upgrade fixed the linux-firmware package and did not appear to trigger any grub-related activity. (I'd point to the comments I made in another bug but I can't find it with any search I do on bugs in 'linux-firmware')

  I shut down the system, and powered off. Waited 10-20sec.
  I powered up the system, got the grub menu and the new kernel was listed first in the list, as expected.
  I hit return to boot it and it started - I saw the bootsplash screen etc.
  Then I saw these lines on screen
    udevadm trigger is not permitted while udev is unconfigured
    udevadm settle is not permitted while udev is unconfigured
    svgalib: cannot open /dev/mem
  ... some lines with advice about what to do...
    /dev/disk/by-uuid/9eccc..etc.. does not exist! Dropping to a shell.

  The uuid shown was the correct uuid for the root of the installation (the same as used by the 2.6.31-13-generic kernel)
  It appears that something has gone awry with the grub entry for this kernel.

  
  I don't have access to more detail (eg grub versions) right now.
  The box has two hard disk, with hardy on one and karmic on the other and it is back in production.
  I can get more details as required in a few days' time.


  What I was expecting to see:

  a normal boot

  
  Steps to reproduce

  It appears all that is required is to safe-upgrade when you have
  linux-image-2.6.31-13-generic installed and linux-image-2.6.31-14-generic pending for install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/454418/+subscriptions