Bug#583917: Bug#594472: grub-pc: scary messages and very long boot time after upgrade

[Dh H]

So this looks a bit like there are two erros:
 1) mdadm is broken in 3.1.2 and brings up these errormessages.
 2) Grub2 seems to be broken, as it does not start crypto,
consecutively failing to bring up LVM

The only thing I dont understand is why it is only us two experiencing this.

To test, I have set up a virtual machine with KVM, for that I created
two lv's with 10G each and started kvm with

kvm -hda /dev/mapper/testdisk1 -hdb /dev/mapper/testdisk2 -cdrom
<yesterdays alpha netinstall.iso>

then I partitioned both disks with two partitions
  partition 1 : 250MB
  partition 2 : all remaining

with these two 'disks' I set up two raid1 sets
md0 = (hda1, hdb1)
md1 = (hda2, hdb2)

md0 is used for /boot as ext3

md1 I encrypted giving md1_crypt

md1_crypt is then used for LVM as volume group "x" which I have
partitioned as follows
x-swap 1GB swap space
x-root  all remaining for / as ext3

The installation process went all fine without any problems. (apart
from some minor quirks that should be reported somewhere else)

When rebooting I have the same behaviour as what you described first;

The system complains about the missing vg and comes up with a lot of
/sys/devices/virtual ... messages, then asks for the disk-passphrase,
goes into a longer thinking period and after another block of
/sys/devices/virtual/... messages the vm actually boots without any
further problems.