https://bugzilla.suse.com/show_bug.cgi?id=1234010 https://bugzilla.suse.com/show_bug.cgi?id=1234010#c3 Alberto Planas Dominguez <aplanas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Alberto Planas Dominguez <aplanas@suse.com> --- Sorry for the delay. Reading your logs I am able to reproduce it: ``` Dec 01 18:25:45 localhost kernel: hid-generic 0003:26CE:01A2.0001: input,hidraw0: USB HID v1.10 Device [ASRock LED Controller] on usb-0000:02:00.0-8/input0 Dec 01 18:25:45 localhost kernel: hid-generic 0003:1050:0120.0002: hiddev96,hidraw1: USB HID v1.10 Device [Yubico Security Key by Yubico] on usb-0000:02:00.0-2.2/input0 Dec 01 18:25:45 localhost kernel: usb 1-2.4.1: new full-speed USB device number 7 using xhci_hcd Dec 01 18:25:45 localhost systemd-cryptsetup[790]: Failed to open FIDO2 device /dev/hidraw1: FIDO_ERR_RX Dec 01 18:25:45 localhost systemd-cryptsetup[790]: Token returned error during pre-flight: Input/output error Dec 01 18:25:45 localhost systemd-cryptsetup[790]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/1b692ff9-23f5-4d84-86ee-51b3c3cb72c4. Dec 01 18:25:45 localhost systemd-cryptsetup[790]: Specified device /dev/hidraw1 is not a FIDO2 device. Dec 01 18:25:45 localhost systemd-cryptsetup[790]: Security token not present for unlocking volume Samsung SSD 990 PRO with Heatsink 1TB (cr_swap), please plug it in. Dec 01 18:25:45 localhost systemd-cryptsetup[790]: Specified device /dev/hidraw1 is not a FIDO2 device. Dec 01 18:25:45 localhost systemd-cryptsetup[789]: Asking FIDO2 token for authentication. Dec 01 18:25:45 localhost systemd-cryptsetup[789]: Please confirm presence on security token to unlock. ``` It is a race condition in systemd. Both cr_root and cr_swap are trying to access to the FIDO2 key, causing problems. I filled an issue upstream: https://github.com/systemd/systemd/issues/35671 We need to add somehow an ordering in the unlock -- You are receiving this mail because: You are on the CC list for the bug.