We ran across another instance of this bug today, on a different system.
A production back-end (no GUI) server had been mistakenly configured to
pull packages from xenial-proposed, and it updated to kernel 4.4.0-119
this morning. It then failed to boot with the exact same symptoms
described above. It boots just fine when manually selecting the
4.4.0-118 kernel.
Now we're down to one release increment...
4.4.0-118: bug is absent, affected systems boot just fine
4.4.0-119: bug is present, affected systems fail to boot
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721618
Title:
cryptsetup: lvm is not available -- unable to boot, not asked for FDE
password
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1721618/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
