Gutsy installer creates a faulty menu.lst when a /boot/ partition is used

Bug #161861 reported by Elie De Brauwer
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

First, I didn't know which package is the real responsible for this error so I hope somebody is good enough to throw this in the right basket.

I've seen this on multiple occasions, but I can clearly remember this as well with my Edgy installation but since I still saw it with Gutsy I decided to write up this bug report.

It's an old habit of mine to perform a manual partitioning of the drive. And I always create one /boot/ partition and then a / (and optionally a /home but this is not relevant). But my partitioning now looks like this (on /dev/sdb, the bootloader is installed on /dev/sda)

isk /dev/sdb: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb6364037

   Device Boot Start End Blocks Id System
/dev/sdb1 1 12 96358+ 83 Linux
/dev/sdb2 13 136 996030 82 Linux swap / Solaris
/dev/sdb3 137 9964 78943410 83 Linux

The fstab looks like:

edb@Flying-Spaghetti-Monster:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb3
UUID=f47c3437-dbfa-4c40-8ac5-1e531e813aa9 / ext3 defaults,errors=remount-ro 0 1
# /dev/sdb1
UUID=e04f2d2f-8db1-4160-9192-89c439970f8c /boot/ ext2 defaults 0 2
# /dev/sda1
UUID=9C4CCC874CCC5E20 /media/sda1 ntfs defaults,umask=007,gid=46 0 1
# /dev/sdb2
UUID=a2d80068-13fa-4c57-b8a1-e716563c40d3 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

And the error lies within the grub menu.lst which contains the following entry:

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd1,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=f47c3437-dbfa-4c40-8ac5-1e531e813aa9 ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd1,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=f47c3437-dbfa-4c40-8ac5-1e531e813aa9 ro single
initrd /boot/initrd.img-2.6.22-14-generic

title Ubuntu 7.10, memtest86+
root (hd1,2)
kernel /boot/memtest86+.bin
quiet

Clearly this should be

root (hd1,0)
kernel /vmlinuz-2.6.22-14-generic root=UUID=f47c3437-dbfa-4c40-8ac5-1e531e813aa9 ro single
initrd /initrd.img-2.6.22-14-generic

Rebooting with the menu list results in a file not found within grub, which can be quite confusing to john/jane doe.

Revision history for this message
Koen (koen-beek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in ubiquity

Revision history for this message
TerryG (tgalati4) wrote :

Triaged to Confirmed. GRUB gets confused as you have noticed. You were lucky to be able to repair it. Many new users get frustrated at this stage. There needs to be better, up front, dialogs that help the new user recover from a malformed GRUB. As there are many use cases to consider, there will always be a few GRUB cases that remain pathological. Perhaps a GRUF--Grand Unified Flowchart for fixing GRUB.

Changed in ubiquity:
status: New → Confirmed
dino99 (9d9)
Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.