Grub assigns the wrong hard drive number in menu.lst

Bug #518266 reported by Garry Leach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: grub

I am still using grub 1, version 0.97-29ubuntu59.

This problem occurred with both Mythbuntu 9.04, & newly installed 9.10.

I have the following partitions:
hd0,0 37GB for a backup/test Mythbuntu system (currently 9.04); boot flag is here.
hd0,1 37GB for the live Mythbuntu system (currently 9.10); this has the mount point "/" assigned.
hd0,2 200 MB; linux swap
hd1,0 300 GB; Myth recordings & videos; this has the mount point "/mnt.mythtv" assigned.
hd2,0 930 GB; Myth recordings & videos; this has the mount point "/mnt.mythtv2" assigned.

Whenever the system is updated with a new kernel, & the install program generates a new menu.lst, the menu.lst shows root (hd2, 0 ), instead of (hd0,1) for the menu lines "root".

I am not sure whether it gets the right UUID for the menu lines beginning "kernel", as it is a while since I allowed automatic creation of menu.lst. However, I think that it does.

Also, it never creates an entry for the back-up system on (hd0,0).

My usual solution is to refuse to allow the automatic creation of menu.lst

Thanks for your help, Garry.

ProblemType: Bug
Architecture: i386
Date: Sun Feb 7 13:51:49 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: grub 0.97-29ubuntu59
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: grub
Uname: Linux 2.6.31-19-generic i686
XsessionErrors: (polkit-gnome-authentication-agent-1:2975): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Garry Leach (garry-leach) wrote :
Revision history for this message
dino99 (9d9) wrote :

This is no more a supported version; and grub legacy upstream is also stopped, only receiving possible random fixes locally

Changed in grub (Ubuntu):
status: New → 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.