[pkg-cryptsetup-devel] Bug#548900: udev update killed my LVM2 boot (sed: not found)

[Sheridan Hutchinson]

2009/9/29 Jonas Meurer <jonas at freesources.org>:
> hello sheridan,
>
> please try to provide more detailed information. how did you break your
> system? was it caused by a udev upgrade? or a cryptsetup upgrade?

Hello there!

I started to write a long complicated email about how I found out what
the problem was and my reasoning, but instead I'm going to keep it
brief.  Thank you to those of you who helped me get back into my
machines.

The problem was that the busybox package was not installed (contrary
to my initial report) on either of my machines when the initramfs was
built on 30/09/09.  The last time that the busybox package was
installed on the machines was 04/09/09.  The last time that a
previously working initramfs was built was 02/09/09, prior to the
removal of busybox.  See #492560 as to why I removed it.

I did not realise that removing the busybox package didn't immediately
trigger an initramfs rebuild trigger (I expected it to but didn't
verify it).  Hence when it rebuilt on 30/09/09, it did not go in the
image and I could not boot my machines.

Summary:
a.) udev is nothing to do with this, it merely correctly triggered an
initramfs rebuild
b.) adding or removing of busybox should cause an initramfs trigger to rebuild
c.) busybox should be a hard dependency on lvm2, or cryptsetup, as
INDISPENSABLE for people with encrypted LVM2's to be able to boot
d.) what is the next move to solve this
e.) This cannot be true:

From: Bastian Blank <waldi at debian.org>
To: 492560-done at bugs.debian.org
Subject: fixed
Date: Mon, 17 Aug 2009 23:24:01 +0200

Version: 2.02.51-1

This bug got fixed by using the new dmsetup splitnames command.

Bastian


-- 
Regards,
Sheridan Hutchinson
sheridan at shezza.org