[Bug 12191] new 2.6.10-34.3 kernel packages break with LVM error

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=12191
Ubuntu | linux-meta





------- Additional Comments From andrelmoraes at gmail.com  2005-06-29 03:53 UTC -------
I've banging my head around this problem twice in the last 40 days:

First time I've got this problem I was upgrading to linux-image-2.6.10-5-k7
(2.6.10-34.2) from a stock install. No action seems to solve the problem. Since
I'll reinstall the system shortly after, I didn't bother to solve.

After clean install + updates *during install*, my new Ubuntu system boots up
running fine with linux-image-2.6.10-5-k7 (2.6.10-34.2). New security update
linux-image-2.6.10-5-k7 (2.6.10-34.3) and guess what? The kernel image upgrade
problem shows up its ugly face.

After some research, I've found a solution that works well for me. The problem
seems to be related to settings of the new image. In this thread
(http://ubuntuforums.org/showthread.php?t=25045&highlight=mkinitrd) on
UbuntuForums, the poster runs over the same issue and managed to solve it
changing the ROOT parameter on /etc/mkinitrd/mkinitrd.conf from ROOT=probe to
ROOT="/dev/<your_root_device_here> <root_device_filesystem_type>" (in my case,
ROOT="/dev/hda1 ext3").

I believe that the new kernel image change this parameter in mkinitrd.conf to a
default value and it brokes the mkinitrd step on config of newly installed package.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.