disko | 364 Members | |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 93 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Jul 2025 | ||
| but when i tried to mount /boot it errored out and i got the following in dmesg
| 13:23:18 | |
| i don't think it's related since the original error was about the root volume | 13:23:38 | |
| as 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 tho | 13:27:26 | |
| nope, no luck | 13:51:59 | |
| 30 Jul 2025 | ||
| got 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=r | 03:44:59 | |
| 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 | ||
| 17:11:35 | ||
| 2 Aug 2025 | ||
| 06:58:26 | ||
| 06:58:39 | ||
| 06:58:46 | ||
| 3 Aug 2025 | ||
| 14:31:40 | ||
| 15:07:47 | ||
| 20:28:38 | ||
| 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 | 20:33:01 | |
| * 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 | 20:33:24 | |
| * 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 | 20:33:41 | |
| 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 | |
| https://github.com/nix-community/disko/issues/678 is what I'm referring to | 20:39:12 | |
| 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 | |
| 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 | |
| im especially confused here:
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 | |
| 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 | |
| okay gotcha, but ultimately disko config is something that is "node-specific", right? | 21:40:23 | |
| so when adding a new machine to my network, i should aim for a workflow that looks like:
| 21:42:42 | |
| 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? | 21:45:14 | |
* 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 | |
| Node-specific yes, just like the rest of NixOS | 21:46:18 | |
| Workflow is good | 21:46:33 | |
| It'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 yourself | 21:48:22 | |
| Yeah, 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 | |