| 3 Feb 2025 |
| Gregor Burger joined the room. | 12:30:34 |
| pbsds changed their display name from pbsds (FOSDEM) to pbsds. | 16:25:01 |
| Elliott joined the room. | 21:02:47 |
Elliott | is parted --align=optimal supported? | 21:03:16 |
| 4 Feb 2025 |
lassulus | Parted in Disko is only used in the deprecated table type. So not reaoluly supported | 01:52:14 |
| lukts30 joined the room. | 12:58:29 |
Elliott | I see. I was looking at the table.nix documentation but I'm actually using a gpt table. | 19:36:14 |
Elliott | * I see. I was looking at the table.nix documentation but I'm actually using a gpt type. | 19:36:21 |
Elliott | So, I'm trying to migrate my setup to disko and in my documentation I have used parted --align=optimal how would I do the equivalent in disko using sgdisk. | 19:37:41 |
Elliott | * So, I'm trying to migrate my setup to disko and in my documentation I have used parted --align=optimal how would I do the equivalent in disko using sgdisk? | 19:55:18 |
| 5 Feb 2025 |
| Singest joined the room. | 15:43:15 |
| 6 Feb 2025 |
Elliott | After some research I think sgdisk tried to align optimally by default. | 16:21:19 |
waltmck | As of today I am no longer able to nixos-rebuild switch nor nixos-rebuild boot; both fail with the following error:
> Adding configuration to bootloader
Traceback (most recent call last):
File "/nix/store/kpz0g2v49frpn640snk0ahai4sjng8yh-systemd-boot/bin/systemd-boot", line 431, in <module>
main()
File "/nix/store/kpz0g2v49frpn640snk0ahai4sjng8yh-systemd-boot/bin/systemd-boot", line 414, in main
install_bootloader(args)
File "/nix/store/kpz0g2v49frpn640snk0ahai4sjng8yh-systemd-boot/bin/systemd-boot", line 338, in install_bootloader
raise Exception("could not find any previously installed systemd-boot")
Exception: could not find any previously installed systemd-boot
Failed to install bootloader
Any idea what could be causing this? My last change was something completely unrelated to booting (neovim configuration), so this issue appeared out of nowhere just today. My config is here
| 22:03:49 |
waltmck | oh wait, I think I might know what the problem is. I set SYSTEMD_COLORS=1 which I think breaks the parsing of bootctl's output | 22:05:42 |
waltmck | yep that was it | 22:10:23 |
waltmck | ok easy problem resolution lol | 22:10:30 |
| 7 Feb 2025 |
| ian joined the room. | 14:53:24 |
@brian:bmcgee.ie | in nixos vm tests is there a way to force the disk uuid to be the same/consistent? | 15:12:15 |
| 8 Feb 2025 |
| terrorjack joined the room. | 01:22:28 |
lassulus | you can set the uuids now in the config, maybe that is sufficient? | 01:49:21 |
| terrorjack set a profile picture. | 02:24:27 |
| terrorjack removed their profile picture. | 02:25:02 |
| Zamyatin joined the room. | 23:52:02 |
| 9 Feb 2025 |
| projectinitiative joined the room. | 04:00:12 |
projectinitiative | Hi, I am trying to add a new feature for multi-drive bcachefs support. I am attempting to model it after zfs and mdadm/mdraid. When I attempt to build the check nix build .\#checks.x86_64-linux.bcachefs-multi-disk.driverInteractive
I run into the following error:
> In /nix/store/v86q00ycq0a1vlwa6fhx3hims0mxj0a7-disko-mount line 140:
> readarray -t pool_devices < <(cat "$disko_devices_dir"/bcachefs_pool1)
> ^----------------^ SC2154 (warning): disko_devices_dir is referenced but not assigned
I know this gets preset before hand (and injected?) in lib/default.nix's _create method. I believe I have added the necessary type to that file as well. Curious if someone had more insight on how this arch works/what vars are provided to types.
Here is my lib/default: https://github.com/ProjectInitiative/disko/blob/feat/bcachefs-as-member/lib/default.nix#L37
| 04:08:31 |
projectinitiative | I think I can answer my own question: topLevel only includes this var for _create methods. I have it in a _mount. I will need to rework some of the logic | 05:09:32 |
| @tired:fairydust.space left the room. | 22:51:59 |
| 10 Feb 2025 |
| snipped-paws joined the room. | 05:51:00 |
snipped-paws | Redacted or Malformed Event | 05:56:41 |
snipped-paws | Hello, I am new-ish to NixOS and disko and am trying to get a setup working for my home server. I have this cut-down config that is just supposed to format the single mirror that I plan to install NixOS on top of, but it seems to not correctly create the zfs partition (as well as the zpool and datasets). When I run sudo disko --mode disko disko-config.nix, it appears to work (?), but when I check the partitions in Gnome Disks in the live environment, the content of the partition is listed as "Unknown." The EFI boot partition does appear to be recognized as expected. Any help would be much appreciated!
{
disko.devices = let
nixosPartitions = {
ESP = {
size = "512M";
type = "EF00";
content.type = "filesystem";
content.format = "vfat";
content.mountpoint = "/boot";
};
zfs = {
size = "100%";
content.type = "zfs";
content.pool = "nixos";
};
};
in {
disk = {
# NixOS boot mirror (240GBx2)
ssd0 = {
device = "/dev/sda";
type = "disk";
content = {
type = "gpt";
partitions = nixosPartitions;
};
};
ssd1 = {
device = "/dev/sdb";
type = "disk";
content = {
type = "gpt";
partitions = nixosPartitions;
};
};
};
};
zpool = {
# NixOS boot mirror
nixos = {
type = "zpool";
mode = "mirror";
options = { ashift = "12"; };
datasets = {
"root" = {
type = "zfs_fs";
mountpoint = "/";
options = {
encryption = "aes-256-gcm";
keyformat = "passphrase";
keylocation = "prompt";
};
};
"nix" = {
type = "zfs_fs";
mountpoint = "/nix";
options."com.sun:auto-snapshot" = "false";
};
"home" = {
type = "zfs_fs";
mountpoint = "/home";
options = {
encryption = "aes-256-gcm";
keyformat = "raw";
keylocation = "file:///etc/zfskey";
};
};
};
};
};
}
| 06:10:38 |