I found that cryptsetup still needs the custom keyscript to access the key-file on the external USB device for the encrypted root.
Without the keyscript specified in "/etc/crypttab" cryptsetup doesn't create an initrd /conf/conf.d/cryptroot file - which maybe should be the subject of another bug. For the /var and /home encrypted volumes I also found that this bug will strike if the USB device isn't inserted very early and given chance to settle - I find inserting it immediately after GRUB menu, which I have displayed for up to 10 seconds. If it is inserted only when the kernel begins running the device isn't ready in time to be mounted according to the "/etc/fstab" entry and this bug will strike. -- lucid: Failure to bring up cryptsetup devices by key files (when not using "splash") https://bugs.launchpad.net/bugs/532898 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
