At boot time, the system asks for a password to unlock and mount this filesystem. When I provide the password I get an
error message (something about modprobe not finding or loading a module).
what kind of encryption are you using ? and is the module available at boot time?i personally use serpent/xts so i compile both xts and serpent not as modules but as part of the kernel. another important thing is did you remake initrd after setting up your encrypted file system? something like: mkinitrd -d /dev/mapper/root -f "dm luks"
The other thing is I see password - KDE daemon window asking me for a password to unlock the encrypted file system that is already mounted! i don't know exactly what you mean but if it is asking you for a password then maybe it's not mounted?
Now, if I do not provide a password to unlock the crypto_luks file system at boot time, the system eventually completes booting up and I can log in and of course the encrypted file my question here will again be on your setup. do you have another partition with linux installed on it? i mean the partition you booted into when you were setting you your encrypted partition? if so when decrypting your new partition fails linux usually "resumes" from your other partition. you should pass 'noresume' flag to the kernel before booting it during the grub menu and see if it changes anything.
If I go to Dolphin and click on the encrypted file system and provide the password it fails and I cannot mount this file system!
Anyone experience this or have an idea where to look to fix this? i'm using 11.3 x86_64 (with 2.6.36 custom compiled) and it is working fine for me. again though it would be handy to know what kernel you are booting from the actual errors etc...
what exactly is the error? thre is a really good guide at : http://en.opensuse.orgSBD:Encrypted_root_file_system i'd like to bring this part to your attention though: "Note: I had to use: "yast2 --> system --> editor for /etc/sysconfig --> system --> kernel --> initrd_modules --> add dm-mod dm-crypt aes_i586 blkcipher" to enable the right modules while booting. Maybe you also need the "lrw" module, if you wanna use a cipher like aes-lrw-benbi. " have you taken this step? i don't know much about pam of if you need to do this but have you added pam or pam_mount in the etc/sysconfig editor and remade initrd? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org