You'll get the 90 second timeout with waiting for dev-disk-by\x2duuid-
0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device (which
presumably is the one containing swap), then your system should boot
without swap.
> Mär 07 09:28:00 darw1n swapon[418]: swapon: /dev/sda3: Swap-Header
konnte nicht gelesen werden
This indicates that your /etc/fstab contains an invalid "swap" partition
entry, as you now use an encrypted swap. Your udev database has no
device with the above UUID, and /dev/sda3 has no file system on it at
all, so it'll indeed wait for that in vain. It might be the UUID of the
/dev/mapper/cryptswap1 device.
Can you please attach your /etc/fstab and /etc/crypttab files? (They
shouldn't contain keys, just the names of the key files; but please do
have a look at them, and feel free to obfuscate anything which looks
like a password/key with XXXXX or so).
Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429354
Title:
Systemd takes very long to boot with error in swap mounting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
