!oNSIfazDqEcwhcOjSL:matrix.org

disko

382 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko100 Servers

Load older messages


SenderMessageTime
10 Mar 2026
@crony:cronyakatsuki.xyzCrony Akatsuki (balkan/slav) np, tho that will prob be tomorrow for me (it's 7pm here, gonna go to sleep soon)18:04:34
@magic_rb:matrix.redalder.orgmagic_rb 7pm here too :P 18:04:48
@magic_rb:matrix.redalder.orgmagic_rbMy sleep schedule is just fucked up18:04:54
@crony:cronyakatsuki.xyzCrony Akatsuki (balkan/slav) my sleep schedule moves according to my work, sometimes I wake up at 3am sometimes at 8am18:05:22
12 Mar 2026
@sebastian:srx.digitalcrstl changed their profile picture.18:02:38
14 Mar 2026
@em:axolotlsin.spaceem joined the room.04:39:55
@matthewcroughan:defenestrate.itmatthewcroughan Looks like disko's image builder just kernel panics these days Mic92 16:33:53
@matthewcroughan:defenestrate.itmatthewcroughan
ed-disko-images> [    5.126922] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000400
ed-disko-images> [    5.128633] CPU: 0 UID: 0 PID: 1 Comm: 1qv9fdw1cl7j7z4 Tainted: P           O        6.19.6 #1-NixOS PREEMPT(lazy) 
ed-disko-images> [    5.130954] Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
ed-disko-images> [    5.132205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022
ed-disko-images> [    5.134054] Call Trace:
ed-disko-images> [    5.134626]  <TASK>
ed-disko-images> [    5.135138]  dump_stack_lvl+0x5d/0x80
ed-disko-images> [    5.136015]  vpanic+0xdb/0x2d0
ed-disko-images> [    5.136725]  panic+0x6b/0x6b
ed-disko-images> [    5.137399]  do_exit.cold+0x15/0x15
ed-disko-images> [    5.138200]  ? handle_mm_fault+0x1d9/0x2e0
ed-disko-images> [    5.139150]  do_group_exit+0x2d/0xc0
ed-disko-images> [    5.139994]  __x64_sys_exit_group+0x18/0x20
ed-disko-images> [    5.140943]  x64_sys_call+0x14fd/0x1510
ed-disko-images> [    5.141801]  do_syscall_64+0xb6/0x560
ed-disko-images> [    5.142684]  ? exc_page_fault+0x6a/0x150
ed-disko-images> [    5.143587]  entry_SYSCALL_64_after_hwframe+0x77/0x7f
ed-disko-images> [    5.144724] RIP: 0033:0x7feac62ee198
ed-disko-images> [    5.145541] Code: ff 64 89 02 eb b4 e8 97 4e 04 00 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 8b 35 55 dc 10 00 eb 04 0f 1f 00 f4 b8 e7 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 f0 f7 d8 64 89 06 eb e9 66 0f 1f 84 00 00 00
ed-disko-images> [    5.149659] RSP: 002b:00007fff8e855088 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
ed-disko-images> [    5.151342] RAX: ffffffffffffffda RBX: 00007feac63fdfc8 RCX: 00007feac62ee198
ed-disko-images> [    5.152927] RDX: 0000000000000000 RSI: ffffffffffffffa0 RDI: 0000000000000004
ed-disko-images> [    5.154477] RBP: 00007fff8e8550e0 R08: 0000000000000000 R09: 0000000000000000
ed-disko-images> [    5.156048] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
ed-disko-images> [    5.157606] R13: 0000000000000004 R14: 00007feac63fc680 R15: 00007feac63fdfe0
ed-disko-images> [    5.159192]  </TASK>
ed-disko-images> [    5.160070] Kernel Offset: 0x3a00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
ed-disko-images> [    5.748001] Rebooting in 1 seconds..
ed-disko-images> [2026-03-14T16:33:15Z INFO  virtiofsd] Client disconnected, shutting down
ed-disko-images> [2026-03-14T16:33:15Z INFO  virtiofsd] Client disconnected, shutting down
ed-disko-images> Virtual machine didn't produce an exit code.
error: Cannot build '/nix/store/afg5rnkl94mf99wk6sx0hvkydrwkwa2g-ed-disko-images.drv'.
16:34:13
@matthewcroughan:defenestrate.itmatthewcroughanHow does the CI not catch this?16:35:10
@joerg:thalheim.ioMic92Maybe it's not reproducing in other machines that are not yours.16:35:59
@matthewcroughan:defenestrate.itmatthewcroughanthe fact that the disko image builder, inherits the kernel of the caller, is an architectural mistake, don't you think?16:36:23
@matthewcroughan:defenestrate.itmatthewcroughanthis means CI can't really tell you anything16:36:38
@matthewcroughan:defenestrate.itmatthewcroughanand in the case of building images for a raspberry pi, that will never work16:37:17
@matthewcroughan:defenestrate.itmatthewcroughanbecause this kernel is specific to the Pi, and won't boot under qemu16:37:26
@joerg:thalheim.ioMic92not sure we test on aarch64 at the moment16:37:41
@matthewcroughan:defenestrate.itmatthewcroughanah that too16:37:45
@matthewcroughan:defenestrate.itmatthewcroughanbut this is x86 in my case anyway16:37:55
@joerg:thalheim.ioMic92but also not sure if this is that is the problem either16:37:56
@matthewcroughan:defenestrate.itmatthewcroughan
  networking.hostId = "b7f38c2e"; # ZFS needs this set
  services.zfs.autoScrub.enable = true;
  boot = {
    supportedFilesystems = [ "zfs" ];
  };
  disko.devices = {
    disk = {
      disk1 = {
        device = "/dev/disk/by-id/usb-Realtek_RTL9210B-CG_012345679039-0:0";
        type = "disk";
        content = {
          type = "gpt";
          partitions = {
            ESP = {
              type = "EF00";
              size = "2G";
              content = {
                type = "filesystem";
                format = "vfat";
                mountpoint = "/boot";
              };
            };
            zfs = {
              size = "100%";
              content = {
                type = "zfs";
                pool = "edpool";
              };
            };
          };
        };
      };
    };
    zpool = {
      edpool = {
        type = "zpool";
        rootFsOptions = {
          acltype = "posixacl";
          compression = "zstd";
          dnodesize = "auto";
          normalization = "formD";
          relatime = "on";
          xattr = "sa";
        };
        options = {
          ashift = "12";
          autotrim = "on";
        };

        datasets = {
          "root" = {
            type = "zfs_fs";
            options = {
              mountpoint = "legacy";
            };
            mountpoint = "/";
          };
          "nix" = {
            type = "zfs_fs";
            options.mountpoint = "legacy";
            mountpoint = "/nix";
          };
          "var" = {
            type = "zfs_fs";
            options.mountpoint = "legacy";
            mountpoint = "/var";
          };
          "home" = {
            type = "zfs_fs";
            mountpoint = "/home";
            options.mountpoint = "legacy";
          };
        };
      };
    };
  };
}
16:38:25
@matthewcroughan:defenestrate.itmatthewcroughanThat's my disko config16:38:28
@matthewcroughan:defenestrate.itmatthewcroughan I was thinking btw, disko could auto generate the networking.hostId based on a hash of the device 16:38:52
@matthewcroughan:defenestrate.itmatthewcroughan * I was thinking btw, disko could auto generate the networking.hostId based on a hash of the device in pure nix 16:38:55
@matthewcroughan:defenestrate.itmatthewcroughanone less thing to worry about 16:39:01
@joerg:thalheim.ioMic92in srvos we set a fixed hostid16:39:43
@joerg:thalheim.ioMic92But it feels a bit overarching for disko to set this. It's a disk partitioning framework16:40:19
@joerg:thalheim.ioMic92* in srvos we set a fixed hostid for all machines16:40:24
@joerg:thalheim.ioMic92* But it feels a bit overarching for disko to set this. It's a disk partitioning framework and this feels more like general NixOS configuration16:40:42
@matthewcroughan:defenestrate.itmatthewcroughanAh sure, I guess you could just do the hashing trick that I mentioned in your own config16:47:24
@joerg:thalheim.ioMic92honestly I don't think this even needs hashing16:48:39
@joerg:thalheim.ioMic92I have seen no usecase yet for a per machine hostid, except if you have zfs hosted on iscsi network block devices and want to prevent accidents.16:49:11

Show newer messages


Back to Room ListRoom Version: 10