I now realize that the behavior I originally described in this report as
a bug is in fact appropriate: three tries to unlock an encrypted
partition at boot is apparently default, and startup can and should
continue even when the /home partition is not available, it just won't
be mounted in the /home mountpoint. As long as the operating system
itself is on unencrypted/unlocked partitions, it can run just fine
without any user home directory.
Amusingly, I can even log in in a virtual console, I'm just dropped into
/ since /home is empty.
Closing this report as Invalid - not a bug.
** Changed in: cryptsetup (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875186
Title:
Booting continues despite three failed attempts if the root partition
is unencrypted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1875186/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
