bug 319982 and bug 287879 have been fixed now and I'm still not prompted for my encryption passphrase at boot. After reading over comments by other people in those bugs, I've noticed that my initrd does not contain a file "conf/conf.d/cryptroot". This file seems to be what tells the initrd which devices to try to unlock.
Each time my initrd is generated I get two warnings about invalid lines: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-2.6.29-020629rc5-generic cryptsetup: WARNING: invalid line in /etc/crypttab - cryptsetup: WARNING: invalid line in /etc/crypttab - update-initramfs: Generating /boot/initrd.img-2.6.28-8-generic ... My /etc/crypttab looks like this: sda2_crypt /dev/disk/by-uuid/52fd0ccb-c1b7-4786-b242-b0c39b83d643 none luks Why does it say invalid line twice? And why is this line invalid now but wasn't before mid-January when this started happening? What does a valid line look like now? Mine seems to be in agreement with what the man page for crypttab says. Note that I haven't modified this file myself - something must have changed in how this file is parsed. Can *someone* please give me some suggestions?! -- initrd no longer activating encrypted filesystems https://bugs.launchpad.net/bugs/318892 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
