This is a lot worse now that systemd actually complains about the missing device and blocks the boot on it for 90s. I just discussed that with Dustin. Summary:
- This was introduced in https://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/revision/776 but can't work (see https://wiki.archlinux.org/index.php/Dm-crypt/Swap_encryption). - Fix for future installs: Add offset=1024, to maintain the swap signature and UUID on the underlying hardware device - While we are at it: change the obsolete cipher setting to the current cryptsetup default "cipher=aes-xts-plain64" For upgrades: Add postinst code to clean up broken installs: find the missing swap partitions and comment them out in crypttab and fstab. We also discussed a possible salvation of swap partitions, running mkswap -U <expected UUID> on them, but IMHO it is unexpected and intrusive to suddenly get a swap partition after having an existing installations for years without one. ** Changed in: ecryptfs-utils (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Also affects: ecryptfs-utils (Ubuntu Vivid) Importance: High Assignee: Martin Pitt (pitti) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953875 Title: Encrypted swap no longer mounted at bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
