| 30 Apr 2023 |
 oddlama | Also not sure if this is related, but sometimes when I am in the middle of entering the password via ssh and systemd-tty-ask-password-agent, the agent seems to be reset and the prompt exits. | 14:02:05 |
 @elvishjerricco:matrix.org | Janne Heß: By default, JobTimeoutSec is set to 0 for crypttab stuff. So there should already be no timeout | 20:01:20 |
| @elvishjerricco:matrix.org | (I believe we do not do this for zfs's import service, so zfs native encryption will timeout; we should change that) | 20:02:25 |
 @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
Janne Heß: By default, JobTimeoutSec is set to 0 for crypttab stuff. So there should already be no timeout There definitely is one. I'll see if I can figure out why in a bit | 20:04:25 |
| @lily:lily.flowers | (I do the same reboot computer and go fetch a coffee thing and occasionally come back to it timed out) | 20:05:04 |
 @janne.hess:helsinki-systems.de | In reply to @elvishjerricco:matrix.org
Janne Heß: By default, JobTimeoutSec is set to 0 for crypttab stuff. So there should already be no timeout That's true but then waiting for the decrypted device times out | 20:05:12 |
| @janne.hess:helsinki-systems.de | 
Download 20230430_220529_474826277132580486.jpg | 20:05:42 |
| @elvishjerricco:matrix.org | Hmm ok | 20:05:44 |
| @elvishjerricco:matrix.org | Well there's fstab options for that | 20:05:54 |
| @janne.hess:helsinki-systems.de | Oh there is? I will check once I find the time | 20:06:12 |
| @janne.hess:helsinki-systems.de | Thanks for the pointer :) | 20:06:23 |
| @elvishjerricco:matrix.org | Hm but that says the device job timed out.... | 20:06:38 |
| @elvishjerricco:matrix.org | Oh I see | 20:08:01 |
| @elvishjerricco:matrix.org | Cryptsetup-generator probably sets the timeout for the physical device to zero, but leaves it default for the mapper device and the FS itself | 20:08:41 |
| 2 May 2023 |
 Arian | ElvishJerricco: could you open a nixpkgs issue about systemd-repart in initrd being borked and assign it to me? | 20:59:48 |
| Arian | I can make some time tomorrow to fix it | 21:00:00 |
| Arian | though i do think it can be a matter of opinion https://github.com/systemd/systemd/blame/main/units/systemd-repart.service.in#L25 | 21:02:47 |
| Arian | upstream runs after /sysusr is mounted (which will become /usr after switchroot) so it definitely expects the main software to already be mounted and only add additional partitions for storage not software | 21:03:29 |
| Arian | I think for us that'd mean run before root but after nix.mount | 21:03:52 |
| Arian | I think that makes sense for the nixos case if /nix is on separate partition | 21:05:10 |
| Arian | but not sure.... | 21:05:19 |
| @elvishjerricco:matrix.org | Arian: Yea I was looking into this last night, and there isn't really a clean answer without patching systemd or something. It really expects at least an OS to be installed on a disk, but in NixOS we go even further and don't even have an OS on a disk. The other thing is that we actually can't just use /sysroot; we would have to wait for nixos-activation.service to run so that /etc is set up | 21:19:39 |
| Arian | I think doing systemd-repart --empty=allow /dev/vda is the way to go | 21:20:17 |
| Arian | for nixos | 21:20:24 |
| Arian | that will re-partition the disk even if it doesnt have a GPT partition table | 21:20:42 |
| Arian | and run that in initrd | 21:20:59 |
| @elvishjerricco:matrix.org | Yea, I'm really starting to think that the only sane option is to put the config files in the initrd and do systemd-repart --empty=allow ${config.fileSystems."/".device} except that isn't quite right because we have to point at the root disk, not the root partition | 21:22:27 |
| @elvishjerricco:matrix.org | Which makes me think we actually need a boot.initrd.systemd.repart.device option | 21:23:21 |
| Arian | boot.initrd.systemd/repart.device | 21:23:25 |
| Arian | yeh | 21:23:29 |
