* Paul Menzel <pm.deb...@googlemail.com> [Mon May 31, 2010 at 06:41:45PM +0200]:
> yesterday I upgrade my Debian Sid/unstable system after over a > week. Several core packages were upgraded by doing this as lvm2, > mdadm, initscripts, initramfs-tools. I have a standard md RAID1 > setup with LVM over it. Furthermore there is a partition for > `/boot` and a LUKS encrypted `/`. > Now I am seeing the following behavior. After GRUB2 started > (`linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/lvm-root …`) I > first get to see a lot of lines > sys/devices/virtual/block (some incremented number in 80??) > (this is from memory). Afterward I am asked for the LUKS > passphrase. After that nothing happens. Just a lot of – according > to my Web research unrelated –udev-work messages about `NAME` and > `SYMLINK` stuff and nothing happens. Then after six to ten minutes > booting finally continues. [...] > Is that related to the `root` argument passed in GRUB to `linux`. > In [1] the solution is to use a UUID instead of the path. Though I > did not find how I can find out the correct value for my RAID > device or LVM partition. Executing 'blkid /dev/mapper/lvm-root' should provide you the UUID of the LVM partiton for use as root=UUID=... argument. regards, -mika-
signature.asc
Description: Digital signature
