Ubuntu

LVM support forgotten in newest kernel update?

Bug #54189 reported by jaek
8
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

I am an LVM user running edgy and the last kernel update seems to have overwritten my /boot/grub/menu.lst file so it no longer boots my machine. There are no LVM specific options left and it fails to boot.

This is how it looks right now for a single kernel entry.

title Ubuntu, kernel 2.6.17-5-686
root (hd0,0)
kernel /vmlinuz-2.6.17-5-686 root=UUID=ee2d2713-6ae2-490d-8dde-c68eec6d2831 ro quiet splash
initrd /initrd.img-2.6.17-5-686
savedefault
boot

The kernel installer script did not make a backup of this file before it munged it so I can not figure out what it used to look like.

Revision history for this message
Andreas Simon (andreas-w-simon) wrote :

Same here. The boot hangs because the rootfs which is on LVM could not be found.

The new UUID stuff doesn't seem to work with LVM volumes.

Revision history for this message
Andreas Simon (andreas-w-simon) wrote :

I forgot to mention:
The last message when the system hangs while booting is
"Waiting for the root file system".

Revision history for this message
jaek (tw1ggz) wrote :

> I forgot to mention:
> The last message when the system hangs while booting is
> "Waiting for the root file system".

Same here. I have attached my mutilated menu.lst. BTW, it also got my UUID wrong... so I changed it to match my UUID, but it still didnt work.

Aside note: why the heck didn't the menu.lst generator back up before it silently overwrote my working copy!!! Now I cant restore it if I wanted to...

Revision history for this message
jaek (tw1ggz) wrote :

My work machine is dead in the water... is there any way to get a developer to actually look at this ticket?

Revision history for this message
neuschnee (nhewitt) wrote :

To fix, if you know your LVM info, boot, jam escape to get to the grub menu, select the kernel you want, press "e" to edit the line...

Then, change (as an example) "root=UUID=ee2d2713-6ae2-490d-8dde-c68eec6d2831" to "root=/dev/mapper/lvm_group-lvm_volume" ... with lvm_group and lvm_volume changed to your info. Then press return.

If you don't know what your root is called, you can use a livecd and look at the /dev/mapper/ directory.. mine is /dev/mapper/chango-root, as an example...

Revision history for this message
jaek (tw1ggz) wrote :

Yes, that fixed it. BTW, it is /dev/mapper/Ubuntu-root if you selected to use LVM for your root partition during installation.

Revision history for this message
ryanmbruce (ryanmbruce) wrote :

https://launchpad.net/distros/ubuntu/+source/grub/+bug/54002 - Duplicate?

If so, make sure to copy the helpful parts of this bug into the older one.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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