| 7 Dec 2022 |
 @hexa:lossy.network | and mount claims things are mounted to /sysroot, /sysroot/state, /sysroot/home | 20:13:42 |
| @hexa:lossy.network | so I wonder whether the mounting order is off 😕 | 20:13:51 |
 @elvishjerricco:matrix.org | hexa: sometimes I've had trouble with file systems being unmounted before hitting switch-root for a variety of reasons. That's one of the reasons we need to switch to initrd-fs.target instead of local-fs.target | 20:57:24 |
| @elvishjerricco:matrix.org | Do you see it saying it's unmounting stuff? | 20:57:32 |
| @hexa:lossy.network | no unmounting | 20:57:49 |
| @hexa:lossy.network | 
Download PXL_20221207_204931189.jpg | 20:58:15 |
| @elvishjerricco:matrix.org | It's very unlikely for the mount order to be off. Systemd handles that hierarchaly | 20:58:25 |
| @hexa:lossy.network | yeah, I expected that | 20:58:35 |
| @hexa:lossy.network | current working theory is that it needs to be after zfs-import.target and before initrd-root-fs.target | 20:58:45 |
| @elvishjerricco:matrix.org | I doubt that | 20:59:42 |
| @elvishjerricco:matrix.org | For one thing, we're not using initrd-root-fs.target like we're supposed to be for the same kinds of reasons we're not using initrd-fs.target like we're supposed to | 21:00:45 |
| @elvishjerricco:matrix.org | But also ZFS allows you to rollback a mounted dataset no problem | 21:01:00 |
| @hexa:lossy.network | but what does that mean for mountpoints that go missing? | 21:01:16 |
| @elvishjerricco:matrix.org | It makes no sense to me that mountpoints are going missing :P | 21:01:52 |
| @elvishjerricco:matrix.org | hexa: In the emergency shell, does systemctl say the mount units are still active? | 21:04:16 |
| @hexa:lossy.network | yes | 21:05:01 |
| @elvishjerricco:matrix.org | Anything interesting in journalctl -u initrd-nixos-activation.service? | 21:05:55 |
| @hexa:lossy.network | 
Download 20221207_220555_7472682676845992109.jpg | 21:06:14 |
| @hexa:lossy.network | ... does not look like a NixOS installation - not activating | 21:07:17 |
| @elvishjerricco:matrix.org | ahhh | 21:07:28 |
| @hexa:lossy.network | hm, /nix requiredForBoot? 😄 | 21:07:41 |
| @hexa:lossy.network | not sure if I set it or not 🙂 | 21:08:06 |
| @elvishjerricco:matrix.org | No, I see it saying Mounting /sysroot/nix in one of those screenshots | 21:08:27 |
| @elvishjerricco:matrix.org | It's missing /etc/NIXOS | 21:08:32 |
| @hexa:lossy.network | that gets mounted via impermanence 😲 | 21:08:56 |
| @hexa:lossy.network | well bind-mounted | 21:09:20 |
| @hexa:lossy.network | In reply to @hexa:lossy.network
... does not look like a NixOS installation - not activating this begins with /nix/store/....-sytem | 21:10:01 |
| @hexa:lossy.network | so I'm not sure how this would be about /etc/nixos | 21:10:12 |
| @elvishjerricco:matrix.org | hexa: Oh wait, I misremembered what generates that error. It's this: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/system/boot/systemd/initrd.nix#L487 | 21:11:42 |
| @elvishjerricco:matrix.org | I guess that makes sense if you said /sysroot is empty? | 21:12:22 |
