Yrurtj

For some reason, I can't add a key to my encrypted swap.

My /etc/crypttab:

swap_crypt /dev/disk/by-partuuid/c4f049d5-ae21-44d6-b753-6e72b7e21770 none luks,swap,discard,keyscript=decrypt_keyctl

root_crypt UUID=26f3c181-e041-47f2-929b-de631a2f1d3f none luks,discard,keyscript=decrypt_keyctl

So to identify those disks:

# ls -l /dev/disk/by-partuuid/c4f049d5-ae21-44d6-b753-6e72b7e21770

lrwxrwxrwx 1 root root 15 Mar  5 22:34 /dev/disk/by-partuuid/c4f049d5-ae21-44d6-b753-6e72b7e21770 -> ../../nvme0n1p7

# blkid |grep 26f3c181-e041-47f2-929b-de631a2f1d3f

/dev/nvme0n1p8: UUID="26f3c181-e041-47f2-929b-de631a2f1d3f" TYPE="crypto_LUKS" PARTUUID="b178ae44-cf49-4dce-b7b5-293c9c0bb9c7"

So I know my swap is on /dev/nvme0n1p7 and my root is /dev/nvme0n1p8.

Now, when I try to add a key for root:

# cryptsetup luksAddKey /dev/nvme0n1p8

Enter any existing passphrase:

Everything works fine, however, for swap:

# cryptsetup luksAddKey /dev/nvme0n1p7

It just exits. A little more info:

# cryptsetup luksAddKey -v --debug /dev/nvme0n1p7

# cryptsetup 2.0.2 processing "cryptsetup luksAddKey -v --debug /dev/nvme0n1p7"

# Running command luksAddKey.

# Locking memory.

# Installing SIGINT/SIGTERM handler.

# Unblocking interruption on signal.

# Allocating context for crypt device /dev/nvme0n1p7.

# Trying to open and read device /dev/nvme0n1p7 with direct-io.

# Initialising device-mapper backend library.

# Trying to load any crypt type from device /dev/nvme0n1p7.

# Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 2.0.2.

# Detected kernel Linux 5.0.0-050000-generic x86_64.

# Loading LUKS2 header.

# Opening lock resource file /run/cryptsetup/L_259:7

# Acquiring read lock for device /dev/nvme0n1p7.

# Verifying read lock handle for device /dev/nvme0n1p7.

# Device /dev/nvme0n1p7 READ lock taken.

# Trying to read primary LUKS2 header at offset 0.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 8192.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 16384.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 32768.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 65536.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 131072.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 262144.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 524288.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 1048576.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 2097152.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# Trying to read secondary LUKS2 header at offset 4194304.

# Opening locked device /dev/nvme0n1p7

# Veryfing locked device handle (bdev)

# LUKS2 header read failed (-22).

# Device /dev/nvme0n1p7 READ lock released.

# Releasing crypt device /dev/nvme0n1p7 context.

# Releasing device-mapper backend.

# Unlocking memory.

Command failed with code -1 (wrong or missing parameters).

Any idea what the problem is?