FS#61417 - [systemd]Failed to mount encrypted partition.

Attached to Project: Arch Linux
Opened by maid (maid) - Tuesday, 15 January 2019, 20:24 GMT
Last edited by freswa (frederik) - Tuesday, 11 February 2020, 21:26 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: systemd-cryptsetup@XXX.service unable to mount partition since last system upgrade at 2019-01-10. Nevertheless, I can easy mount it manualy with command: cryptsetup plainOpen /dev/XXX name

Additional info:
systemd-cryptsetup[502]: Set cipher twofish, mode xts:sha256, key size 512 bits for device /dev/XXX.
systemd-cryptsetup[502]: device-mapper: reload ioctl on failed: Invalid argument
systemd-cryptsetup[502]: Failed to activate: Invalid argument
systemd[1]: systemd-cryptsetup@XXX.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-cryptsetup@XXX.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Cryptography Setup for XXX.
systemd[1]: Dependency failed for Local Encrypted Volumes.
systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.

Crypttab content.
Variant 1.
name /dev/XXX none plain
Variant 2.
name /dev/XXX - plain,cipher=twofish-xts:sha256,size=512

Steps to reproduce:
pacman -Syu
This task depends upon

Closed by  freswa (frederik)
Tuesday, 11 February 2020, 21:26 GMT
Reason for closing:  Not a bug
Additional comments about closing:  No response from reporter. Please request re-open if issue persists.
Comment by maid (maid) - Thursday, 17 January 2019, 10:26 GMT
(sd-passwd)[422]: Invalid password file /run/systemd/ask-password/ask.xlEYn8
(sd-passwd)[422]: Failed to show password: Bad message
systemd-cryptsetup[496]: Set cipher twofish, mode xts:sha256, key size 512 bits for device /dev/XXA8.
systemd-cryptsetup[496]: device-mapper: reload ioctl on failed: Invalid argument
kernel: device-mapper: table: 254:0: crypt: IV mechanism required
kernel: device-mapper: ioctl: error adding target to table
systemd-cryptsetup[367]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/XXA4.
systemd-cryptsetup[496]: Failed to activate: Invalid argument
systemd[1]: systemd-cryptsetup@home.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd

# crypttab: mappings for encrypted partitions
# plain
XXA8 /dev/XXA8 - plain,cipher=twofish-xts:sha256,size=512
# luks
XXA4 /dev/XXA4 none
Comment by maid (maid) - Sunday, 20 January 2019, 16:51 GMT
Downgrade to libsystemd 239.370-1, systemd 239.370-1, lib32-systemd 239.370-1, systemd-sysvcompat 239.370-1 will fix this problem.
Comment by maid (maid) - Wednesday, 23 January 2019, 15:45 GMT
journalctl attached.
Comment by Justin Capella (justincapella) - Thursday, 07 March 2019, 21:24 GMT
I believe the systemd encrypt hook wants you to specify the disk uuid in a kennel command line. See https://wiki.archlinux.org/index.php/Dm-crypt/System_configuration#Using_sd-encrypt_hook
Comment by Justin Capella (justincapella) - Friday, 13 September 2019, 14:50 GMT
kernel: device-mapper: table: 254:0: crypt: IV mechanism required

Loading...