Marco d'Itri (26.04.2011, 15:33:00): >Because they cannot be relevant, and anyway your problem happens in the >initramfs.
So I first had a look there and enabled debugging. It looked like the lvm2 script didn't find any VG with udev-168-1: ========== | + /scripts/local-top/mdadm | Begin: Loadingdone. | + [ -e /conf/param.conf ] | + /scripts/local-top/lvm2 | Volume group "vg01" not found | Skipping volume group vg01 | Unable to find LVM volume vg01/lv01 | + [ -e /conf/param.conf ] | + /scripts/local-top/cryptroot | + [ -e /conf/param.conf ] ========== But when I started the same script on the initramfs console, the VG and LV were found and activated, so I assumed a timing issue. I then added a "sleep 10" before the activation command in the above script and on the next reboot, the system booted again fine - although with this 10 s delay ;-) I am not very familiar with how exactly initrd is working, what starts first, etc. - but somehow the new udev causes a confusion in the right running order or at least timing. Maybe it takes longer to start… or whatever. Is it possible to change this somehow without this additional "sleep"? Steve -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
