Hello all, I installed openSUSE 13.1 on a GPT/UEFI system with Windows 8.1 and an encrypted openSUSE 13.1 LVM (/boot: /dev/sda9, LVM: /dev/sda10) and an encrypted /home/myusername filesystem (/dev/sda11, opened via pam_mount). After a while, I found in 'dmesg' logs, that a ext4 filesystem is corrupted. I wanted to clear this situation with the recovery stick and found some problems. I did the following: * booted with openSUSE 13.1 64Bit (openSUSE-13.1-DVD-x86_64.iso written on an USB stick) (I wonder, why the Grub screen from USB stick does not show the function key menus and so I have to use English keyboard layout) * I checked the /boot filesystem (/dev/sda9, ext4 => no errors) * Now I tried to open the encrypted LVM /dev/sda10 with cryptsetup I got this error: Rescue:~ # cryptsetup luksOpen -v /dev/sda10 rootlvm Enter passphrase for /dev/sda10: /dev/mapper/temporary-cryptsetup-1697: mknod for temporary-cryptsetup-1697 failed: Read-only file system Failed to open temporary keystore device. Command failed with code 5: Failed to open temporary keystore device. The root filesystem in recovery itself is not Read-only, but /dev/mapper is read-only. I found a simple way to create an writable /dev/mapper directory: Rescue:~ # mv /dev/mapper /dev/mapper.orig && mkdir /dev/mapper The downside of this simple way is, that "cryptsetup luksClose" does not work. The root filesystem had no errors. But instead the /home/myusername filesystem (/dev/sda11) was corrupted: Rescue:~ # cryptsetup luksOpen -v /dev/sda11 home Rescue:~ # fsck -f -C -t ext4 -D /dev/mapper/home (a lot of errors) This is my /etc/security/pam_mount.conf.xml:. I changed the original YaST entry <volume fstype="crypt" user="myusername" path="/home/myusername.img" fskeypath="/home/myusername.key" fskeycipher="aes-256-cbc" fskeyhash="md5" cipher="aes-cbc-essiv:sha256" options="loop" mountpoint="/home/myusername"/> to <volume fstype="crypt" user="myusername" path="/dev/disk/by-uuid/<some-uuid>" options="loop" mountpoint="/home/myusername"/> My questions: * Is the missing function key menu bug on some systems/displays when booting with the installation DVD/USB media known? I had this on different systems. Any work-arounds? * Why is /dev/mapper read-only in recovery and thus "cryptsetup luksOpen" does not work? * My setup with an encrypted /home/myusername and a custom pam_mount configuration is probably not officially supported, so problems here may not be seen as a bug. Does anyone has a tip for me how to do this setup correctly? Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org