| 31 May 2023 |
 @lily:lily.flowers | (Mapped devices though is eh) | 11:42:02 |
 ElvishJerricco | 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 | 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 |
| ElvishJerricco | In reply to @lily:lily.flowers
The dependency is already correct it just times out Well if the cryptsetup service never finished, then the import service probably shouldn't have started? | 11:48:34 |
| ElvishJerricco | It should have After=cryptsetup.target though so I'm not sure why that wouldn't have been the case | 11:48:54 |
| Copa Dium | The log looks like it does try to import the rpool a second time :/
But I have no idea how all of this works.. | 11:49:37 |
 @linus:schreibt.jetzt | In reply to @elvishjerricco:matrix.org
It should have After=cryptsetup.target though so I'm not sure why that wouldn't have been the case if it doesn't have a Wants or Requires on it? | 11:49:51 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
Well if the cryptsetup service never finished, then the import service probably shouldn't have started? True | 11:50:01 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
It should have After=cryptsetup.target though so I'm not sure why that wouldn't have been the case Yeah that should have happened. Idk I don't use zfs though | 11:50:32 |
| ElvishJerricco | In reply to @linus:schreibt.jetzt
if it doesn't have a Wants or Requires on it? We do have sysinit.target.wants/cryptsetup.target -> ../cryptsetup.target, so it should already be wanted by the initial transaction... | 11:50:58 |
| ElvishJerricco | Ok so three separate problems then:
- A mount can timeout waiting for its mapped device
- The ZFS import service can timeout
| 11:52:17 |
| ElvishJerricco | * Ok so three separate problems then:
- A mount can timeout waiting for its mapped device
- The ZFS import service can timeout
- emergency.service can timeout
| 11:52:25 |
| Copa Dium | Maybe 4. because I get this emergency.service: Executable /nix/store/jmd50jrn6l2bqqm5dvq6xvripzvr3npc-systemd-stage-1-network-253.3/bin/plymouth missing, skipping: No such file or directory, but I don't have or want plymouth | 11:53:39 |
| ElvishJerricco | that's not relevant | 11:53:50 |
| ElvishJerricco | that's just systemd being silly | 11:53:57 |
| ElvishJerricco | but it's harmless | 11:54:03 |
| Copa Dium | Okay | 11:54:28 |
