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

[Andreas von Heydwolff]

On 2010-09-14 22:26, Alexander Kurtz wrote:
> Am Dienstag, den 14.09.2010, 21:28 +0200 schrieb Andreas von Heydwolff:
>>     My /etc/crypttab reads
>>
>> md1_crypt UUID=3a10eb55-2dd8-4846-97e5-74649abf234f none luks
>> md2_crypt UUID=e78a6bea-cafb-41a7-89e9-03e999b38d6c none luks
>
> Just some thoughts: What happens if you
>
>   * try `/dev/disk/by-uuid/' instead of `UUID='
>   * try the raw devices (presumably /dev/md1 and /dev/md2)
>   * try the symlinks to the devices (presumably /dev/md/1 and /dev/md/2)
>     (note that you *might* need the new mdadm version for that to work)


Hm. All three variants yielded the same result:

# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
cryptsetup: WARNING: invalid line in /etc/crypttab -
cryptsetup: WARNING: invalid line in /etc/crypttab -


Then I followed this previously mentioned error message:

# update-grub
Generating grub.cfg ...
Found background image: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
   Found duplicate PV c1Evvwvx3ZfBwDWRyhhI0nY864wtPZ3o: using /dev/dm-11 
not /dev/dm-0
Found Debian GNU/Linux (squeeze/sid) on /dev/sda2 [my rescue system]
done

# blkid | grep Evv
/dev/mapper/md1_crypt: UUID="c1Evvw-vx3Z-fBwD-WRyh-hI0n-Y864-wtPZ3o" 
TYPE="LVM2_member"
/dev/mapper/vg-md1dm0: UUID="c1Evvw-vx3Z-fBwD-WRyh-hI0n-Y864-wtPZ3o" 
TYPE="LVM2_member"

# l /dev/mapper/
insgesamt 0
crw------- 1 root root 10, 59 14. Sep 20:59 control
lrwxrwxrwx 1 root root      8 14. Sep 20:59 md1_crypt -> ../dm-11
lrwxrwxrwx 1 root root      8 14. Sep 20:59 md2_crypt -> ../dm-12
lrwxrwxrwx 1 root root      7 14. Sep 20:53 vg-md1dm0 -> ../dm-0

Perhaps this is the source of confusion? Identical UUIDs for the 
encrypted RAID1 pv and the vg that emerges when the pv has been unlocked 
with cryptsetup? This is the configuration on the running system on 
which md1_crypt and the vg had been unlocked and started manually. Do I 
have to remove one symlink, either to dm-0 or to dm-11 in order to 
create a functioning initramdisk? I had to unlock md1_crypt twice, once 
from within busybox and once after exiting lvm and busybox.

What else could I try, or what further info from my system might be helpful?

Andreas