!oNSIfazDqEcwhcOjSL:matrix.org

disko

364 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko93 Servers

Load older messages


SenderMessageTime
29 Jul 2025
@sinan:sinanmohd.comsinan

but when i tried to mount /boot it errored out and i got the following in dmesg

[ 263.242473] FAT-fs (nvme0n2p1): invalid media value (0x7d)
[ 263.242947] FAT-fs (nvme0n2p1): Can't find a valid FAT filesystem

13:23:18
@sinan:sinanmohd.comsinani don't think it's related since the original error was about the root volume 13:23:38
@sinan:sinanmohd.comsinanas a last effort, i'll switch away from nvme and try booting from a normal disk i don't think it's diskio related, should be probably handled by nixos-hardware i recall having a similar problem when using diskio+aws, it's not just azure, worked on hetzner tho13:27:26
@sinan:sinanmohd.comsinannope, no luck13:51:59
30 Jul 2025
@sinan:sinanmohd.comsinangot serial, the drive is not showing up in initrd https://md-visiqgtxcng5llql.z50.blob.storage.azure.net/10226849-9c65-4a95-be56-538fbc5d6d27/devbox-master.e245caec-1370-4dfa-af2f-019b16af6308.serialconsole.log?sv=2018-03-28&sr=b&sig=8nfIKVbk6%2bf2%2bJ%2fRiI4Eil6rBEuC6ehEIorhID9VbNk%3d&se=2025-07-30T05%3a44%3a26Z&sp=r03:44:59
@sinan:sinanmohd.comsinan finally worked, about fuking time
just lsmod | cut -f1 -d' ' from the ubuntu vm, got rid of zfs & spl and added rest to boot.initrd.kernelModules
06:05:27
31 Jul 2025
@maxcf:matrix.orgMax joined the room.17:11:35
2 Aug 2025
@sinan:sinanmohd.comsinan changed their profile picture.06:58:26
@sinan:sinanmohd.comsinan 06:58:39
@sinan:sinanmohd.comsinan 06:58:46
3 Aug 2025
@adrielus:matrix.orgprescientmoon changed their display name from Adriel to prescientmoon.14:31:40
@sinan:sinanmohd.comsinan changed their profile picture.15:07:47
@zsuper:matrix.orgzsuper joined the room.20:28:38
@zsuper:matrix.orgzsuper

hey everyone, im very new to disko and disk partitioning/management in general, but i had a few questions as i prep to use nixos-anywhere to setup/expand my homelab.

i have 5 Intel NUC computers, each with a SSD and a 1.8T HDD. The issue is that some of them report /dev/sda to be the SSD and /dev/sdb to be the HDD, while some do reverse. is this a problem when working with disko? aka would i be able to reuse the same disko config for each one? or do i necessarily need to tailor each one specifically to the output of lsblk?

20:33:01
@zsuper:matrix.orgzsuper *

hey everyone, im very new to disko and disk partitioning/management in general, but i had a few questions as i prep to use nixos-anywhere to setup/expand my homelab.

i have 5 Intel NUC computers, each with a SSD and a 1.8T HDD. The issue is that some of them report /dev/sda to be the SSD and /dev/sdb to be the HDD, while some do reverse. is this a problem when working with disko? aka would i be able to reuse the same disko config for each of the 5 computers? or do i necessarily need to tailor each one specifically to the output of lsblk?

20:33:24
@zsuper:matrix.orgzsuper *

hey everyone, im very new to disko and disk partitioning/management in general, but i had a few questions as i prep to use nixos-anywhere to setup/expand my homelab.

i have 5 Intel NUC computers, each with a SSD and a 1.8T HDD. The issue is that some of them report /dev/sda to be the SSD and /dev/sdb to be the HDD, while some do reverse. is this a problem when working with disko? aka would i be able to reuse the same disko config for each of the 5 computers? or do i necessarily need to tailor each one specifically to the output of its respective host's lsblk?

20:33:41
@caraiiwala:beeper.comcaraiiwala I tailor mine with /dev/disk/by-id/... You can still reuse the config though. Unfortunately disko still has issues merging modules so you'd have to import a common config file and override with recursiveUpdate, for example, to declare in full for each host 20:38:05
@caraiiwala:beeper.comcaraiiwala https://github.com/nix-community/disko/issues/678 is what I'm referring to 20:39:12
@zsuper:matrix.orgzsupercould you explain how you use disk/by-id/? i guess from the nixos-anywhere POV, what steps would i have to take?20:46:50
@zsuper:matrix.orgzsuperim not super familiar with device names and whatnot, and im moreso nervous here since one of the devs is a HDD while the other is an SSD, so i want to make sure the SSD is prioritized to have the boot partition or whatever20:47:59
@zsuper:matrix.orgzsuper

im especially confused here:

{
  disko.devices.disk.example = {
    type = "disk";
    device = "/dev/nvme0n1";
    content = {
      type = "gpt";
      partitions = {
        ESP = {
          size = "512MiB";
          type = "EF00";
          priority = 1;
          content = {
            type = "filesystem";
            format = "vfat";
            mountpoint = "/boot";
            mountOptions = [ "umask=0077" ];
          };
        };
        root = {
          size = "100%";
          priority = 2;
          content.format = "ext4";
        };
      };
    };
  };
}

how do i know what the Type of the partition is? and also the file system format (i.e. "vfat" vs "ext4")? are these things i just need to know about the hardware beforehand?

20:52:32
@caraiiwala:beeper.comcaraiiwalaWell those things are for you to decide. I would read up on what you actually want. But if you want the boot partition on your SSD, then you just need that EF00/vfat block on the SSD disk. The disk is determined by the device path (/dev/nvme0n1 as shown here, or /dev/disk/by-id/...)21:28:33
@zsuper:matrix.orgzsuperokay gotcha, but ultimately disko config is something that is "node-specific", right?21:40:23
@zsuper:matrix.orgzsuper

so when adding a new machine to my network, i should aim for a workflow that looks like:

  1. ssh into the target and run ls -l /dev/disk/by-id/
  2. using that information, write a disko configuration at ./modules/node-specific/machine-X/disko.nix
  3. Run nixos-anywhere using that disko.nix
  4. Add a node to my deploy-rs setup, which reuses that same disko.nix (and anything else in node-specific/machine-X/)
  5. Future rebuilds are done via deploy-rs
21:42:42
@zsuper:matrix.orgzsuperokay, and should i bother reading up on the different types? Or should I just internalize the fact that "EF00/vfat" correlates to the boot partition?21:45:14
@zsuper:matrix.orgzsuper * okay, and should i bother reading up on the different types? Or should I just internalize the fact that "EF00/vfat" correlates to the boot partition? and for the rest of my disk config just make it ext4 and a type = filesystem? 21:46:07
@caraiiwala:beeper.comcaraiiwalaNode-specific yes, just like the rest of NixOS21:46:18
@caraiiwala:beeper.comcaraiiwalaWorkflow is good21:46:33
@caraiiwala:beeper.comcaraiiwalaIt's sufficient to start simple this way but you should try to understand what you are doing. Nobody should have to tell you to educate yourself21:48:22
@zsuper:matrix.orgzsuperYeah, I'm pretty confident about how the deployment tools function, but i have literally never touched file systems and device/disks before, so all of this is very alien. Plus the lack of actual documentation for disko makes it very difficult to self teach. In any case, thank you for filling the gaps in my basic understanding!21:50:58

Show newer messages


Back to Room ListRoom Version: 10