I too am experiencing issues with multiple luks partitions. Under a
single LVM I have three crypt-volumes. One for /, /home, and swap. All
require passwords.
I have read the man page for crypttab and my entries are NOT using
noearly; therefore all three partitions should be prompted for and
This, BTW, was at one point working in Karmic, but recently broke (I
don't remember exactly what updates that occurred with) and also showed
up when I re-installed with just Lucid since it had otherwise become
stable enough for near normal use (and more in depth testing).
--
System frezes after
I have read the man page for crypttab and my entries are NOT using
noearly; therefore all three partitions should be prompted for and asked
in the INITRAMFS. Only / is asked for.
That's not what 'noearly' means. It refers to two passes after the root
filesystem has been mounted. We don't
I can confirm this problem on my system. My system is slightly different
in that my / swap and /home are each crypted with a passphrase. Until
recently (i.e. the last week), the system would prompt for passphrases
for / and swap, and then throw an error message about waiting too long
to mount fs
As I realized mountall 1.0 had been released I decided to try this
again, but it still fails. This time, however, I'm getting an error
message, rather than the system just freezing:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33393793/Dependencies.txt
--
System frezes after fscking root
https://bugs.launchpad.net/bugs/447817
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
it sounds like mountall is simply waiting for the encrypted disk to
appear, and that you didn't get prompted for a passphrase means this is
a cryptsetup issue
** Package changed: mountall (Ubuntu) = cryptsetup (Ubuntu)
--
System frezes after fscking root
https://bugs.launchpad.net/bugs/447817
A small correction: Cryptsetup is not supposed to ask for a passphrase,
as it should use the keyfile configured in /etc/crypttab. But that is
most likely not relevant to the issue at hand.
However, please do note that cryptsetup 1.0.6+20090405.svn49-1ubuntu4
will set up the disk propperly when
