| 24 Apr 2023 |
 oddlama | Nvm you beat me to it | 15:20:33 |
| oddlama | I guess I could just manually start the things I want to debug from the emergency shell then | 15:21:34 |
 @elvishjerricco:matrix.org | yea, rescue or emergency mode in initrd will start very nearly nothing | 15:22:19 |
| @elvishjerricco:matrix.org | it won't even try mounting /sysroot and friends because those go under initrd-fs.target instead of local-fs.target | 15:22:42 |
| @elvishjerricco:matrix.org | * rescue won't even try mounting /sysroot and friends because those go under initrd-fs.target instead of local-fs.target | 15:22:56 |
| @elvishjerricco:matrix.org | but btw a very convenient way to tell it "please just boot now" is systemctl default | 15:23:39 |
| oddlama | hmm emergency is so early that my usb keyboard is not ininitialized 🫠| 15:24:34 |
| @elvishjerricco:matrix.org | ah, yea that would be a reason to use rescue | 15:24:45 |
 @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
the earliest possible shell would be rd.systemd.unit=emergency.target, since emergency mode literally only starts a shell by default I've had emergency.target do weird things, but I forget what exactly at the moment. When I want a shell that early I use emergency.service | 15:24:47 |
| @elvishjerricco:matrix.org | get your kernel modules loaded | 15:24:48 |
| @elvishjerricco:matrix.org | yea emergency mode really isn't meant to be manually targeted. It's really meant to be transitioned too in the event of boot failure | 15:25:34 |
| @elvishjerricco:matrix.org | * yea emergency mode really isn't meant to be manually targeted. It's really meant to be transitioned to in the event of boot failure | 15:25:44 |
| oddlama | that makes sense | 15:26:10 |
| oddlama | is there a wiki page yet to collect some of this stuff? | 15:27:04 |
| @elvishjerricco:matrix.org | not that I know of | 15:27:14 |
| oddlama | Rescue works fine :) | 15:30:55 |
| oddlama | Not sure why my sshd doesn't come up, systemd says it's started and exited, but there are no journal messages about any of it :/ | 15:31:55 |
| @elvishjerricco:matrix.org | There's no reason that would come up on its own; you started it manually? | 15:32:48 |
| oddlama | I just used boot.initrd.networking.ssh to configure it, and it is seemingly started before my zfs is unlocked | 15:33:44 |
| oddlama | the rescue shell comes after unlocking | 15:34:04 |
| @elvishjerricco:matrix.org | wait wut | 15:34:41 |
| @elvishjerricco:matrix.org | oh | 15:34:49 |
| @elvishjerricco:matrix.org | are you using zfs? | 15:34:56 |
| oddlama | yep | 15:35:10 |
| @elvishjerricco:matrix.org | https://github.com/NixOS/nixpkgs/pull/227208 | 15:35:18 |
| @elvishjerricco:matrix.org | zfs-import-${pool}.service is in local-fs.target, which is incorrect in initrd | 15:35:46 |
| @elvishjerricco:matrix.org | but that incorrectness does result in it being pulled in by rescue.target | 15:36:04 |
| oddlama | I see. It's probably not correct but in my case it shouldn't be a problem either | 15:36:47 |
| @elvishjerricco:matrix.org | that doesn't explain why sshd is starting though | 15:36:50 |
| oddlama | Wait I have to add some utils to the initrd before continuing, I can't even ping :P | 15:37:23 |
