Kernel 2.6.32-23-generic breaks LVM on RAID and GRUB on Boot

[Kris]

Ubuntu Lucid 10.04
Kernel 2.6.32-23-generic

I recently updated the kernel to the newest version(2.6.32-23-generic) using the update manager and now I am unable to boot in to my Lucid installation.

My setup is LVM on top of a RAID 0 array. My computer had been running in this configuration since Lucid was released.

The Error Code I get on Boot is to the effect of: /dev/mapper/ubuntu-os is not available.. and then I get kicked in to Busy Box.

Once in Busy Box if I try to use mdadm to mount the RAID array I get this error:

CREATE user root not found
CREATE group disk not found

If I boot in to the live CD I can mount all of the partitions and LVM volumes, so it does not appear to be a failed drive or volume.

I have looked in the mdadm.conf, lvm config and grub config files and searched the "Google" for an answer with no-avail...

It appears that the newest Kernel(2.6.32-23-generic) is the issue.

After uninstalling the newest Kernel(2.6.32-23-generic) back to Kernel (2.6-32-22-generic) everything was back to where I left off and I am able to boot back in.

[Jay S. (jurgen-schellaert)]

Confirmed. 2.6.32-23 fails to mount / using LVM on RAID1 (actually, none of the LVM partitions on the RAID device could be mounted).
lsmod shows that the RAID modules are loaded but none for LVM. And loading them manually without having access to / is a bit of a vicious circle... Solved for now by returning to the previous kernel.

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. I have classified this bug as a bug in linux kernel package for you, Thanks again.

[Jeremy Foshee (jeremyfoshee)]

Hi Kris,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 601740

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Stefano Rivera (stefanor)]

I've seen a similar issue with 2.6.32-24. It seems to be caused by a missing initrd entry in grub.cfg? Can you check if your grub loads an initrd when booting this kernel? (press E and look for an initrd line)

[hurra (sheepshit)]

Sure it loads an initrd

[Fabian Zeindl (fabian-xover)]

Maybe related: #605720 (fixed my LVM+Raid Problems on Lucid Server)

[Fabian Zeindl (fabian-xover)]

How does on make links to bugs?

[kurt belgrave (trinikrono)]

Fabian
Just put the full url link like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/601740

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]