update-grub keeps on converting my root device to a uuid

Bug #54042 reported by Michael Bienia
This bug report is a duplicate of:  Bug #62195: edgy update-grub destroys kopt. Edit Remove
4
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
New
Undecided
Unassigned

Bug Description

After the upgrade to grub 0.97-11ubuntu7 upgrade-grub converts everytime my root-device from my kopt line to a uuid. I'm using a self-compiled kernel without a initrd. My kopt line looked like
# kopt=root=/dev/sda5 ro
but after running update-grub it's always converted to
# kopt=root=UUID=bb90f216-5cfb-442a-a258-7afc6f3030ad ro
The problem is my kernel doesn't boot with a UUID as root-device. Changing it back to root=/dev/sda5 works but I can't get this change permanent as update-grub keeps overwriting it.

Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :

It gets worse... even with the default ubuntu kernel, if your root device is on an LVM partition, you can no longer boot either.

This has already been fixed in debian:

http://packages.debian.org/changelogs/pool/main/g/grub/grub_0.97-13/changelog.html#versionversion0.97-5

Revision history for this message
lithorus (lithorus) wrote :

I have the same problem, but with /dev/md0. I basically have to edit the grub startup menu everytime I boot my machine.

Revision history for this message
Pascal de Bruijn (pmjdebruijn) wrote :
Revision history for this message
Walter Tautz (wtautz) wrote :

still a problem in feisty. The weired part is of kopt root=UUID=xxxxxbbsss ro then it will not get updated
with update-grub runs, unless one puts in kopt root=/dev/hdawhere / is mounted on /dev/hda it gets
over written with the UUID value, however, if one makes up some crap like

kopt root=axyaljdfljdglkj ro

it will not get updated.....

clearly what should happen is # kopt should never be modified, after all it's suppose to be edited by
humans. If a human makes a mistake so be it. The program shouldn't presume to do something for me.

Second it could support some kind of method option, i.e., if I say kopt root=UUID then it will make a point
of looking up the UUID of the root device, presumably via vol_id and substitute that value for the various
cmdline parameters for the kernels found in /boot and not overwrite the option kopt!

Revision history for this message
Hauke Zuehl (hzuehl) wrote :

Just a question:
Where do I have to look to fix that bug?

Regrads,
Hauke

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.