[Bug 12191] initrd breaks kernel packages 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 | initrd-tools





------- Additional Comments From random at 72616e646f6d20323030342d30342d31360a.nosense.org  2005-08-10 01:52 UTC -------
Hi,

Had the a similar problem after a new 5.04 install, my error message is slighly
different, I thought I'd post it here as it might be be useful.

I don't know if this matters, however, my install may have been slightly
different to others with regards to my RAID arrays. I wanted to preserve the
data on a few of my /dev/md devices from my former Linux install. In the past a
technique I've used is to hidden them from the Linux install, by changing the
partition types to something that Linux wouldn't try to understand e.g. CPM,
Plan9 etc., then performed the install, then changed the partition types back
and then added them to /etc/fstab. Ubuntu seems too smart for that, and detected
all my former MD devices and file systems. Not quite what I expected, however, I
was able to keep all the prior MD arrays, and format the ones where I wanted the
new Ubuntu install to go. A bit of a risk to my data, however I was careful and
got away with it.

Why do I mention this ? Well, the MD devices that I'm using weren't created
during the Ubuntu install. Although I don't think that probably would cause the
problem I'm having, I thought there may be some MD device setting or parameter
value that wasn't set on these MD devices that may have been if they'd been
freshly created during the Ubuntu install.

I can provide more details if it would help.

This is from a manual install of the .deb kernel package after I'd aborted it
during the "apt-get upgrade" :

--
marks at ubu:/var/cache/apt/archives$ sudo dpkg -i linux-image-2.6.10-5-386_2.6.10-
34.3_i386.deb
Password:
(Reading database ... 57997 files and directories currently installed.)
Preparing to replace linux-image-2.6.10-5-386 2.6.10-34.3 (using linux-image-2.6
.10-5-386_2.6.10-34.3_i386.deb) ...
The directory /lib/modules/2.6.10-5-386 still exists. Continuing as directed.
Unpacking replacement linux-image-2.6.10-5-386 ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.10-5-386
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

Setting up linux-image-2.6.10-5-386 (2.6.10-34.3) ...
File descriptor 3 left open
File descriptor 4 left open
File descriptor 5 left open
File descriptor 6 left open
File descriptor 7 left open
    Finding all volume groups
  No volume groups found
/usr/sbin/mkinitrd: /dev/evms/.nodes/hdc5: Cannot find LVM device
Failed to create initrd image.
dpkg: error processing linux-image-2.6.10-5-386 (--install):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 linux-image-2.6.10-5-386
marks at ubu:/var/cache/apt/archives$
--

I'll try out some of the suggested fixes in the prior posts.

Thanks,
Mark.

-- 
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.