!PSmBFWNKoXmlQBzUQf:helsinki-systems.de

Stage 1 systemd

81 Members
systemd in NixOs's stage 1, replacing the current bash tooling https://github.com/NixOS/nixpkgs/projects/5127 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
31 May 2023
@lily:lily.flowers@lily:lily.flowersSo it's actually the mapped device that times out, not the unlocking. So you can probably set a fstab option to disable systemd timeout (i forget what the exact option is)11:04:35
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Lily Foster: is it the mapped device or the physical device? 11:38:57
@elvishjerricco:matrix.org@elvishjerricco:matrix.org Copa Dium: could try boot.initrd.luks.devices.encryptedpool.crypttabExtraOpts = ["device-timeout=0"]; 11:39:57
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgI'm thinking we need to add a NixOS option for that and default it to zero to retain the default behavior of the old initrd11:40:36
@lily:lily.flowers@lily:lily.flowers
In reply to @elvishjerricco:matrix.org
Lily Foster: is it the mapped device or the physical device?
Mapped. Physical device obviously already exists since it prompts for password on mine
11:40:36
@lily:lily.flowers@lily:lily.flowersIf I don't enter password it times out on the mapper device though11:40:51
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgAh11:40:57
@lily:lily.flowers@lily:lily.flowers
In reply to @elvishjerricco:matrix.org
Copa Dium: could try boot.initrd.luks.devices.encryptedpool.crypttabExtraOpts = ["device-timeout=0"];
That would be if physical device was not present. Which should be rare? In this case it was because lack of drivers
11:41:36
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgYea11:41:52
@lily:lily.flowers@lily:lily.flowersIdk if we should remove timeouts for physical devices unless user asks for it11:41:55
@lily:lily.flowers@lily:lily.flowers(Mapped devices though is eh)11:42:02
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgThat's fair11:42:02
@copadium:matrix.orgCopa Dium
In reply to @lily:lily.flowers
That would be if physical device was not present. Which should be rare? In this case it was because lack of drivers
Yeah my problem was fixed by adding the module. I get a prompt now and can boot. :)
11:42:40
@copadium:matrix.orgCopa DiumBut I can test what happens if I don't enter anything for a minute or so11:42:56
@copadium:matrix.orgCopa DiumYeah it spawns an emergency shell11:43:20
@copadium:matrix.orgCopa Diumjournalctl says it is zfs import that times out though11:44:32
@copadium:matrix.orgCopa Dium
[...] many more
May 31 11:42:49 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:50 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:51 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:52 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:53 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:55 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:56 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:57 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:58 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:42:59 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:43:00 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:43:01 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:43:02 localhost zfs-import-rpool-start[196]: Pool rpool in state MISSING, waiting
May 31 11:43:03 localhost zfs-import-rpool-start[441]: cannot import 'rpool': no such pool available
May 31 11:43:03 localhost systemd[1]: zfs-import-rpool.service: Main process exited, code=exited, status=1/FAILURE
May 31 11:43:03 localhost systemd[1]: zfs-import-rpool.service: Failed with result 'exit-code'.
May 31 11:43:03 localhost systemd[1]: Failed to start Import ZFS pool "rpool".
May 31 11:43:03 localhost systemd[1]: zfs-import-rpool.service: Consumed 1.934s CPU time.
May 31 11:43:03 localhost systemd[1]: Reached target Local File Systems.
May 31 11:43:03 localhost systemd[1]: Starting impermanence-root.service...

looks like this

11:45:28
@copadium:matrix.orgCopa Diummaybe import service is not started after the luks service? Do i have to add a dependency?11:46:17
@lily:lily.flowers@lily:lily.flowersThe dependency is already correct it just times out11:46:38
@lily:lily.flowers@lily:lily.flowersProbably11:46:43
@lily:lily.flowers@lily:lily.flowers(On mobile and didn't read log)11:46:50
@copadium:matrix.orgCopa DiumAlso I get kicked out of the emergency shell after another minute and a second one is spawned...11:47:13
@elvishjerricco:matrix.org@elvishjerricco:matrix.orgoh that's weird11:47:23
@lily:lily.flowers@lily:lily.flowers
In reply to @copadium:matrix.org
Also I get kicked out of the emergency shell after another minute and a second one is spawned...
Oh delightful
11:47:36
@lily:lily.flowers@lily:lily.flowersIs there a timeout on the emergency shell itself 👀11:47:59
@copadium:matrix.orgCopa DiumIt only happens once11:48:16

Show newer messages


Back to Room ListRoom Version: 6