home manager module fails to mount.

[antotocar34]

Oct 13 22:33:17 HOSTNAME mount[6995]: 2025/10/13 22:33:17 Waiting for mountpoint to be created...

Using home manager module on manjaro linux.

Configuration is more or less as follows

imports = [                                                                                                                                                       
  inputs.agefs.homeModules.agefs                                                                                                                                  
];                                                                                                                                                                

age = {                                                                                                                                                           
  package = inputs.agefs.packages.${system}.agefs;                                                                                                                

  ...
};

Any idea on how to troubleshoot this effectively?

[andre4ik3]

Hm, can you try manually mounting it by seeing what command it runs and mounting it manually, with the flag -f so it runs in the foreground?

You can find the command by using systemctl --user cat and then the mount path with .mount at the end. You can probably just type systemctl --user cat secrets.mount and hit tab on the last part and it should autocomplete:

The command would be agefs <What> <Where> -o <Options> -f, so for the above example, it would be:

agefs /nix/store/bwrymn50qvww7fg8v0ra0bfvzv3i7hrg-agefs-meta.json /data/user/user/.local/share/secrets -o identity=/data/user/user/.local/share/age/identity,identity=/data/user/user/.ssh/id_ed25519,x-gvfs-hide -f

Then it will output the error if any. (Note that you need to umount the mountpoint after done, simply pressing CTRL+C will leave the mountpoint but will cause an error "device not configured" when accessing it)

Currently it doesn't put logs in journald because systemd has some weird requirements for mount units, notably it must be a "oneshot"-style unit and the filesystem must be mounted after it's finished, otherwise it's an error. And it can't run in the foreground either, else it will time out and be killed. So it has to fork into the background. But I'll try to add some kind of log forwarding so the logs don't just get thrown away.