menu.lst not updated after kernel update

[Jeffrey Seguerra]

i upgraded my hardy desktop to intrepid ibex rc and i notice that the latest kernel is not in the menu.lst before booting when you press ESC.

[Thomas Bechtold (toabctl)]

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Jeffrey Seguerra (jepong)]

not anymore... thanks you.

[Charlie Kravetz (cjkgeek)]

I have found this to happen upgrading from Xubuntu 8.10 to Xubuntu Jaunty Jackalope. I have three hard drives installed, all PATA. I installed Xubuntu 8.10 to sdc, before installing jaunty to sdb. When I run the upgrade, all items upgrade as expected with no errors. When the system is restarted, the grub menu has not changed from before the upgrade. Selecting sdc to boot into from the menu does boot into Jaunty on sdc, but the grub menu is never updated. All installations have been told to install grub to the MBR of the first boot device.

I believe there is enough information to confirm this report.

[Steve Langasek (vorlon)]

Charlie, you're inferring that the original submitter's problem is the same as yours but there is no evidence of that. Setting this bug back to 'incomplete'.

[David Edwards (se014a0001)]

I think I have experienced this problem upgrading from 'hardy' to 'intrepid'.

It seems that the grub update step isn't synchronised with the installation of the new kernel, and the generation of a new initramfs. In my case, I ended up with a menu.lst that listed the new kernel, but did not have a corresponding initrd line for it. The menu.lst was generated at a time when the kernel image was there, but the initramfs had not yet been created. The new kernel would not boot. Fortunately an old one would.

[Jan Schnackenberg (yehaa)]

I just had this very same issue after installing Jaunty from the alternate disk and afterwards switching to grub (I hate LILO).

I just today found that there were these two lines missing in the file /etc/kernel-img.conf:

postinst_hook = update-grub
postrm_hook = update-grub

I have no idea where those lines should have come from, but after inserting them into that file the update-grub skript was called. Could this be your Problem?

[Steve Langasek (vorlon)]

Jan, those lines are created by grub-installer as part of the installation process. A more interesting question is why you ended up with lilo instead of grub when installing jaunty; lilo is only used by default in certain disk configurations where grub is known to not work reliably.

Anyway, the original submitter says this is no longer a problem for him, so I'm closing this bug - there's no sense in leaving a bug open with such a generic description, it just becomes a magnet for twenty different bugs.