disko | 385 Members | |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 100 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Mar 2026 | ||
| I mainly want to do it for the sake of easier reproducibility, and also not needing the graphical installer anymore (since I'm terrible at disk formatting with the CLI). Also, I have been considering reinstalling on btrfs. Can disko manage btrfs subvolumes, and how would I go about doing so? | 13:56:50 | |
| 20:38:22 | ||
| 3 Mar 2026 | ||
| 00:18:50 | ||
| with respect to zfs, disko will create zfs datasets and volumes after installation | 06:23:43 | |
| my workflow with new apps/servers is to update the disko config with a new app specific dataset and then rerun disko with format mode | 06:24:38 | |
| it doesn't reformat non zfs partitions (it seems to fail running the tools to partition) but it will create if not exists new zfs datasets/volumes and since it's linked to nixos via the disko nixos module also update the mounting to match | 06:26:46 | |
| indium114 though i've never used btrfs or disko with btrfs, https://github.com/nix-community/disko/blob/5af7af10f14706e4095bd6bc0d9373eb097283c6/lib/types/btrfs.nix#L175 implies that subvolumes are created if it doesn't exist which suggests you could rerun disko and create new subvolumes as you expand your disko config (have not tested this) | 06:36:51 | |
| https://github.com/numtide/disko-zfs is safer :) | 10:54:08 | |
| til thanks | 11:02:08 | |
| If you run into anything ping me, im the guy who wrote it | 11:03:52 | |
| (if you happen to run into a physical wall, call the ambulance, not me please) | 11:04:20 | |
| 25 Apr 2024 | ||
| 23:38:25 | ||
| 23:51:57 | ||
| 26 Apr 2024 | ||
| Couple of questions about NixOS live USBs: I want to partition my 64 GB USB flash drive into two partitions (FAT32 live USB + ext4 storage), so I used the following disko config:
I then copied over the files from the (minimal, non-graphical) NixOS live ISO into partition 1, hoping that the instructions on the Arch wiki would generalize to NixOS, but then my live ISO gets stuck with the following error message:
How can I use my USB flash drive as both a live USB and as a storage device? I found this relevant Discourse link but there was no resolution to the problem there. I realize this might not be the best place to ask this, but I figured that folks here would have expertise configuring boot partitions correctly. | 02:02:16 | |
| * Couple of questions about NixOS live USBs: I want to partition my 64 GB USB flash drive into two partitions (FAT32 live USB + ext4 storage), so I used the following disko config:
I then copied over the files from the (minimal, non-graphical) NixOS live ISO into partition 1, hoping that the instructions on the Arch wiki would generalize to NixOS, but then my live ISO gets stuck with the following error message:
How can I use my USB flash drive as both a live USB and as a storage device? I found this relevant Discourse link but there was no resolution to the problem there. I realize this might not be the best place to ask this, but I figured that folks here would have expertise configuring boot partitions correctly. For reference, the NixOS manual says I should | 02:12:28 | |
| I don't think that this will work since you need to unmount the live USB to format it as storage device | 07:16:00 | |
In reply to @tim92:matrix.orgNot sure what you mean, exactly. To clarify, I'm not trying to format the USB while it's live; I'm running this from an existing NixOS install. If the"live USB" bit uses only ~1 GiB, there should be some way to make use of the remaining space, hopefully. | 07:57:47 | |
| 07:57:54 | ||
| 08:25:00 | ||
| Soooo,
Does anybody have any idea how I can fix this? Here's my disko.nix:
| 15:33:36 | |
| I couldn't find anything remotely connected with this bug | 15:34:34 | |
| If you need anything else from me, please ask | 18:58:57 | |
| in line 43 you have root_vg but your vg is called root | 21:38:05 | |
| so you would need to change the name also to root instead of root_vg | 21:38:19 | |
| ah wait no | 21:38:30 | |
| I misread | 21:38:32 | |
| lvm_vg is under disk instead of of being under lvm_vg in the toplevel | 21:39:15 | |
| so the stuff from line 50 onwards needs to go one lever higher | 21:39:38 | |
| sorry for it being so complicated | 21:40:02 | |
| 23:32:11 | ||