doesnt write correct uuid

Bug #385021 reported by sojourner on 2009-06-09
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: grub2

karmic koala amd64 , grub2 wrote incorrect uuid for my boot drive , also even though the installer reported finding 2 of my three other installs it only added karmic to the menu.lst . note the box has 6 drives , 4 with different installs 2 data only , 3 installs are ubuntu (hardy ,jaunty ,karmic ) 1 is open suse , each is on a seperate drive (not partition) , suse is the install not found by the grub2 installer , all installs were in the grub menu.lst that the installer replaced . I was able to recover my karmic install by copying the correct uuid from a backup to the menu.lst written by grub2 using a live cd.after correcting the uuid grub2 will boot both by chainloading and by selecting a kernel from the menu (corrected uuid there also).

ProblemType: Bug
Architecture: amd64
Date: Mon Jun 8 21:51:55 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: grub2 1.96+20090523-1ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SourcePackage: grub2
Uname: Linux 2.6.30-8-generic x86_64

sojourner (itsmealso2) wrote :
sojourner (itsmealso2) wrote :

the incorrect uuid that grub2 wrote came from my jaunty install on the 1st bootable (sdb) drive on my system , I installed grub2 from my karmic install which is on the 3rd bootable drive on my sys (sdd) . I believe what is happening is that grub2 is picking up the first bootable drives uuid rather than the drive it was installed from , even though it installs its menu.lst on the correct drive (the one you installed from ) .

So basically, GRUB2 is looking on the wrong partition/drive for the menu.lst?

sojourner (itsmealso2) wrote :

no when it is installed it writes the menu.lst in correct place , the /boot/grub directory of the place it was installed from . But it writes the uuid of the first bootable drive on the system as the drive to boot from , when booting it finds the menu.lst ok but then attempts to boot from the wrong drive and not finding the correct kernel , initrd and vmlinuz it issues a file not found error . editing the menu.lst to use the correct uuid allows the system to boot . Note ! this was installed from Karmic Koala and is not the error warned about for jaunty . This may only affect systems with multiboot installs on seperate drives (or perhaps partitions) where it is installed from a drive that is not the first bootable drive on the system .Note 2 ! during install grub2 reported finding the other 2 Ubuntu installs on my box but did not write the boot stanzas into the menu.lst to allow them to boot even though those installs were in the original menu.lst that it replaced .

sojourner (itsmealso2) wrote :

additional info , upon examining /boot/grub/grub.cfg , the correct uuid was used there even though grub2 wrote the wrong uuid in the menu.lst it generated , including the chainloader line . so here is what seems to happen , on boot grub2 goes to the correct drive
to get the menu.lst but then goes to the incorrect drive to get grub.cfg resulting in the file not found error .

Dimitrios Symeonidis (azimout) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in grub2 (Ubuntu):
status: New → Incomplete
MFHD (hal9000) wrote :

Same problem with 9.10 fresh install + all updates as of Jan 23, 2010.

Wrong UUID in /boot/grub/grub.cfg:

menuentry "Ubuntu, Linux 2.6.31-17-generic (on /dev/sda5)" {
 insmod ext2
 set root=(hd0,5)
 search --no-floppy --fs-uuid --set 64e579fa-8835-4bae-841f-e19f7e25aaa3
 linux /boot/vmlinuz-2.6.31-17-generic root=UUID=054dc5ad-8f1f-4a2c-aa31-b8e3b278d476 ro quiet splash
 initrd /boot/initrd.img-2.6.31-17-generic
}

First UUID (search line) is correct. Second UUID is from the partition from which grub-mkconfig was run.
This is clearly a severe grub2 bug, please assign for urgent fixing!

Skip S. (skip5840) wrote :

Has this been corrected in 10.04.
I have a problem with this on dual boot xp pro on 2 hdd in system. Both entries of choosing xp show on boot menu but choosing either goes to a black screen and then the grub shows again. This occurred a couple weeks after I put 10.04 on new hdd.
Does not seem to be an answer on forums or google--that WORKS.

Launchpad Janitor (janitor) wrote :

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

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers