[Bug 1736072] [NEW] Encrypted swap does not work

dino99 1736072 at bugs.launchpad.net
Mon Dec 4 06:52:59 UTC 2017 

Public bug reported:

On a working system, i've added a new hdd, and decided to use it as the main device storage.
So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation.
Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation.

Booting with that new install, i hit a cryptswap1 timeout after beeing
frozen around 1 minute.

oem at ubuntu:~$ journalctl | grep cryptswap
systemd[1]: Starting Cryptography Setup for cryptswap2...
systemd[1]: Started Cryptography Setup for cryptswap2.
systemd[1]: Found device /dev/mapper/cryptswap2.
systemd[1]: Activating swap /dev/mapper/cryptswap2...
kernel: Adding 10584572k swap on /dev/mapper/cryptswap2.  Priority:-1 extents:1 across:10584572k FS
systemd[1]: Activated swap /dev/mapper/cryptswap2.
systemd[1]: Starting Cryptography Setup for cryptswap1...
systemd[1]: Started Cryptography Setup for cryptswap1.

oem at ubuntu:~$ journalctl | grep timeout
systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'.

Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition.
/etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens.

oem at ubuntu:~$ swapon -s
Filename				Type		Size	Used	Priority
/dev/dm-0                              	partition	10584572	221184	-1


Conclusion:
-ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions
- the cryptsetup version is not well supporting the kernel/systemd settings/configs

As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these.
http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cryptsetup 2:1.7.3-4ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec  4 07:26:17 2017
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

** Affects: cryptsetup (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic upgrade-software-version

** Description changed:

  On a working system, i've added a new hdd, and decided to use it as the main device storage.
- So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. 
+ So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation.
  Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation.
  
  Booting with that new install, i hit a cryptswap1 timeout after beeing
  frozen around 1 minute.
  
  oem at ubuntu:~$ journalctl | grep cryptswap
- Dec 04 05:07:09 ubuntu systemd[1]: Starting Cryptography Setup for cryptswap2...
- Dec 04 05:07:09 ubuntu systemd[1]: Started Cryptography Setup for cryptswap2.
- Dec 04 05:07:09 ubuntu systemd[1]: Found device /dev/mapper/cryptswap2.
- Dec 04 05:07:09 ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap2...
- Dec 04 05:07:09 ubuntu kernel: Adding 10584572k swap on /dev/mapper/cryptswap2.  Priority:-1 extents:1 across:10584572k FS
- Dec 04 05:07:09 ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap2.
- Dec 04 05:07:09 ubuntu systemd[1]: Starting Cryptography Setup for cryptswap1...
- Dec 04 05:07:09 ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
+ systemd[1]: Starting Cryptography Setup for cryptswap2...
+ systemd[1]: Started Cryptography Setup for cryptswap2.
+ systemd[1]: Found device /dev/mapper/cryptswap2.
+ systemd[1]: Activating swap /dev/mapper/cryptswap2...
+ kernel: Adding 10584572k swap on /dev/mapper/cryptswap2.  Priority:-1 extents:1 across:10584572k FS
+ systemd[1]: Activated swap /dev/mapper/cryptswap2.
+ systemd[1]: Starting Cryptography Setup for cryptswap1...
+ systemd[1]: Started Cryptography Setup for cryptswap1.
+ 
  oem at ubuntu:~$ journalctl | grep timeout
- Dec 04 05:08:36 ubuntu systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'.
+ systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'.
  
- Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition. 
+ Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition.
  /etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens.
+ 
+ oem at ubuntu:~$ swapon -s
+ Filename				Type		Size	Used	Priority
+ /dev/dm-0                              	partition	10584572	221184	-1
+ 
  
  Conclusion:
  -ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions
  - the cryptsetup version is not well supporting the kernel/systemd settings/configs
  
  As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these.
  http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:1.7.3-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec  4 07:26:17 2017
  EcryptfsInUse: Yes
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

** Tags added: upgrade-software-version

** Also affects: ubiquity (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1736072

Title:
  Encrypted swap does not work

Status in cryptsetup package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  On a working system, i've added a new hdd, and decided to use it as the main device storage.
  So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation.
  Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation.

  Booting with that new install, i hit a cryptswap1 timeout after beeing
  frozen around 1 minute.

  oem at ubuntu:~$ journalctl | grep cryptswap
  systemd[1]: Starting Cryptography Setup for cryptswap2...
  systemd[1]: Started Cryptography Setup for cryptswap2.
  systemd[1]: Found device /dev/mapper/cryptswap2.
  systemd[1]: Activating swap /dev/mapper/cryptswap2...
  kernel: Adding 10584572k swap on /dev/mapper/cryptswap2.  Priority:-1 extents:1 across:10584572k FS
  systemd[1]: Activated swap /dev/mapper/cryptswap2.
  systemd[1]: Starting Cryptography Setup for cryptswap1...
  systemd[1]: Started Cryptography Setup for cryptswap1.

  oem at ubuntu:~$ journalctl | grep timeout
  systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'.

  Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition.
  /etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens.

  oem at ubuntu:~$ swapon -s
  Filename				Type		Size	Used	Priority
  /dev/dm-0                              	partition	10584572	221184	-1

  
  Conclusion:
  -ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions
  - the cryptsetup version is not well supporting the kernel/systemd settings/configs

  As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these.
  http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:1.7.3-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec  4 07:26:17 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1736072/+subscriptions

More information about the foundations-bugs mailing list