Basically this is done according to the following guide: https://help.ubuntu.com/community/EncryptedFilesystemHowto3
Here's how to reproduce (even though this reproduction is actually worse than what I've seen before, now I'm afraid of rebooting my karmic box because it won't come up again): Installed karmic alpha 2, and then dist-upgraded everything. apt-get install mdadm apt-get install cryptsetup mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sdb1 missing cryptsetup luksFormat /dev/md0 cryptsetup luksOpen /dev/md0 md0_crypt mkfs.ext3 /dev/mapper/md0_crypt mkdir /t /etc/crypttab: # <target name> <source device> <key file> <options> md0_crypt /dev/md0 none luks # /etc/fstab: add this /dev/mapper/md0_crypt /t ext3 defaults 0 2 /etc/mdadm/mdadm.conf add this (change uuid): ARRAY /dev/md0 level=raid1 num-device=2 UUID=c0357b84:18cb2297:8282d032:d2636449 That results in it just waiting for the volume, doesn't ask for the crypt password. Then if you press esc, it drops to regular console and you're allowed to enter the passphrase (cosmetically broken, but seems to work to enter the passphrase). Then after the crypted volume has been opened, nothing more happens. Won't even go to rescue mode if that's chosen. Will attach PNGs from the boot process. -- Passphrase request at bootup doesn't work properly https://bugs.launchpad.net/bugs/516524 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
