| 27 Apr 2025 |
 musjj | Does it make sense to add additional fileSystems attribute for drives I don't want disko to manage/format like:
disko.devices.disk.main = { ... };
fileSystems = { ... };
Will this work correctly?
| 14:44:29 |
| musjj | To clarify the filesystems I want to add lives on a different block device from disko's main disk. | 14:53:15 |
 robsliwi | Why even bother adding them to disko at all? | 14:56:36 |
 mkg20001 | grub = {
efiSupport = true;
#efiInstallAsRemovable = true; # in case canTouchEfiVariables doesn't work for your system
device = "nodev";
};
from here: https://nixos.wiki/wiki/Bootloader
| 14:58:39 |
| mkg20001 | you need boot.loader.grub.device = "nodev"; when you have uefi+grub | 14:58:55 |
| musjj | I'm not adding them to disko, but directly to NixOS's fileSystems option | 15:02:36 |
| musjj | Like, I have two devices, one for my OS and the other is just for my old data storage. I want disko to format and manage only the OS device and let NixOS normally mount the data storage device. | 15:04:10 |
 parismagpie | Hi ! So i'm trying to use disko to generate both a vm image and a raw image. It works, but the thing is I want to put secrets on some ext4 partition mounted over /etc/secrets. For the raw image, no problem. | 16:19:51 |
| parismagpie | For the VM image, I use virtualisation.vmVariantWithDisko.sharedDirectories to avoid putting secrets into the nix store (it works nicely with a classical vm) | 16:20:29 |
| parismagpie | But with disko, i'm getting some error :
error: The option `virtualisation.vmVariantWithDisko.virtualisation.fileSystems."/etc/secrets".fsType' has conflicting definition values:
- In `/nix/store/hzaj4d6ari2wq2cbg1j60n9zw42gnshy-source/nixos/modules/virtualisation/qemu-vm.nix': "9p"
- In `/nix/store/7wf9q0mb1i43x9dr1qlyfaraq15n6sii-source/lib/interactive-vm.nix': "ext4"
Use `lib.mkForce value` or `lib.mkDefault value` to change the priority on any of these definitions.
I believe this is because the disko vm image actually respects my partitions formats, but that's a bit of a problem for my specific usecase. I can remove the /etc/secrets partition definition in disko, and it works, but do I have any other option ?
| 16:21:57 |
 tcurdt | I am a little lost trying to get disko working in this setup https://github.com/tcurdt/nixos-hetzner/blob/main/install-nixos.sh
error: attribute 'createScript' missing
at /nix/store/5dgq6q4jilxz6aipvhr24jsbzhvgy4zx-disko/share/disko/cli.nix:65:7:
64| else if (lib.traceValSeq hasDiskoModuleFlake) then
65| (builtins.getFlake flake).nixosConfigurations.${flakeAttr}.config.system.build.${diskoAttr}
| ^
66| else
| 17:52:49 |
| tcurdt | That's when I use v1.9.0 ... latest gives a different error | 17:53:12 |
| tcurdt | But I am also confused why there can be a version mismatch when I used "latest" instead. | 17:54:43 |
| tcurdt | Any pointers much appreciated. | 17:55:03 |
| tcurdt | echo 'Error: Attribute `nixosConfigurations.base.config.system.build.createScript` >&2
echo ' not found in flake
I don't see that attribute set in the example config
https://github.com/Lassulus/flakes-testing/blob/master/flake.nix
What am I missing?
| 18:13:45 |
|  food style edible product changed their display name from SS Bullshit Dreams to nowhere to SS Bullshit Dreams to Nowhere. | 18:30:46 |
 @realhotgirlshit:envs.net | Do you happen to know of the BIOS equivalent? My desktop is a little bit older | 22:26:20 |
| @realhotgirlshit:envs.net | Okay, now I get it to boot up but it doesn’t unlock the disk saying:
error: disk: 'cryptouuid/…' not fond.
I’m going to check the paths in my config. | 23:09:38 |
| tcurdt | finally got it working ...and created a github issue asking for a better error message and a PR to fix the current one | 23:40:20 |
| 28 Apr 2025 |
| @realhotgirlshit:envs.net | Yeah, I changed the config a little, same situation.
Do I need to load a kernel module or configure something? | 00:15:46 |
|  Magnus Jurdal joined the room. | 07:40:18 |
| tcurdt | I am stuck on this issue here https://github.com/nix-community/disko/issues/1026
Am I doing something wrong? | 11:20:21 |
| tcurdt | --mode destroy --yes-wipe-all-disks ignores --yes-wipe-all-disks and gets stuck waiting for input
and
--mode destroy,format,mount --yes-wipe-all-disks also gets stuck ... maybe a missing sync?
| 11:22:42 |
 lassulus | Huh stuck sounds like a bug | 12:08:07 |
| lassulus | It should run with -x already. So what is the output? | 12:08:22 |
| tcurdt | I have added the debug output to the ticket.
| 12:37:23 |
| tcurdt | Oh, you mean for --mode destroy,format,mount ? | 12:37:24 |
| tcurdt | lassulus: I have added the debug output for the "disko" mode
https://github.com/nix-community/disko/issues/1026
| 13:19:42 |
| tcurdt | Nothing happens anymore after lsblk -a -f | 13:20:21 |
| mkg20001 | then you need to specify the device grub should write the MBR to
look under lsblk
note that yoiu should not use a partition (so /dev/nvme0n1 - but not /dev/nvme0n1p1) | 17:13:35 |
