Comment 9 for bug 413345

I think I have experienced another facet of this bug. I had Jaunty installed in /dev/sda with a separate /boot partition. When I installed Karmic on another partition (also on /dev/sda) and *not* using the /boot partition for Karmic, the resulting grub.cfg created entries for Jaunty that ignored the separate /boot partition. In other words, In other words, it produced:

menuentry "Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sda6)" {
        insmod ext2
        set root=(hd0,6)
        search --no-floppy --fs-uuid --set 7f69072f-cea2-4ec3-bde9-81dd16744034
        linux /boot/vmlinuz-2.6.28-15-generic root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
        initrd /boot/initrd.img-2.6.28-15-generic
}

when it should have been:

menuentry "Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sda6)" {
        insmod ext2
        set root=(hd0,6)
        search --no-floppy --fs-uuid --set 9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2
        linux /vmlinuz-2.6.28-15-generic root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
        initrd /initrd.img-2.6.28-15-generic
}

Annotated results from 'blkid'

root@cypress:/media/disk/boot/grub# blkid
/dev/sda1: UUID="5C0CDB8F0CDB6296" LABEL="SERVICEV003" TYPE="ntfs"
/dev/sda2: UUID="C4F8DDE6F8DDD730" LABEL="SW_Preload" TYPE="ntfs"
/dev/sda3: UUID="DE62E0C562E0A38D" LABEL="Lenovo" TYPE="ntfs"
/dev/sda5: UUID="9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2" TYPE="ext3" <<<<<<<<<<<< Jaunty /boot
/dev/sda6: UUID="7f69072f-cea2-4ec3-bde9-81dd16744034" TYPE="ext3" <<<<<<<<<<<< Jaunty /
/dev/sda7: TYPE="swap" UUID="a8b4289b-34b4-4c92-a7b9-c0bd7f253cff"
/dev/sda8: UUID="e186fa4e-a98c-49b9-b491-2205628c1f75" TYPE="ext3" SEC_TYPE="ext2" <<<<<<<< (shared /home)
/dev/sda9: UUID="836c9f55-820b-4760-b2cb-81af5b6fedfe" TYPE="ext4" <<<<<<<<<<<< Karmic /
root@cypress:/media/disk/boot/grub#

This was on the Karmic beta Desktop CD as of 2009-10-06. Following work around (which will require manual editing of grub.cfg every time I run 'update-grub on Karmic) I installed grub-pc on Jaunty and found that it did appear to produce grub.cfg compliant with a separate /boot partition when run from that installation. I'm not certain that the Jaunty grub.cfg is correct for Jaunty (which does not use the /boot partition.) It produced the entry:

menuentry "Ubuntu, Linux 2.6.31-12-generic (on /dev/sda9)" {
        set root=(hd0,9)
        linux /boot/vmlinuz-2.6.31-12-generic root=UUID=836c9f55-820b-4760-b2cb-81af5b6fedfe ro quiet splash
        initrd /boot/initrd.img-2.6.31-12-generic
}

If that uses the search line for Jaunty it will not find the kernel or initial RAM disk as those are not in the /boot partition.