This bug report has gotten very muddled, with comments from users with
all different kinds of configurations. Looking at the original
reporter's symptoms:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/: waiting for /dev/mapper/whisper-whisper_root
/tmp: waiting for (null)
/boot: waiting for /dev/disk/by-uuid/23xxxxx
/home: waiting for /dev/disk/by-uuid/d5xxxxx
My understanding is that this is a system with /, /home, and swap all on
the *same* crypted LVM. That means that the cryptsetup passphrase
prompt must happen in the initramfs (to decrypt / for mounting),
*before* mountall starts.
So why does mountall think it's still waiting for the root filesystem,
when it's already /running/ from the root filesystem? Does /dev/mapper
/whisper-whisper_root not match the root filesystem value specified in
the grub config?
(And why would this problem go away if not using usplash?)
I'm going to mark the cryptsetup task 'invalid' here, because I don't
see any way it could be involved given the initramfs/mountall split at
work.
** Changed in: cryptsetup (Ubuntu)
Status: New => Invalid
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
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
