| 31 Jul 2025 |
|  Max joined the room. | 17:11:35 |
| 2 Aug 2025 |
|  sinan changed their profile picture. | 06:58:26 |
| sinan | 06:58:39 |
| sinan | 06:58:46 |
| 3 Aug 2025 |
|  prescientmoon changed their display name from Adriel to prescientmoon. | 14:31:40 |
| sinan changed their profile picture. | 15:07:47 |
|  zsuper joined the room. | 20:28:38 |
| zsuper | 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 | * 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 | * 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 | 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 | https://github.com/nix-community/disko/issues/678 is what I'm referring to | 20:39:12 |
| zsuper | could 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 | im 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 whatever | 20:47:59 |
| zsuper | 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 | Well 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 |
