Bug#582177: initramfs-tools: fails to load ramdisk on boot; system with RAID & CRYPTO; udev problems?

[maximilian attems <max@stro.at>]

On Tue, May 18, 2010 at 05:29:17PM -0400, C. Cropper wrote:
> Package: initramfs-tools
> Version: 0.94.4
> Severity: important
> Tags: squeeze
> 
> Very recent changes to the initramfs-tools have caused my system to fail to
> "load ramdisk" at boot.  I have to boot the system with the backup initrd
> image. I have checked with "rootdelay=10"--no change.  The problem does not
> appear to be related to grub.  When I boot the machine and watch the mass of
> kernel data fly by I get the impression that udev is not "working" or has
> somehow changed from mid-February till now (all of these problems first
> appeared in late Feb/early March of 2010).  I am only using the squeeze dataset
> without items from experimental or other sources.
> 
> My system is different from most in that my / partition is inside a luks crypto
> container which is then on a RAID 6 volume.  The /boot is on an unencrypted
> RAID 1 volume.  Each physical disk has a separate bios_grub partition (128k)
> and the partition tables are GPT.
> 
> As I said before this above setup WORKS and I have a 6TB system where the
> "boot" disk can fail (I tested this) and the system comes back alive.  For
> whatever reason, recent changes to initramfs-tools 1) make it not "see" the
> hard drives or any USB devices for that mater, 2) fails to start the RAID
> devices, and thus 3) the kernel panics at about 2secs into the boot sequence.
> 
> Thank you for all your work.  Squeeze really is shaping into a mighty force.
> 
> C. Cropper

thanks for your feedback, will need more data to see whats gone wrong.
please post output of:
sh -x mkinitramfs -v -o /tmp/foo

dpkg -l cryptsetup

and

mount

thank you and sorry.