disko | 349 Members | |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 87 Servers |
| Sender | Message | Time |
|---|---|---|
| 7 Jun 2025 | ||
| I only saw, that it was not able to mount the datasets. When I changed the keylocation to a file, it said that it was an invalid option. Could be that I overlooked it on the first run though. | 07:39:52 | |
| Is Disko able to add to my existing zfs datasets? | 18:16:57 | |
| So if I create a new dataset in the config, will it generate it upon nixos-rebuild? | 18:17:19 | |
| I don't think so | 18:25:38 | |
| at least I have been always manually reconciling that | 18:25:43 | |
| theoretically you can run the format part of the script again | 19:22:28 | |
| but better check what it would run beforehand :) | 19:22:37 | |
| So if I add Disko as a module to my configuration, and add another dataset there, it does not get automatically created? What is the expected way to do it then? Create the dataset by hand and then add it to fileSystems? | 19:24:52 | |
no, add it to the disko config and either create it manually or run what is in config.system.build.format | 19:27:22 | |
| That sounds much better 😉 | 19:30:47 | |
| 22:11:25 | ||
| 23:16:28 | ||
| 8 Jun 2025 | ||
No, I’m using the command I saw in the README:sudo nix --experimental-features "nix-command flakes" run github:nix-community/disko/latest -- --mode destroy,format,mount ./etc/nixos/disk-config.nix, which I run inside /mnt with my configurations | 00:26:16 | |
| I’ll work on that pastebin for you. | 01:37:59 | |
| Hello again. Right now all I can see is (in | 08:55:41 | |
| If you don't set a static mountpoint in your disko config, I don't think it's possible for the general case during eval time. I think if you leave it empty the default should just be "/${dataset.name}"? During run time you could just do "zfs get mountpoint dataset" | 12:31:07 | |
So from what I found during research is that I should use options.mountpoint = "legacy"; and then declare my fileSystems with the filesystems that should be mounted automatically, and for others I must find a better way. Like hard coding stuff maybe | 13:07:10 | |
| So... Can I just write my own systemd mount unit for datasets I do not want to mount automatically? And if yes, how can I tell systemd that the dataset encryption password has to be retrieved from the user? I suppose there's ways... Because with a unit, I can make other units depend on it (like for starting navidrome only if the dataset with the music is mounted) | 13:13:34 | |
| 9 Jun 2025 | ||
| 03:28:26 | ||
| 20:13:58 | ||
| Is there a way to configure a swap file using Disko? | 20:14:09 | |
| specifically, a swap file on an ext4 in LUKS partition | 20:14:21 | |
| 20:43:55 | ||
| 20:46:24 | ||
| 10 Jun 2025 | ||
| 00:26:37 | ||
| I'm new to ZFS and trying to convert my RAID setup to Disko. The deployment with nixos-anywhere was successful, but once rebooted, the system failed to boot. Here is my disko configuration: | 00:45:00 | |
you need to either use dataset option mountpoint=legacy and configure mountpoints with usual fstab (which i recommend for root fs, "legacy" is a misnomer) or tell zfs to run an import in initrd | 01:20:28 | |
| https://search.nixos.org/options?channel=25.05&show=boot.zfs.extraPools&from=0&size=50&sort=relevance&type=packages&query=boot+zfs | 01:21:45 | |
| Thanks for responding. I actually tried booting it with an even simpler non-ZFS config and I'm having the same issue: | 01:28:56 | |
| So now I'm very confused | 01:29:13 | |