Hi After the last updates (sry dont know which pkg is buggy) i cant see /dev/mapper/root anymore. But the system still works except the fsck script at boot! gentoo ~ # ls /dev/mapper/ backup control home swap gentoo ~ # gentoo ~ # cryptsetup status root /dev/mapper/root is active: cipher: aes-xts-plain keysize: 512 bits device: /dev/sda3 offset: 4040 sectors size: 83903455 sectors mode: read/write gentoo ~ # gentoo ~ # mount | grep root rootfs on / type rootfs (rw) /dev/mapper/root on / type ext4 (rw,noatime,barrier=1,data=ordered) gentoo ~ # After a resume i can see root again.. gentoo ~ # dmsetup resume root gentoo ~ # ls /dev/mapper/ backup control home root swap gentoo ~ # Reproducible: Always Steps to Reproduce: 1. Install encrypted Gentoo (~amd64 or ~x86) 2. Start System 3. ls /dev/mapper sys-kernel/genkernel-3.4.10.907 sys-kernel/gentoo-sources-2.6.33 sys-fs/udev-151-r2 sys-fs/cryptsetup-1.1.0 sys-apps/openrc-0.6.1-r1
I can confirm this. The only symptom seems to be /etc/init.d/fsck being unable to find the mapping for the root fs while booting up. Otherwise, everything works. These are the upgrades that caused the problem for me: sys-fs/cryptsetup: 1.1.0 -> 1.1.1_rc1 sys-fs-lvm2: 2.02.56 -> 2.02.64 sys-fs/udev: 149 -> 151-r2 I'm running a kernel compiled from gentoo-sources-2.6.32-r8 (non-genkernel). I tried to downgrade to cryptsetup-1.1.0 while keeping the newer versions of udev and lvm2. The problem persists.
Maybe something with udev?
It seems to be fixed in sys-fs/udev-151-r4.
(In reply to comment #3) > It seems to be fixed in sys-fs/udev-151-r4. > I added setting STARTUP property for "udevadm trigger" as it seems new lvm2 udev rules expect this to load the needed variables. So I guess this is the reason that luks is fixed, too.
