Hi Andreas, let's try to keep this short, this bug report is already long enough:
Am Samstag, den 18.09.2010, 01:38 +0200 schrieb Andreas von Heydwolff: > ii cryptsetup 2:1.1.3-3 > ii lvm2 2.02.66-3 > ii mdadm 3.1.4-1+8efb9d1 Good. > # update-initramfs -u > update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 > > ... and nothing else as output. Even better. > the initramfs came up but I got > ALERT! /dev/mapper/vg--md1dm0-slash does not exist > and ls -l /dev/dm* was empty, > ls -l /dev/mapper showed only /dev/mapper/control Not so good. Ok, let me summarize: * You did have[1] the problem that was caused by mdadm bug #583917[2]. However, after upgrading to mdadm 3.1.4 that is solved. * You did have[3] some issue with cryptsetups initramfs hook. However, for some reason that is gone now. * You do still have the problem that for some reason your root file system is not correctly mounted during initramfs stage. Everything correct so far? If so we can focus on tackling the last point! Best regards Alexander Kurtz [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#44 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583917 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#124
signature.asc
Description: This is a digitally signed message part
