Cannot login with user created using --luks-sector-size=4096 #30393
Description
systemd version the issue has been seen with
255-1
Used distribution
Arch Linux
Linux kernel version used
6.6.4-arch1-1
CPU architectures issue was seen on
x86_64
Component
systemd-homed
Expected behaviour you didn't see
Successful login from getty.
Unexpected behaviour you saw
When logging it from getty, password was asked four times, but home was still not unlocked.
Full boot log with systemd.log_level=debug: vm3.log
Steps to reproduce the problem
Create user with:
# homectl create test1 --storage=luks --luks-sector-size=4096
And then try to log in as test1.
Additional program output to the terminal or log subsystem illustrating the issue
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: Sending to worker: {"luksSectorSize":4096,"userName":"test1","perMachine":[{"storage":"luks","matchMachineId":"418c71588d254bd99e170598e657c240"}],"disposition":"regular","lastChangeUSec":1702114399414059,"lastPasswordChangeUSec":1702114399414059,"privileged":{"hashedPassword":["$y$j9T$6ZVl2lxZz6RtRK7HV5U2H1$2wX6PZEoNYhTd26NYh4FYwwFpYDcDpUDKuYOB8/hWJA"]},"signature":[{"data":"2x07M1tGS0//vnaUmv7sBeDLsVARLIi4SCYXCeU7/4xm5sBc/Y3mfuXJ+GLN3vhYpjddI9i2tjRv9UHVSO+SBw==","key":"-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEA7zKL9UrI6RWJYaQ4aw9AbuaivMVs2COEn3smZVP/z2s=\n-----END PUBLIC KEY-----\n"}],"binding":{"418c71588d254bd99e170598e657c240":{"imagePath":"/home/test1.home","partitionUuid":"8c118879-0164-4f49-b7ab-6b146d13bba2","luksUuid":"f18e4697-db98-4ce8-876e-2e3ce6b67c1a","fileSystemUuid":"bba71fbd-f086-4655-a0fb-2e580e82d0c9","luksCipher":"aes","luksCipherMode":"xts-plain64","luksVolumeKeySize":32,"fileSystemType":"btrfs","uid":60510,"gid":60510,"storage":"luks"}},"status":{"418c71588d254bd99e170598e657c240":{"rateLimitBeginUSec":1702114411845443,"rateLimitCount":1}},"secret":{}}
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: Successfully forked off '(sd-homework)' as PID 515.
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: test1: changing state inactive → activating-for-acquire
Dec 09 09:33:31 archtestvm3 systemd-journald[227]: Compressed data object 1101 -> 727 using ZSTD
Dec 09 09:33:31 archtestvm3 systemd-homework[515]: User record has no recovery keys, plaintext passwords not tested against it.
Dec 09 09:33:31 archtestvm3 systemd-homework[515]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: Got notify message lacking both ERRNO= and SYSTEMD_LUKS_LOCK_FD= field, ignoring.
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: Worker reported error code ENOKEY.
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: Activation failed: Required key not available
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: Sent message type=error sender=n/a destination=:1.9 path=n/a interface=n/a member=n/a cookie=26 reply_cookie=3 signature=s error-name=org.freedesktop.home1.BadPassword error-message=Password for home test1 is incorrect or not sufficient for authentication.
Dec 09 09:33:31 archtestvm3 systemd-homed[350]: test1: changing state activating-for-acquire → inactive