Grub wrong kopt entries in edgy

[Adrian R Goalby]

Binary package hint: grub

Grub menu.lst, kopt and kopt_2_6 need merging for Edgy.

On a fresh Edgy install the menu.lst for Grub contains something like:-

# kopt=root=UUID=9b63a575-ba40-4bf3-b5a4-e421c02c3b02 ro
# kopt_2_6=root=/dev/hda1 ro

My computer needed additional mem option, which I added to the kopt_2_6 line, as it seemed to be the one used to generate the real entries further down. This produced:-

# kopt=root=UUID=9b63a575-ba40-4bf3-b5a4-e421c02c3b02 ro
# kopt_2_6=root=/dev/hda1 ro mem=242688K

After problems with a more complicated system I found that UUID's are now being used to identify partitions in fstab, so the purpose of the kopt line is to specify the root partition to the kernel by UUID. But this is not happening because the kopt_2_6 line is overriding the kopt line.

So I have now combined the lines to give:-

# kopt=root=UUID=9b63a575-ba40-4bf3-b5a4-e421c02c3b02 ro mem=242688K

I have run update-grub, and this seems to work properly.

For Edgy to use UUID's as intended there should be an update script to perform this merging of kopt and kopt_2_6. It should preserve any additional manually added options. Having read several of the other Grub bug reports, I think the user should also be explicitly informed that the change is being made and maybe asked for confirmation.

This bug report may be related to other Grub bugs, eg.Bug #73090, but I am concerned about an Edgy situation, not an upgrade from Dapper or to Feisty. I would also like it to be confirmed (for myself and others) that the last kopt line above (or similar), with no kopt_2_6 line, is the correct Grub configuration for Edgy.

[Tormod Volden (tormodvolden)]

It would make more sense that the kopt_2_6 line uses UUID, instead of the kopt line.

[Tormod Volden (tormodvolden)]

I think this is missing.