LVM not bootable with 2.6.22 kernel after Gusty upgrade

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. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-source-2.6.22.

Hi. I experienced this bug, too. Package: linux-image-2.6.22-14-generic, platform: x86-64. Configuration: root-partition on LVM on RAID-1.

It did work with feisty's 2.6.20 kernel and actually right now I'm typing these words on the same machine with gutsy on feisty's 2.6.20 kernel.

Hi there,

I finally had some time to deal with this. This morning I booted into the 2.6.20 kernel and did the ol' "sudo apt-get update && sudo apt-get dist-upgrade -y". After everything was updated I ran the following "sudo update-grub" and then "sudo update-initramfs -k all -c". I now get past this particular problem. I did run into some additional issues, however I believe they are not related to this bug. If I need additional help I would seek the appropriate channels.

As a side note, I am not sure if this bug should be closed or not. After I ran into this I did a big of digging and found similar problems with the initramfs, which subsequently led me to my solution. This leads me to believe that one of the packages is not allowing the initrd to be created correctly. Manually generating it is not for novice or casual user.

It seems like update-initramfs and depmod steps were forgotten somewhere in the upgrade procedure.

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Hi Leann,
   I'm responding to you rather than on the bug report page because
I'm not sure if this relates directly to this bug or not. I solved
the problem, for my system, of not being able to boot after a kernel
upgrade. I'm now running Hardy Heron with the 2.6.24-19 kernel and
have successfully upgraded with each kernel offered on the Ubuntu
updates.

   With each kernel upgrade, I have to edit my menu.lst file before
rebooting. Attached is part of the menu.lst file that resulted from
the upgrade from Feisty to Gutsy which caused the first incident of
not being able to boot. A wrong "root=" id was placed in the file by
the upgrade process. Now, whenever the kernel is upgraded I edit
menu.lst before rebooting and change the "root= UUID =..." back to
"root=/dev/sda3". My guess is that the problem happens because my
machine is dual partition with Windows XP on one partition and Ubuntu
on the other.

   The manual editing process is no problem, now that I know what the
problem is.

   Thanks for all you do.

Lynn

Portion of menu.lst after upgrade to Gutsy Gibbon:

## ## End Default Options ##

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,1)
kernel /vmlinuz-2.6.22-14-generic root=UUID=7c9d822a-8703-4551-91a9-
a50989ee066f ro quiet splash
initrd /initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,1)
kernel /vmlinuz-2.6.22-14-generic root=UUID=7c9d822a-8703-4551-91a9-
a50989ee066f ro single
initrd /initrd.img-2.6.22-14-generic

title Ubuntu 7.10, kernel 2.6.20-16-generic
root (hd0,1)
kernel /vmlinuz-2.6.20-16-generic root=/dev/sda3 quiet splash
initrd /initrd.img-2.6.20-16-generic
quiet

title Ubuntu 7.10, kernel 2.6.20-16-generic (recovery mode)
root (hd0,1)
kernel /vmlinuz-2.6.20-16-generic root=/dev/sda3 single
initrd /initrd.img-2.6.20-16-generic

### END DEBIAN AUTOMAGIC KERNELS LIST

On Aug 29, 2008, at 1:14 AM, Leann Ogasawara wrote:

> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for
> the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team
> would
> appreciate it if you could please test this newer 2.6.27 Ubuntu
> kernel.
> There are one of two ways you should be able to test:
>
> 1) If you are comfortable installing packages on your own, the linux-
> image-2.6.27-* package is currently available for you to install and
> test.
>
> --or--
>
> 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
> 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.
> Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
> You should then be able to test via a LiveCD.
>
> Please let us know immediately if this newer 2.6.27 kernel resolves
> the
> bug reported here or if the issue remains. More importantly, please
> open a new bug report for each new bug/regression introduced by the
> 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also,
> please
> specifically note if the issue does or does not appear in the 2.6.26
> kernel. Thanks again, we really appreicate your help and feedback.
>
> ** Tags added: cft-2.6.27
>
> --
> LVM not b...

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

Hi Jeremy,
  I'm sorry to take so long to get back to you, but I only just did the
upgrade to 9.04. In fact I did the successive upgrades from Hardy to
Intrepid then to Jaunty in one evening. (I had been thinking of sticking
with an LTS version, but changed my mind.) The bug you mention was
still present in the upgrade to Intrepid, but it went away upon the
upgrade to Jaunty. I did NOT have to edit menu.lst after the upgrade to
Jaunty. Thanks!
  The only issue that re-appeared for me was a vpn issue I encountered
upon upgrade from Gutsy to Hardy. After upgrading to Hardy my vpn would
constantly disconnect a minute or so after connecting. I solved this
problem by reverting to the Gutsy version of vpn. Looks like I'll need
to do that again.
  Thanks for your work on the boot issue.

Lynn

-----Original Message-----
From: Jeremy Foshee <email address hidden>
Reply-to: Bug 153144 <email address hidden>
To: <email address hidden>
Subject: [Bug 153144] Re: LVM not bootable with 2.6.22 kernel after
Gusty upgrade
Date: Thu, 09 Jul 2009 00:46:35 +0000

Unfortunately it seems this bug is still an issue. Can you confirm this
issue exists with the most recent Jaunty Jackalope 9.04 release -
http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know
your results. Thanks.

Marking this Fix Released against the kernel based on Lynn's feedback. Thanks!