disko | 351 Members | |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 89 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Apr 2025 | ||
| but removing that code is also fine | 22:10:59 | |
| 18 Apr 2025 | ||
| @reflux1291:catgirl.cloud: nixos-install is idempotent. You can use it to repair stuff | 05:14:53 | |
| 13:29:48 | ||
| 19 Apr 2025 | ||
| 13:01:24 | ||
| 14:31:10 | ||
| Hey | 19:05:27 | |
| 20 Apr 2025 | ||
| so I'm using disko to declare partitioning for two raw disk images (/ in ext4, /home in zfs). Booting the system using qemu to test whether everything works or not, zfs complain about the zpool being mounted on another system ( "pool was previously in use from another system.", "The pool can be imported, use 'zpool import -f' to import the pool." ) | 07:35:01 | |
| I'm thinking that it's might be related to the use of diskoImagesScript to create the two raw images. Is there any disko option to avoid this problem ? | 07:35:55 | |
(I can boot.zfs.forceImportAll = true but that seems a bit overkill) | 07:47:57 | |
| 21 Apr 2025 | ||
| 04:53:02 | ||
| Redacted or Malformed Event | 04:53:41 | |
| 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 | |