| 20 Nov 2024 |
daddychan | * Of note, I enabled boot.initrd.systemd in my config since it seemed like that was necessary to use keyFileTimeout, so that could also have something to do with this. I did not enable it before when I was able to boot successfully. | 05:16:30 |
| 22 Nov 2024 |
| Morgan (@numinit) joined the room. | 17:49:27 |
| 24 Nov 2024 |
| danjujan joined the room. | 10:34:18 |
| 25 Nov 2024 |
| NullCube joined the room. | 10:04:53 |
| luxus joined the room. | 18:06:38 |
| else42 joined the room. | 21:54:50 |
else42 | hey! trying to set up a new system via nixos net image using disko-install. hitting this error:
/nix/store/bz18paxklav6yyhqvvl1l7aiq3drncy4-disko-install/bin/.disko-install-wrapped: line 216: artifacts[1]: unbound variable
anybody got an idea what that could be related to? this is my config: https://gist.github.com/elsbrock/7707bb8edfe527fbf250aa2c99ca5815 | 21:56:26 |
else42 | [nixos@nixos:~/infra]$ sed -n '214, 220 p' /nix/store/bz18paxklav6yyhqvvl1l7aiq3drncy4-disko-install/bin/.disko-install-wrapped
IFS=$'\n' mapfile -t artifacts <<<"$outputs"
nixos_system=${artifacts[0]}
closure_info=${artifacts[1]}
disko_script=${artifacts[2]}
if [[ -n ${dry_run-} ]]; then
echo "Would run: $disko_script"
| 21:58:20 |
| 26 Nov 2024 |
maralorn | I am trying to configure a system based on the zfs examples. | 10:21:15 |
maralorn | I have a zpool which configures mountpoint "/" | 10:21:27 |
maralorn | On eval I get the error The fileSystems option does not specifiy your root file system. | 10:22:03 |
maralorn | Oooof, classic flakes problem … | 10:22:51 |
maralorn | Hadn’t staged disko-config.nix | 10:23:00 |
| victorbjelkholm joined the room. | 16:02:33 |
| 27 Nov 2024 |
| jopejoe1 [4094] changed their display name from jopejoe1 to jopejoe1 [4094]. | 18:19:01 |
netpleb | I have a disks.nix in my git repo, added it to my configuration, and disko-install ... worked perfectly! My my disks config looks like (basically it is the luks-btrfs example in the docs):
{
disko.devices = {
disk = {
main = {
type = "disk";
# When using disko-install, we can overwrite this value (device) from the commandline:
# $ sudo nix run 'github:nix-community/disko/latest#disko-install' -- --write-efi-boot-entries --flake '/tmp/config/etc/nixos#mymachine' --disk main /dev/sda
# see: https://github.com/nix-community/disko/blob/master/docs/disko-install.md
device = "/dev/nvme0n1";
content = {
type = "gpt";
partitions = {
ESP = {
size = "512M";
type = "EF00";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = [ "umask=0077" ];
};
};
luks = {
size = "100%";
content = {
type = "luks";
name = "crypted";
# disable settings.keyFile if you want to use interactive password entry
#passwordFile = "/tmp/secret.key"; # Interactive
settings = {
allowDiscards = true;
# keyFile = "/tmp/secret.key";
};
# additionalKeyFiles = [ "/tmp/additionalSecret.key" ];
content = {
type = "btrfs";
extraArgs = [ "-f" ];
subvolumes = {
"/root" = {
mountpoint = "/";
mountOptions = [ "compress=zstd" "noatime" ];
};
"/home" = {
mountpoint = "/home";
mountOptions = [ "compress=zstd" "noatime" ];
};
"/nix" = {
mountpoint = "/nix";
mountOptions = [ "compress=zstd" "noatime" ];
};
"/swap" = {
mountpoint = "/.swapvol";
swap.swapfile.size = "8G";
};
};
};
};
};
};
};
};
};
};
}
| 18:35:59 |
netpleb | Then I added a second nvme device to the machine and booted it up. I noticed that the machine switched the original /dev/nvme0n1 over to /dev/nvme1n1 and the new device is now /dev/nvme0n1, but it booted up just fine. I am guessing that is becuase (correctly) disko set fileSystems."/".device = "crypted". So far so good. | 18:40:29 |
netpleb | but here is my question: can I somehow simply update my disks.nix file and use disko to add the 2nd device to the btrfs filesystem? or do I need to run the respective btrfs device add ... and btrfs balance start -mconvert=raid1 commands myself? | 18:45:58 |