© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> /etc/fstab:
> /root/e_data /root/e crypto_LUKS defaults 0 0
What are you expecting this to do? crypto_LUKS is not a filesystem. There's no way this is going to do anything meaningful.
> cryptsetup-luks 2:1.6.1-1ubuntu1
There is no such package in Ubuntu.
> 2. The password prompt created by cryptsetup exhibits
> similar behavior but can be worked around by holding the enter key.
cryptsetup does not at boot prompt for passphrases in Ubuntu. It communicates with plymouth for prompting. Please provide information about the plymouth configuration on your machine (including /proc/cmdline).
> 1. With ecryptsfs:
> /etc/fstab:
> /root/ecfs_data /root/ecfs ecryptfs rw,exec,suid 0 0
ecryptfs is designed for cases where an encrypted filesystem is *not* mounted at boot, but instead mounted at user login (and unmounted at user logout). I have no idea what the behavior is of ecryptfs if used from /etc/fstab. How is ecryptfs prompting for a passphrase? If it is bypassing plymouth, then this is a bug in ecryptfs-utils, and the error you're experiencing is because it's fighting plymouth for the console. Plymouth owns the console exclusively at boot.