New grub boot menu fails to show device designations

[Erick Brunzell]

I realize that this is somewhat intentional with the upgrade to grub 2.* but the new grub really is virtually worthless with a complex multi-boot because it fails to show device designations such as (sda2) etc.

I'll review this tomorrow and add more info after looking through the logs.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: grub-pc 2.00-7ubuntu8
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
Date: Thu Oct 11 22:10:25 2012
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121011)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

[Erick Brunzell (lbsolost)]

I'm including the grub.cfg.

[Erick Brunzell (lbsolost)]

Here's a pic of the actual boot menu.

[Erick Brunzell (lbsolost)]

And just handing boot off to an older grub2 OS results in ridiculously long and sometimes totally incorrect menu items like:

menuentry "Ubuntu quantal (development branch), kernel 3.5.0-15-generic (on /dev/sda15)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.5.0-15-generic--562a6d98-7630-445d-b3eb-186990955537 (on /dev/sda16)" --class gnu-linux --class gnu --class os {
 insmod part_msdos
 insmod ext2
 set root='(hd0,msdos16)'
 search --no-floppy --fs-uuid --set=root f3221ba1-36a8-42d5-9205-8d873e8ecb4f
 linux /boot/vmlinuz-3.5.0-15-generic root=UUID=562a6d98-7630-445d-b3eb-186990955537 ro quiet splash
 initrd /boot/initrd.img-3.5.0-15-generic
}
menuentry "Ubuntu quantal (development branch), kernel 3.5.0-15-generic (recovery mode) (on /dev/sda15)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.5.0-15-generic-root=UUID=562a6d98-7630-445d-b3eb-186990955537 ro single-562a6d98-7630-445d-b3eb-186990955537 (on /dev/sda16)" --class gnu-linux --class gnu --class os {
 insmod part_msdos
 insmod ext2
 set root='(hd0,msdos16)'
 search --no-floppy --fs-uuid --set=root f3221ba1-36a8-42d5-9205-8d873e8ecb4f
 linux /boot/vmlinuz-3.5.0-15-generic root=UUID=562a6d98-7630-445d-b3eb-186990955537 ro single
 initrd /boot/initrd.img-3.5.0-15-generic

You'll notice in one place it mentions sda15 but in another it mentions sda16.

So booting the correct OS is now like rolling the dice.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1065801

[Erick Brunzell (lbsolost)]

Testing Lubuntu Raring i386 20130104 and I see the "long name" problem is fixed but still no device desigantions. Please see the attached photo (sorry it's so fuzzy).

[Erick Brunzell (lbsolost)]

Just thought to also add that grub.cfg.

[YannUbuntu (yannubuntu)]

I agree that adding device name (eg sda5) would be useful, BUT only when there are several systems.

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]