In reply to @lily:lily.flowers
(Genuinely though, even if you don't end up using systemd-initrd, at least share the config you were having issues with and I can at least look and see what was going on and if we need to fix nixos bugs)

In reply to @winterqt:nixos.dev

  boot.initrd.systemd.services.wipe-root = {
    wantedBy = [ "cryptsetup.target" ];
    after = [ "cryptsetup.target" ];
    before = [ "local-fs.target" ];

anyone know why this causes (apparently) a dep cycle?

  boot.initrd.systemd.services.rollback = {
    description = "Rollback ZFS datasets to a pristine state";
    wantedBy = [
      "initrd.target"
    ]; 
    after = [
      "zfs-import-zroot.service"
    ];
    before = [ 
      "sysroot.mount"
    ];
    path = with pkgs; [
      zfs
    ];
    unitConfig.DefaultDependencies = "no";
    serviceConfig.Type = "oneshot";
    script = ''
      set -ex
      zfs rollback -r zroot/local/root@blank && echo "rollback complete"
    '';
  };

In reply to @lily:lily.flowers
Oh actually, was it just timing out?

In reply to @hexa:lossy.network
will gladly repost in eternity 🙂

In reply to @winterqt:nixos.dev
Maybe? But like... crashing to an emergency shell with no other messages is... not good UX.

In reply to @hexa:lossy.network
team randomencrypted swap 😛

In reply to @elvishjerricco:matrix.org
I mean, what else is there to do? If a critical thing fails, an emergency shell is really the only option

In reply to @elvishjerricco:matrix.org
maybe we could make emergency.target output systemctl status --failed before starting emergency.service?