[Confirmed bug w/ cryptsetup] Mkinitcpio error related to sd-encrypt: ==> ERROR: file not found: `'

[Kusgow]

Oh, thanks a lot! I did completely misinterpret it

[sedi]

I can confirm that switching to stable-staging solved this error for me! Thanks

sudo mkinitcpio -p linux510
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.42-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [sd-vconsole]
  -> Running build hook: [keyboard]
  -> Running build hook: [sd-plymouth]
  -> Running build hook: [sd-encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.42-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [sd-vconsole]
  -> Running build hook: [keyboard]
  -> Running build hook: [sd-plymouth]
  -> Running build hook: [sd-encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64-fallback.img
==> Image generation successful

[El_Brujo]

I’m just marking this post as accepted solution for this thread.

[Confirmed bug w/ cryptsetup] Mkinitcpio error related to sd-encrypt: ==> ERROR: file not found: `'

The issue is this: update sd-encrypt hook · archlinux/svntogit-packages@bf77990 · GitHub People had reported to me to have issues with the newer systemd series. Therefore I did hold it back. However cryptsetup slipped. We have to use the older version if we keep the older systemd series. So let’s update systemd to the 248 series and you switch over to stable-staging branch to test that out. This should fix the issue. And for stable branch I’ll downgrade cryptsetup for now.

So far this is the best answer you guys can get at the moment.

[sedi]

unfortunately I had to revert to the older systemd and cryptsetup! I use a keyfile in my crypttab and I was not able to decrypt with it anymore - even without systemd (i.e. no sd-encrypt but encrypt). I guess that is related to cryptsetup then but anyways this is not working atm as it should. using cryptsetup open … --keyfile … was still working fine so so no idea where the bug actually is…

the error I get is:

Jul 03 20:17:32  systemd-cryptsetup[534]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/sdb1.
Jul 03 20:17:32  systemd-cryptsetup[534]: Failed to activate with key file '/home/tfi/2tb.k': Invalid argument
Jul 03 20:17:32  systemd[1]: systemd-cryptsetup@bigopt.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 20:17:32  systemd[1]: systemd-cryptsetup@bigopt.service: Failed with result 'exit-code'.
Jul 03 20:17:32  systemd[1]: Failed to start Cryptography Setup for bigopt

where bigopt is the name for the encrypted device.

/etc/crypttab:

bigopt	/dev/sdb1	/home/myname/2tb.k	timeout=30,nofail

I have also tried to put it in /etc/cryptsetup-keys.d/bigopt.key and specifying it with luks.key=xx-uuid=/path/to/keyfile (when sd-encrypt was enabled) but whatever I tried nothing worked. the only thing which worked was downgrading systemd + cryptsetup (I did that in one run so dunno if it is the one or the other or both…)

currently on (working - without sd-encrypt):

systemd 247.6-1.0
cryptsetup 2.3.5-4

will now upgrade to

cryptsetup-2.3.6-1
systemd-248.3-3

(I wasnt sure about the previous version I had installed so downgraded too much. now I am back at stable and not stable-staging anymore and so upgrade to the latest version there)

upgraded to

cryptsetup-2.3.6-1
systemd-248.3-3

and keyfile stops working again.

downgraded to:

systemd 247.7-1 <--- newer then on my above other try
cryptsetup 2.3.5-4

and it works again… im lost.