Public bug reported:
I use Ubuntu 18.04.1 with systemd version:
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2
default-hierarchy=hybrid
I use dracut + clevis for automatic decryption of my LUKS encrypted
drives during boot.
I get the following message from one of the non-root disks:
●
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service
- Cryptography Setup for luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
Loaded: loaded (/etc/crypttab; generated)
Active: failed (Result: signal) since Sun 2019-02-03 15:04:35 UTC; 5min ago
Docs: man:crypttab(5)
man:systemd-cryptsetup-generator(8)
man:systemd-cryptsetup@.service(8)
Process: 589 ExecStart=/lib/systemd/systemd-cryptsetup attach
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 none
luks,discard (code=killed, signal=ABRT)
Main PID: 589 (code=killed, signal=ABRT)
Feb 03 15:04:26 beta systemd[1]: Starting Cryptography Setup for
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1...
Feb 03 15:04:35 beta systemd-cryptsetup[589]: Set cipher aes, mode xts-plain64,
key size 256 bits for device
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1.
Feb 03 15:04:35 beta systemd-cryptsetup[589]: realloc(): invalid next size
Feb 03 15:04:35 beta systemd[1]:
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service:
Main process exited, code=killed, status=6/ABRT
Feb 03 15:04:35 beta systemd[1]:
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service:
Failed with result 'signal'.
Feb 03 15:04:35 beta systemd[1]: Failed to start Cryptography Setup for
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1.
The systemd issue reporting template told me to not report systemd
issues for anything but the two newest versions of systemd, and refered
to the distribution bug tracker instead.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I use Ubuntu 18.04.1 with systemd version:
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2
default-hierarchy=hybrid
I use dracut + clevis for automatic decryption of my LUKS encrypted
drives during boot.
I get the following message from one of the non-root disks:
●
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service
- Cryptography Setup for luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
- Loaded: loaded (/etc/crypttab; generated)
- Active: failed (Result: signal) since Sun 2019-02-03 15:04:35 UTC; 5min ago
- Docs: man:crypttab(5)
- man:systemd-cryptsetup-generator(8)
- man:systemd-cryptsetup@.service(8)
- Process: 589 ExecStart=/lib/systemd/systemd-cryptsetup attach
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 none
luks,discard (code=killed, signal=ABRT)
- Main PID: 589 (code=killed, signal=ABRT)
+ Loaded: loaded (/etc/crypttab; generated)
+ Active: failed (Result: signal) since Sun 2019-02-03 15:04:35 UTC; 5min ago
+ Docs: man:crypttab(5)
+ man:systemd-cryptsetup-generator(8)
+ man:systemd-cryptsetup@.service(8)
+ Process: 589 ExecStart=/lib/systemd/systemd-cryptsetup attach
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 none
luks,discard (code=killed, signal=ABRT)
+ Main PID: 589 (code=killed, signal=ABRT)
Feb 03 15:04:26 beta systemd[1]: Starting Cryptography Setup for
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1...
Feb 03 15:04:35 beta systemd-cryptsetup[589]: Set cipher aes, mode
xts-plain64, key size 256 bits for device
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1.
Feb 03 15:04:35 beta systemd-cryptsetup[589]: realloc(): invalid next size
Feb 03 15:04:35 beta systemd[1]:
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service:
Main process exited, code=killed, status=6/ABRT
Feb 03 15:04:35 beta systemd[1]:
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service:
Failed with result 'signal'.
Feb 03 15:04:35 beta systemd[1]: Failed to start Cryptography Setup for
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1.
The systemd issue reporting template told me to not report systemd
- issues for anything but the two newest versions of systemd.
+ issues for anything but the two newest versions of systemd, and refered
+ to the distribution bug tracker instead.
--
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/1814460
Title:
systemd-cryptsetup fails during initrd stage of boot
Status in systemd package in Ubuntu:
New
Bug description:
I use Ubuntu 18.04.1 with systemd version:
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2
default-hierarchy=hybrid
I use dracut + clevis for automatic decryption of my LUKS encrypted
drives during boot.
I get the following message from one of the non-root disks:
●
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service
- Cryptography Setup for luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
Loaded: loaded (/etc/crypttab; generated)
Active: failed (Result: signal) since Sun 2019-02-03 15:04:35 UTC; 5min ago
Docs: man:crypttab(5)
man:systemd-cryptsetup-generator(8)
man:systemd-cryptsetup@.service(8)
Process: 589 ExecStart=/lib/systemd/systemd-cryptsetup attach
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 none
luks,discard (code=killed, signal=ABRT)
Main PID: 589 (code=killed, signal=ABRT)
Feb 03 15:04:26 beta systemd[1]: Starting Cryptography Setup for
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1...
Feb 03 15:04:35 beta systemd-cryptsetup[589]: Set cipher aes, mode
xts-plain64, key size 256 bits for device
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1.
Feb 03 15:04:35 beta systemd-cryptsetup[589]: realloc(): invalid next size
Feb 03 15:04:35 beta systemd[1]:
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service:
Main process exited, code=killed, status=6/ABRT
Feb 03 15:04:35 beta systemd[1]:
systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service:
Failed with result 'signal'.
Feb 03 15:04:35 beta systemd[1]: Failed to start Cryptography Setup for
luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1.
The systemd issue reporting template told me to not report systemd
issues for anything but the two newest versions of systemd, and
refered to the distribution bug tracker instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814460/+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
