All passwords are already entered, the problem occurs some time after the passwords have been entered, and as far as I could see on the debug console, all encrypted devices exist under /dev/mapper, so it does not seem to be caused by encryption (except for the fact that encryption generataes long device names as /dev/mapper/crypt... which get shortened).
My current guess is that it is a problem with the swap device (I'm using separate encrypted swap devices on those machines where the problem occurs), that systemd somehow tries to clean/format the swap device and something goes wrong there. And no, the problem is not new, I've already seen this months ago. It came with 16.04/systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668906 Title: systemd occasionally hangs forever while booting: A start job is running for ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668906/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
