Well, life would be much easier if there was some usable documentation about what's going on within systemd.
By the way, I did not put in that 'swap' option manually, it was inserted by the xubuntu 15.10 beta installer on cdrom/usb image. If you choose to encrypt a partition and put a swap inside, it automatically adds that swap option. So at least this crypttab option, the behaviour of the installer, and systemd don't fit together. Since you mention it: On my other machine with 15.10 I noticed the problem that the machine does not recover from hibernate, but performs a fresh boot, which meets your hint, that wake up does not work with that style of crypt swap. whatever it is what fills the device with random data, should honor the luks option in the crypttab and use this thing as intended (i.e. configure the device mapper and do a swapon). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1506139 Title: 15.10beta crashes encrypted swap partition Status in systemd package in Ubuntu: New Bug description: Hi, I'm usually using a setup with three partitions on a disk Partition 1: plain ext4 boot partition mounted on /boot Partition 2: luks-encrypted swap Partition 3: luks-encrypted btrfs for / /home ... both mentioned in /etc/crypttab like sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard With several machines I have installed 15.10 beta on and in several cases I experienced the problem that the swap is not activated at boot time and that /dev/disks/by-uuid does not contain a link to the swap partition, and the previously created luks-encrypted swap is destroyed after boot: It is not a luks partition anymore and filled with random (presumably encrypted) bytes without structure. I first thought that this is a problem of the setup process, and repaired the swap manually. But then I found the partition destroyed again. This happend several times on several machines. I am not sure yet what exactly would destroy the partition. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cryptsetup 2:1.6.6-5ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Oct 14 18:12:58 2015 InstallationDate: Installed on 2015-10-08 (5 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) crypttab: sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
