| 31 May 2023 |
 @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:matrix.org | 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:matrix.org | 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:matrix.org | * 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:matrix.org | that's not relevant | 11:53:50 |
| @elvishjerricco:matrix.org | that's just systemd being silly | 11:53:57 |
| @elvishjerricco:matrix.org | but it's harmless | 11:54:03 |
| Copa Dium | Okay | 11:54:28 |
| @elvishjerricco:matrix.org | ok so looking at my system that has zfs on luks: It looks like the zfs import service is starting before we reach cryptsetup.target, which is odd | 11:54:34 |
| Copa Dium | Also are you sure the emergency shell times out? In my journal it looks like there's just a second zfs-import-rpool-start that spawns a second emergency shell when it fails | 11:55:01 |
| @elvishjerricco:matrix.org | In reply to @copadium:matrix.org
Also are you sure the emergency shell times out? In my journal it looks like there's just a second zfs-import-rpool-start that spawns a second emergency shell when it fails Oh I see. That's weird | 11:55:22 |
| Copa Dium | Would the full log be helpful to you? | 11:55:56 |
| @elvishjerricco:matrix.org | possibly? | 11:56:02 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
but it's harmless (Well it's not harmless exactly if you do have plymouth because plymouth crashes instead of gracefully exits when entering emergency shell right now. I have a branch with a two line fix though..... just need to find time in the next week for nixpkgs work) | 11:56:10 |
| @elvishjerricco:matrix.org | oh that's why that happens? wut | 11:56:37 |
| @lily:lily.flowers | (Not that that's fatal or anything. But kinda silly) | 11:56:45 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
oh that's why that happens? wut Yeah plymouth expects systemd to stop it when entering emergency shell. That seems extraordinarily dumb to have that inter-project dependency. Systemd assumes plymouth is in its install bindir which is also silly | 11:57:43 |
| Copa Dium | Also interesting is that the ssh daemon is killed when the emergency shell enters, which is weird :D | 11:58:02 |
| @lily:lily.flowers | My fix just adds plymouth-quit-wait to be wanted by and before emergency and rescue shells | 11:58:13 |
| Copa Dium | Do you have a preferred pastebin like service around here? | 11:58:26 |
| @lily:lily.flowers | In reply to @copadium:matrix.org
Do you have a preferred pastebin like service around here? (One that works and preferably without ads for me. Otherwise I really don't care myself, but I imagine ElvishJerricco is more likely to be looking at them since I'm on mobile and really need to be getting ready to leave for $dayjob) | 11:59:25 |
| @elvishjerricco:matrix.org | In reply to @copadium:matrix.org
Also interesting is that the ssh daemon is killed when the emergency shell enters, which is weird :D Yea, I considered adding boot.initrd.systemd.targets.emergency.wants = ["network.target"]; when initrd networking is enabled, but ultimately decided against it. You can totally add that to your config though to keep networking up in an emergency | 11:59:48 |
| @elvishjerricco:matrix.org | er, actually, I guess sshd.service isn't wanted by network.target... | 12:00:36 |
| @elvishjerricco:matrix.org | so that wouldn't actually work | 12:01:09 |
 @gdamjan:spodeli.org | you can add that too :) | 12:01:47 |
| Copa Dium | In reply to @elvishjerricco:matrix.org
possibly? https://hastebin.skyra.pw/itupozaruc.yaml | 12:02:25 |
| @elvishjerricco:matrix.org | ok so there's initrd-fs.target: Triggering OnFailure= dependencies. three different times | 12:03:57 |
| @elvishjerricco:matrix.org | and finally initrd-switch-root.service: Triggering OnFailure= dependencies. once | 12:04:09 |
