disko | 355 Members | |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 89 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Apr 2025 | ||
| 04:53:43 | ||
| 22 Apr 2025 | ||
| 02:28:45 | ||
| 02:41:04 | ||
| 02:51:48 | ||
| 09:32:35 | ||
| Hm... between two vms, that shouldn't be an issue if For diskoImagesScript i believe the idea would be that it runs zfs export in the end which also should cause it to import cleanly on another system iiuc. | 10:07:47 | |
| 23 Apr 2025 | ||
| Redacted or Malformed Event | 18:42:13 | |
| 24 Apr 2025 | ||
| The PR got merged 🎉 (thanks for your UUID contribution, btw), but I couldn't quite get subvolumes to mount at boot time. I saw that your PR included code for a custom systemd unit. I haven't tried using that and haven't much experience with writing systemd units, so maybe you could try implementing something with it to get boot-time subvolume mounts to work, if you're interested? | 23:32:42 | |
| 25 Apr 2025 | ||
| 16:10:02 | ||
| 18:00:35 | ||
| 26 Apr 2025 | ||
| @projectinitiative:matrix.org: Ignore my last message. Apparently the PR did allow subvolumes to be mounted at boot time and I just didn't implement the test properly to allow the test to unlock the subvolumes. This new PR fixes that though. So I think this means that we can probably now use bcachefs for impermanence, or we're at least one step closer to it 😀. | 00:17:04 | |
| * @projectinitiative:matrix.org: Ignore my last message. Apparently the PR did allow subvolumes to be mounted at boot time and I just didn't implement the test properly to allow it to unlock the subvolumes. [This new PR fixes that though](https://github.com/nix-community/disko/pull/1021). So I think this means that we can probably now use bcachefs for impermanence, or we're at least one step closer to it 😀. | 00:19:53 | |
| 01:46:44 | ||
| 02:22:05 | ||
| 14:42:27 | ||
| 22:53:07 | ||
| Hey everyone | 22:53:39 | |
| I’m trying to create a BTRFS subvolumes on LUKS, and I’m wondering if the disko configuration I have is enough, or if I have to adjust the NixOS configuration: | 22:56:55 | |
| 22:57:03 | |
| Should be fine | 23:42:28 | |
| yayyy :D | 23:42:33 | |
| not so hard | 23:42:37 | |
| 27 Apr 2025 | ||
| Copied from #Nix / NixOS : I’m trying to set up LUKS–style Btrfs full disk encryption on my older BIOS desktop with a layout generated from disko. I try to install it, but I get an error that says installation of GRUB on /dev/sda failed: No such file or directory.The command I used: sudo nix --extra-experimental-features nix-command --extra-experimental-features flakes run 'github:nix-community/disko/latest#disko-install' -- --flake '/etc/nixos#koolthing' --disk main /dev/sdaThe relevant NixOS configuration: The entire disko configuration in its flake: | 08:29:02 | |
| I’m pretty sure /dev/sda was listed in lsblk hmm I can check a little later | 08:30:41 | |
Which disk devices do you have? Usually they match /dev/sd* or /dev/nvme*. | 08:31:19 | |
| I have a 465.8 GB SSD showing up as /dev/sda, and it has a BIOS partition /dev/sda1, and a root partition that doesn’t take up the whole drive, just 300 GB | 08:55:18 | |
You do have device = "/dev/vdb"; in your configuration though. Not sure how that interacts with the CLI. | 08:56:50 | |
Why do I have to specify--disk NAME PATH when those are already in the configuration? | 08:57:49 | |
* Why do I have to specify--disk NAME DEVICE when those are already in the configuration? | 08:57:57 | |
* Why do I have to specify --disk NAME DEVICE when those are already in the configuration? | 08:58:03 | |