Public bug reported:
Binary package hint: grub
Running grub-mkconfig or update-grub in karmic beta leaves only the
karmic partition as bootable. Other systems such as 9.04 are found but
the setup in grub.cfg is wrong and they will not boot. The version is
kubuntu beta for 9.10
What update-grub set up for 9.04:
menuentry "Ubuntu, linux 2.6.28-15-generic (on /dev/sda8)" {
insmod ext2
set root=(hd0,8)
search --no-floppy --fs-uuid --set a7fc95c3-f9f4-477c-932a-7860ceaa19ab
linux /boot/vmlinuz-2.6.28-15-generic
root=UUID=a7fc95c3-f9f4-477c-932a-7860ceaa19ab ro splash
initrd /boot/initrd.img-2.6.28-15-generic
}
Note that the --set uuid is the SAME as the root-UUID which is wrong.
Also the set root= points to partition 8 which is also wrong and points
to the '/' partition instead of the boot partition. Both the uuid and
the set root are pointing to the '/' partition and this leads to a
message of "must load linux kernel first" when trying to boot this
entry.
What works after manual changes:
menuentry "Ubuntu, linux 2.6.28-15-generic (on /dev/sda8)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set 1ad72304-03b2-41f4-bb83-9a13ec9f75a8
linux /vmlinuz-2.6.28-15-generic
root=UUID=a7fc95c3-f9f4-477c-932a-7860ceaa19ab ro splash
initrd /initrd.img-2.6.28-15-generic
}
Above, the set root= now points to the /boot partition and the --set
uuid now points also to the /boot partition. I also removed the
/boot/ from in front of both the kernel and initrd lines. This may not
be necessary but those items were not included in the entry for karmic
which works without changes.
** Affects: grub (Ubuntu)
Importance: Undecided
Status: New
--
grub under karmic sets up wrong boot situation
https://bugs.launchpad.net/bugs/446292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
