[Bug 957262] Re: update-grub ran before update-initramfs resulting in a menu.lst without an initrd line

[Colin Watson]

grub (0.97-29ubuntu66) precise; urgency=low

  * When we replace the /etc/kernel-img.conf hook with the
    /etc/kernel/postinst.d hook on upgrade, also call update-grub manually;
    otherwise if the kernel was upgraded before grub itself, update-grub may
    only be called before update-initramfs (due to triggerization of the
    latter), giving us an unbootable default entry in menu.lst.
    LP: #957262.

 -- Steve Langasek <steve.langasek at ubuntu.com>  Fri, 16 Mar 2012
12:55:10 -0700

** Changed in: grub (Ubuntu)
     Assignee: Colin Watson (cjwatson) => Steve Langasek (vorlon)

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

Title:
  update-grub ran before update-initramfs resulting in a menu.lst
  without an initrd line

Status in “grub” package in Ubuntu:
  Fix Released

Bug description:
  I was performing a distribution upgrade from Lucid to Precise and was
  unable to boot after the upgrade.  Come to find out this was due to my
  menu.lst missing an intird line.  I had the following:

  title           Ubuntu precise (development branch), kernel 3.2.0-18-generic
  root            (hd0,0)
  kernel          /boot/vmlinuz-3.2.0-18-generic root=/dev/md0 ro quiet splash
  quiet

  I manually added in the initrd line and was able to boot.  I also
  reinstalled the linux-image package and the initrd line was created
  for the recovery boot option.  From what I could see in the apt-
  term.log file update-grub was run one time halfway through the upgrade
  and update-initramfs was run at the very end.  So I'm guessing because
  there wasn't an initrd available it wasn't added to menu.lst.

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