[Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Steve Langasek]

I don't know exactly why this manifests as a dependency loop, but your
/etc/crypttab is certainly wrong; the first column of /etc/crypttab is
the target device name, and you cannot have two separate source
encrypted devices map to the same decrypted device name.

If you give the two devices separate names (e.g. swap1, swap2), does
this work for you?

If not this should probably be reassigned to systemd, since those
systemd units are created by a systemd generator and not by the
cryptsetup package.

** Changed in: cryptsetup (Ubuntu)
       Status: New => Incomplete

-- 
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/1875577

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in cryptsetup package in Ubuntu:
  Incomplete

Bug description:
  root at eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:	Ubuntu
  Description:	Ubuntu 20.04 LTS
  Release:	20.04
  Codename:	focal

  root at eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
    Installed: (none)
    Candidate: 2:2.2.2-3ubuntu2
    Version table:
       2:2.2.2-3ubuntu2 500
          500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ======================

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap (debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each disk)

  
  4. /etc/crypttab is set up as follows:

  swap      /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-00000_S3W6NX0M802914-part2    /dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap      /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-00000_S3W6NX0M802933-part2    /dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===============

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =====================

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [    5.360793] systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup at swap.service/start
  Apr 28 17:13:01 eu1 kernel: [    5.360795] systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [    5.360796] systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [    5.360797] systemd[1]: cryptsetup.target: Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [    5.360798] systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [    5.360799] systemd[1]: cryptsetup.target: Job systemd-cryptsetup at swap.service/start deleted to break ordering cycle starting with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [    5.361082] systemd[1]: Unnecessary job for /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-00000_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root at eu1:/var/log# ls -l /dev/mapper
  total 0
  crw------- 1 root root 10, 236 Apr 28 17:13 control
  root at eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:      0.0 total,      0.0 free,      0.0 used.  63153.6 avail
  Mem

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