Public bug reported:
Binary package hint: linux-image-2.6.17-10-386
I first noticed this problem when I upgraded from Dapper to Edgy. I noted that
in the upgrade to Edgy the menu.1st file that Grub uses was re-written with the
location of the boot image specified as a UUID, as in;
title Ubuntu, kernel 2.6.17-10-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.17-10-386
root=UUID=1dd4ba53-b277-49ad-9f7c-27533b0446fa ro quiet splash
Previously in Dapper the kernel root was located by a directory path as in;
title Ubuntu, kernel 2.6.15-27-386
root (hd0,3)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/hda4 ro quiet splash
Note the difference in the second line. My Ubuntu partition is on (hd0,3) not
(hd0,1). I had to edit menu.1st manually to get a bootable system.
I just upgraded to linux-image-2.6.17-11-386 and this is what it wrote to
menu.1st;
========================================================
## ## End Default Options ##
title Ubuntu, kernel 2.6.17-11-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.17-11-386 root=/dev/hda2 ro quiet splash
initrd /boot/initrd.img-2.6.17-11-386
savedefault
boot
title Ubuntu, kernel 2.6.17-11-386 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.17-11-386 root=/dev/hda2 ro single
initrd /boot/initrd.img-2.6.17-11-386
boot
title Ubuntu, kernel 2.6.17-10-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.17-10-386 root=/dev/hda2 ro quiet splash
initrd /boot/initrd.img-2.6.17-10-386
savedefault
boot
title Ubuntu, kernel 2.6.17-10-386 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.17-10-386 root=/dev/hda2 ro single
initrd /boot/initrd.img-2.6.17-10-386
boot
title Ubuntu, kernel 2.6.15-27-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/hda2 ro quiet splash
initrd /boot/initrd.img-2.6.15-27-386
savedefault
boot
title Ubuntu, kernel 2.6.15-27-386 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/hda2 ro single
initrd /boot/initrd.img-2.6.15-27-386
boot
title Ubuntu, memtest86+
root (hd0,1)
kernel /boot/memtest86+.bin
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Home Edition
root (hd0,0)
savedefault
makeactive
chainloader +1
======================================================
I had to again manually fix this changing all (hd0,1) entries to (hd0,3) and
/dev/hda2 to the proper partition UUID (I guess /dev/hda4 would work, but I
remember this caused some other problem with mounting USB memory sticks).
I should mention that I have a bit of an odd partition layout.
/dev/hda1 is an NTFS partition for windows.
/dev/hda2 does not exist.
/dev/hda3 is extended.
/dev/hda5 is swap.
/dev/hda4 is ext3 for Ubuntu.
Things ended up this way when I shrunk my windows NTFS partition to give
Ubuntu more room and because Gnome Partition Manager does not support
move for ext3 I had to shrink hda1, create a new ext3 partition in the
space between hda1 and hda2 (this was labeled hda4), copy the contents
of hda2 to hda4, delete hda2 and then expand hda4.
Anyway, it appears that whatever is updating the menu.1st file when a
linux-image upgrade is done is disregarding the existing menu.1st
entries and misreading the partition table.
** Affects: linux-source-2.6.17 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Linux-image upgrade messes up menu.1st
https://launchpad.net/bugs/84289
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
