You are not logged in.

#1 2021-12-29 11:34:39

p90
Member
Registered: 2013-06-07
Posts: 21

systemd homed cannot use user on extra harddrive anymore

Hello,

have yesterday resetup my laptop to move the root partition from ext4 to F2FS. As it seemed to be easiest to backup my old config and just reinstall arch, I went that route.
Unfortunately I am facing now an issue there homed refuses to activate any user on a dedicated hard drive while local users seem to work.

Example

homectl create test_local --disk-size 2
homectl activate test_local

works. I see

Dez 29 12:07:06  systemd-homed[411]: test_local: changing state inactive → activating
Dez 29 12:07:06  systemd-homework[3621]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Dez 29 12:07:06  systemd-homed[411]: Activation failed: Required key not available
Dez 29 12:07:06  systemd-homed[411]: test_local: changing state activating → inactive
Dez 29 12:07:07  systemd-homed[411]: test_local: changing state inactive → activating
Dez 29 12:07:07  systemd-homework[3622]: Provided password unlocks user record.
Dez 29 12:07:07  systemd-homework[3622]: Successfully locked image file '/home/test_local.home'.
Dez 29 12:07:07  systemd-homework[3622]: Allocated additional 191.1M.
Dez 29 12:07:07  systemd-homework[3622]: Setting up loopback device /dev/loop0 completed.
Dez 29 12:07:07  kernel: loop0: detected capacity change from 0 to 557056
Dez 29 12:07:08  systemd-homework[3622]: Setting up LUKS device /dev/mapper/home-test_local completed.
Dez 29 12:07:08  systemd-homework[3622]: Provided password unlocks user record.
Dez 29 12:07:08  systemd-homework[3622]: Probing file system completed (found btrfs).
Dez 29 12:07:08  systemd-homework[3622]: File system check completed.
Dez 29 12:07:08  systemd-homework[3622]: Mounting file system completed.
Dez 29 12:07:08  systemd-homework[3622]: Discovered used loopback device /dev/loop0.
Dez 29 12:07:08  systemd-homework[3622]: offset = 1048576, size = 285212672, image = 287309824
Dez 29 12:07:08  kernel: BTRFS info (device dm-0): flagging fs with big metadata feature
Dez 29 12:07:08  kernel: BTRFS info (device dm-0): use zstd compression, level 1
Dez 29 12:07:08  kernel: BTRFS info (device dm-0): using free space tree
Dez 29 12:07:08  kernel: BTRFS info (device dm-0): has skinny extents
Dez 29 12:07:08  kernel: BTRFS info (device dm-0): enabling ssd optimizations
Dez 29 12:07:08  systemd-homework[3622]: New file system size identical to old file system size, skipping operation.
Dez 29 12:07:08  systemd-homework[3622]: Read embedded .identity file.
Dez 29 12:07:08  systemd-homework[3622]: Provided password unlocks user record.
Dez 29 12:07:08  systemd-homework[3622]: Reconciling user identities completed (host and header version were identical).
Dez 29 12:07:08  systemd-homework[3622]: Reconciling embedded user identity completed (host and embedded version were identical).
Dez 29 12:07:08  systemd-homework[3622]: Recursive changing of ownership not necessary, skipped.
Dez 29 12:07:08  systemd-homework[3622]: Synchronized disk.
Dez 29 12:07:08  systemd-homework[3622]: Moving to final mount point /home/test_local completed.
Dez 29 12:07:08  systemd-homework[3622]: Activation completed.
Dez 29 12:07:08  systemd-homework[3622]: Image size is 272.0M, file system size is 256.0M, file system payload size is 256.0M, file system free is 252.4M.
Dez 29 12:07:08  systemd-homed[411]: Home test_local is signed exclusively by our key, accepting.
Dez 29 12:07:08  systemd-homed[411]: test_local: changing state activating → active

in the logs so it seems that homed is setup correctly.

However,
if I try to replicate my old setup with my user living on its own harddrive I get this:

homectl create test_remote --image-path /dev/sdb
homectl activate test_remote
Operation on home test_remote failed: Failed to execute operation: Invalid argument

Please note that I am using an empty password for both here but the issue also occures when using a password.
In the logs I see

Dez 29 12:21:37  systemd-homed[411]: test_remote: changing state inactive → activating
Dez 29 12:21:37  systemd-homework[3993]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Dez 29 12:21:37  systemd-homed[411]: Activation failed: Required key not available
Dez 29 12:21:37  systemd-homed[411]: test_remote: changing state activating → inactive
Dez 29 12:21:38  systemd-homed[411]: test_remote: changing state inactive → activating
Dez 29 12:21:38  systemd-homework[3994]: Provided password unlocks user record.
Dez 29 12:21:38  systemd-homework[3994]: Setting up loopback device /dev/disk/by-uuid/879b8acc-8d17-4ca2-bd2a-62d698e8e277 completed.
Dez 29 12:21:39  systemd-homework[3994]: Setting up LUKS device /dev/mapper/home-test_remote completed.
Dez 29 12:21:39  systemd-homework[3994]: Provided password unlocks user record.
Dez 29 12:21:39  systemd-homework[3994]: Probing file system completed (found btrfs).
Dez 29 12:21:39  systemd-homework[3994]: File system check completed.
Dez 29 12:21:39  kernel: BTRFS info (device dm-0): flagging fs with big metadata feature
Dez 29 12:21:39  kernel: BTRFS info (device dm-0): use zstd compression, level 1
Dez 29 12:21:39  kernel: BTRFS info (device dm-0): turning on sync discard
Dez 29 12:21:39  kernel: BTRFS info (device dm-0): using free space tree
Dez 29 12:21:39  kernel: BTRFS info (device dm-0): has skinny extents
Dez 29 12:21:39  systemd-homework[3994]: Mounting file system completed.
Dez 29 12:21:39  kernel: BTRFS info (device dm-0): enabling ssd optimizations
Dez 29 12:21:42  systemd-homework[3994]: Discarded unused 931.4G.
Dez 29 12:21:42  systemd-homework[3994]: Operating on partition device /dev/disk/by-uuid/879b8acc-8d17-4ca2-bd2a-62d698e8e277, using parent device.
Dez 29 12:21:42  systemd-homework[3994]: Discovered used loopback device (null).
Dez 29 12:21:42  systemd-homework[3994]: offset = 1048576, size = 1000203091968, image = 1000204886016
Dez 29 12:21:42  systemd-homework[3994]: New partition doesn't fit into backing storage, refusing.
Dez 29 12:21:42  systemd-homework[3994]: Discarded unused 2.0G.
Dez 29 12:21:42  systemd-homed[411]: block device /sys/devices/virtual/block/dm-0 has been removed.
Dez 29 12:21:42  systemd-homed[411]: block device /sys/devices/virtual/block/dm-0 has been removed.
Dez 29 12:21:42  systemd-homed[411]: Activation failed: Invalid argument
Dez 29 12:21:42  systemd-homed[411]: test_remote: changing state activating → inactive

I dont get why this is not working especially as I had this working yesterday with my old installation. Any hints would be appreciated!

Offline

#2 2022-01-01 08:25:43

MMime
Member
Registered: 2020-04-07
Posts: 3

Re: systemd homed cannot use user on extra harddrive anymore

I have (different) problems with systemd v250 leading to the same kind of error (`Failed to execute...`). Could you try downgrading to a previous version just to make sure this is a bug and not a configuration error?

Offline

Board footer

Powered by FluxBB