| 31 May 2023 |
 @lily:lily.flowers | In reply to @copadium:matrix.org
I also moved the system to a vm, so your kernel module guess could be pretty on point Oh yeah prob that then. If the dev doesn't exist there then that's most likely it | 10:57:46 |
 Copa Dium | Yeah you seem to be right! Thanks a lot for the help, probably virto_blk is missing | 10:58:33 |
| Copa Dium | One more thing, do you know how I can disable the timeout that spawns the emergency shell? I'd like to remove unlock the system later and if it fails after a minute that'd be annoying :D | 10:59:13 |
| Copa Dium | * One more thing, do you know how I can disable the timeout that spawns the emergency shell? I'd like to remote unlock the system later and if it fails after a minute that'd be annoying :D | 10:59:23 |
| @lily:lily.flowers | So 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 | Lily Foster: is it the mapped device or the physical device? | 11:38:57 |
| @elvishjerricco:matrix.org | Copa Dium: could try boot.initrd.luks.devices.encryptedpool.crypttabExtraOpts = ["device-timeout=0"]; | 11:39:57 |
| @elvishjerricco:matrix.org | I'm thinking we need to add a NixOS option for that and default it to zero to retain the default behavior of the old initrd | 11:40:36 |
| @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 | If I don't enter password it times out on the mapper device though | 11:40:51 |
| @elvishjerricco:matrix.org | Ah | 11:40:57 |
| @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 | Yea | 11:41:52 |
| @lily:lily.flowers | Idk if we should remove timeouts for physical devices unless user asks for it | 11:41:55 |
| @lily:lily.flowers | (Mapped devices though is eh) | 11:42:02 |
| @elvishjerricco:matrix.org | That's fair | 11:42:02 |
| Copa 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 |
| Copa Dium | But I can test what happens if I don't enter anything for a minute or so | 11:42:56 |
| Copa Dium | Yeah it spawns an emergency shell | 11:43:20 |
| Copa Dium | journalctl says it is zfs import that times out though | 11:44:32 |
| Copa 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 |
| Copa Dium | maybe import service is not started after the luks service? Do i have to add a dependency? | 11:46:17 |
| @lily:lily.flowers | The dependency is already correct it just times out | 11:46:38 |
| @lily:lily.flowers | Probably | 11:46:43 |
| @lily:lily.flowers | (On mobile and didn't read log) | 11:46:50 |
| Copa Dium | Also I get kicked out of the emergency shell after another minute and a second one is spawned... | 11:47:13 |
| @elvishjerricco:matrix.org | oh that's weird | 11:47:23 |
| @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 | Is there a timeout on the emergency shell itself 👀 | 11:47:59 |
| Copa Dium | It only happens once | 11:48:16 |
