| 19 Jan 2025 |
 Enzime | people make the empty snapshot for impermanence setups where you wipe your rootfs on every boot | 02:38:54 |
 lanice | Ah, right, I've seen that before. That makes sense, thank you! Not doing that for now. | 03:00:51 |
| lanice | For my HDD's, I have a zpool "data" configured like this:
data = {
type = "zpool";
mode = {
topology = {
type = "topology";
vdev = [ { members = ["hdd24tb_0" "hdd24tb_1" "hdd24tb_2"]; mode = "raidz1"; } ];
};
};
rootFsOptions = {
atime = "off";
xattr = "sa";
compression = "zstd";
};
options.ashift = "12";
datasets = {
"data" = { type = "zfs_fs"; mountpoint = "/data"; };
"media" = { type = "zfs_fs"; mountpoint = "/data/media"; };
"backup" = { type = "zfs_fs"; mountpoint = "/data/backup"; };
};
};
After finishing the install with nixos-anywhere, when I do zfs list, the output for that pool is:
data 1.41M 43.5T 139K /data
data/backup 128K 43.5T 128K /data/backup
data/data 139K 43.5T 139K /data
data/media 128K 43.5T 128K /data/media
What confuses me is the double-use of mountpoint /data. It seems both data and data/data is mounted on /data. Why did that happen? I probably did something wrong in my disko config, I'm doing a lot of trial and error and looking at other configs. | 03:21:46 |
| lanice | * For my HDD's, I have a zpool "data" configured like this:
disko.devices.zpool.data = {
type = "zpool";
mode = {
topology = {
type = "topology";
vdev = [ { members = ["hdd24tb_0" "hdd24tb_1" "hdd24tb_2"]; mode = "raidz1"; } ];
};
};
rootFsOptions = {
atime = "off";
xattr = "sa";
compression = "zstd";
};
options.ashift = "12";
datasets = {
"data" = { type = "zfs_fs"; mountpoint = "/data"; };
"media" = { type = "zfs_fs"; mountpoint = "/data/media"; };
"backup" = { type = "zfs_fs"; mountpoint = "/data/backup"; };
};
};
After finishing the install with nixos-anywhere, when I do zfs list, the output for that pool is:
data 1.41M 43.5T 139K /data
data/backup 128K 43.5T 128K /data/backup
data/data 139K 43.5T 139K /data
data/media 128K 43.5T 128K /data/media
What confuses me is the double-use of mountpoint /data. It seems both data and data/data is mounted on /data. Why did that happen? I probably did something wrong in my disko config, I'm doing a lot of trial and error and looking at other configs. | 03:22:36 |
| lanice | * For my HDD's, I have a zpool "data" configured like this:
disko.devices.zpool.data = {
type = "zpool";
mode = {
topology = {
type = "topology";
vdev = [ { members = ["hdd24tb_0" "hdd24tb_1" "hdd24tb_2"]; mode = "raidz1"; } ];
};
};
rootFsOptions = {
atime = "off";
xattr = "sa";
compression = "zstd";
};
options.ashift = "12";
datasets = {
"data" = { type = "zfs_fs"; mountpoint = "/data"; };
"media" = { type = "zfs_fs"; mountpoint = "/data/media"; };
"backup" = { type = "zfs_fs"; mountpoint = "/data/backup"; };
};
};
After finishing the install with nixos-anywhere, when I do zfs list, the output for that pool is:
data 1.41M 43.5T 139K /data
data/backup 128K 43.5T 128K /data/backup
data/data 139K 43.5T 139K /data
data/media 128K 43.5T 128K /data/media
What confuses me is the double-use of mountpoint /data. It seems both data and data/data is mounted on /data. Why did that happen? I probably did something wrong in my disko config, I'm doing a lot of trial and error and looking at other configs. | 03:24:58 |
| lanice | * For my HDD's, I have a zpool "data" configured like this:
disko.devices.zpool.data = {
type = "zpool";
mode = {
topology = {
type = "topology";
vdev = [ { members = ["hdd24tb_0" "hdd24tb_1" "hdd24tb_2"]; mode = "raidz1"; } ];
};
};
rootFsOptions = {
atime = "off";
xattr = "sa";
compression = "zstd";
};
options.ashift = "12";
datasets = {
"data" = { type = "zfs_fs"; mountpoint = "/data"; };
"media" = { type = "zfs_fs"; mountpoint = "/data/media"; };
"backup" = { type = "zfs_fs"; mountpoint = "/data/backup"; };
};
};
After finishing the install with nixos-anywhere, when I do zfs list, the output for that pool is:
data 1.41M 43.5T 139K /data
data/backup 128K 43.5T 128K /data/backup
data/data 139K 43.5T 139K /data
data/media 128K 43.5T 128K /data/media
What confuses me is the double-use of mountpoint /data. It seems both data and data/data is mounted on /data. Why did that happen? I probably did something wrong in my disko config, I'm doing a lot of trial and error and looking at other configs. | 03:25:06 |
| lanice | * For my HDD's, I have a zpool "data" configured like this:
disko.devices.zpool.data = {
type = "zpool";
mode = {
topology = {
type = "topology";
vdev = [ { members = ["hdd24tb_0" "hdd24tb_1" "hdd24tb_2"]; mode = "raidz1"; } ];
};
};
rootFsOptions = {
atime = "off";
xattr = "sa";
compression = "zstd";
};
options.ashift = "12";
datasets = {
"data" = { type = "zfs_fs"; mountpoint = "/data"; };
"media" = { type = "zfs_fs"; mountpoint = "/data/media"; };
"backup" = { type = "zfs_fs"; mountpoint = "/data/backup"; };
};
};
After finishing the install with nixos-anywhere, when I do zfs list, the output for that pool is:
data 1.41M 43.5T 139K /data
data/backup 128K 43.5T 128K /data/backup
data/data 139K 43.5T 139K /data
data/media 128K 43.5T 128K /data/media
What confuses me is the double-use of mountpoint /data. It seems both data and data/data is mounted on /data. Why did that happen? I probably did something wrong in my disko config, I'm doing a lot of trial and error and looking at other configs. | 03:25:19 |
| lanice | * For my HDD's, I have a zpool "data" configured like this:
disko.devices.zpool.data = {
type = "zpool";
mode = {
topology = {
type = "topology";
vdev = [ { members = ["hdd24tb_0" "hdd24tb_1" "hdd24tb_2"]; mode = "raidz1"; } ];
};
};
rootFsOptions = {
atime = "off";
xattr = "sa";
compression = "zstd";
};
options.ashift = "12";
datasets = {
"data" = { type = "zfs_fs"; mountpoint = "/data"; };
"media" = { type = "zfs_fs"; mountpoint = "/data/media"; };
"backup" = { type = "zfs_fs"; mountpoint = "/data/backup"; };
};
};
After finishing the install with nixos-anywhere, when I do zfs list, the output for that pool is:
data 1.41M 43.5T 139K /data
data/backup 128K 43.5T 128K /data/backup
data/data 139K 43.5T 139K /data
data/media 128K 43.5T 128K /data/media
What confuses me is the double-use of mountpoint /data. It seems both data and data/data is mounted on /data. Why did that happen? I probably did something wrong in my disko config, I'm doing a lot of trial and error and looking at other configs. | 03:25:26 |
| lanice | Could it be that I should not declare the first of those datasets at all, "data" with mountpoint "/data"? | 03:34:28 |
| Enzime | it looks like the dataset shouldn't be mounted from what you posted, maybe it's something to do with ZFS topologies, I'm not very familiar with them (possibly a bug?) | 04:12:42 |
| Enzime | the simplest fix would be to add canmount = "off" and mountpoint = "none"; to rootFsOptions | 04:13:47 |
| lanice | Thank you, will try that! Is it possible to make those changes without reinstalling just with disko, or do I need to wipe and repartition everything? | 04:22:06 |
| Enzime | the simplest solution would be running zfs set -u canmount=off mountpoint=none data and then rebooting | 04:29:20 |
| lanice | Right, makes sense, thank you! | 04:33:40 |
 Raj | Running into this error when trying to use disko to create a bootable USB (sudo nix run 'github:nix-community/disko/latest#disko-install' -- --flake '.#image' --disk nixos-usb-stick /dev/sdc):
Creating initial /etc/machine-id
efiSysMountPoint = '/boot' is not a mounted partition. Is the path configured correctly?
Traceback (most recent call last):
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 431, in <module>
main()
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 411, in main
run([CHECK_MOUNTPOINTS])
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 58, in run
return subprocess.run(cmd, check=True, text=True, stdout=stdout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8/lib/python3.12/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/nix/store/686vaqa40l0vxcp1ll54cbvlrmn9kn55-check-mountpoints']' returned non-zero exit status 1.
Failed to install bootloader
disko-install failed
rmdir: failed to remove '/mnt/disko-install-root': Directory not empty
The disko config is:
{
disko.devices = {
nodev."/" = {
fsType = "tmpfs";
mountOptions = [
"size=2G"
"defaults"
"mode=755"
];
};
nodev."/home/raj" = {
fsType = "tmpfs";
mountOptions = [
"size=2G"
"defaults"
"mode=777"
];
};
disk = {
nixos-usb-stick = {
type = "disk";
content = {
type = "gpt";
partitions = {
ESP = {
type = "EF00";
priority = 0;
end = "1G";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = ["defaults" "umask=0077"];
};
};
root = {
priority = 1;
end = "-0";
content = {
type = "luks";
name = "root";
initrdUnlock = true;
extraFormatArgs = ["--pbkdf argon2id"];
content = {
type = "btrfs";
extraArgs = ["-f"];
subvolumes = {
"/nix" = {
mountpoint = "/nix";
mountOptions = ["compress=zstd" "noatime"];
};
"/persist" = {
mountpoint = "/persist";
mountOptions = ["compress=zstd" "noatime"];
};
"/data" = {
mountpoint = "/data";
mountOptions = ["compress=zstd" "noatime"];
};
};
};
};
};
};
};
};
};
};
}
| 23:13:36 |
| Raj | * Could someone please help me troubleshoot this?
I'm running into this error when trying to use disko to create a bootable USB (sudo nix run 'github:nix-community/disko/latest#disko-install' -- --flake '.#image' --disk nixos-usb-stick /dev/sdc):
Creating initial /etc/machine-id
efiSysMountPoint = '/boot' is not a mounted partition. Is the path configured correctly?
Traceback (most recent call last):
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 431, in <module>
main()
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 411, in main
run([CHECK_MOUNTPOINTS])
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 58, in run
return subprocess.run(cmd, check=True, text=True, stdout=stdout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8/lib/python3.12/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/nix/store/686vaqa40l0vxcp1ll54cbvlrmn9kn55-check-mountpoints']' returned non-zero exit status 1.
Failed to install bootloader
disko-install failed
rmdir: failed to remove '/mnt/disko-install-root': Directory not empty
The disko config is:
{
disko.devices = {
nodev."/" = {
fsType = "tmpfs";
mountOptions = [
"size=2G"
"defaults"
"mode=755"
];
};
nodev."/home/raj" = {
fsType = "tmpfs";
mountOptions = [
"size=2G"
"defaults"
"mode=777"
];
};
disk = {
nixos-usb-stick = {
type = "disk";
content = {
type = "gpt";
partitions = {
ESP = {
type = "EF00";
priority = 0;
end = "1G";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = ["defaults" "umask=0077"];
};
};
root = {
priority = 1;
end = "-0";
content = {
type = "luks";
name = "root";
initrdUnlock = true;
extraFormatArgs = ["--pbkdf argon2id"];
content = {
type = "btrfs";
extraArgs = ["-f"];
subvolumes = {
"/nix" = {
mountpoint = "/nix";
mountOptions = ["compress=zstd" "noatime"];
};
"/persist" = {
mountpoint = "/persist";
mountOptions = ["compress=zstd" "noatime"];
};
"/data" = {
mountpoint = "/data";
mountOptions = ["compress=zstd" "noatime"];
};
};
};
};
};
};
};
};
};
};
}
| 23:14:08 |
| Raj | * Could someone please help me troubleshoot this? Should one of the commands in the install script be run with sudo or something?
I'm running into this error when trying to use disko to create a bootable USB (sudo nix run 'github:nix-community/disko/latest#disko-install' -- --flake '.#image' --disk nixos-usb-stick /dev/sdc):
Creating initial /etc/machine-id
efiSysMountPoint = '/boot' is not a mounted partition. Is the path configured correctly?
Traceback (most recent call last):
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 431, in <module>
main()
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 411, in main
run([CHECK_MOUNTPOINTS])
File "/nix/store/diy6lcklb9r4k18l6plg6yj9chn3pg19-systemd-boot/bin/systemd-boot", line 58, in run
return subprocess.run(cmd, check=True, text=True, stdout=stdout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8/lib/python3.12/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/nix/store/686vaqa40l0vxcp1ll54cbvlrmn9kn55-check-mountpoints']' returned non-zero exit status 1.
Failed to install bootloader
disko-install failed
rmdir: failed to remove '/mnt/disko-install-root': Directory not empty
The disko config is:
{
disko.devices = {
nodev."/" = {
fsType = "tmpfs";
mountOptions = [
"size=2G"
"defaults"
"mode=755"
];
};
nodev."/home/raj" = {
fsType = "tmpfs";
mountOptions = [
"size=2G"
"defaults"
"mode=777"
];
};
disk = {
nixos-usb-stick = {
type = "disk";
content = {
type = "gpt";
partitions = {
ESP = {
type = "EF00";
priority = 0;
end = "1G";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = ["defaults" "umask=0077"];
};
};
root = {
priority = 1;
end = "-0";
content = {
type = "luks";
name = "root";
initrdUnlock = true;
extraFormatArgs = ["--pbkdf argon2id"];
content = {
type = "btrfs";
extraArgs = ["-f"];
subvolumes = {
"/nix" = {
mountpoint = "/nix";
mountOptions = ["compress=zstd" "noatime"];
};
"/persist" = {
mountpoint = "/persist";
mountOptions = ["compress=zstd" "noatime"];
};
"/data" = {
mountpoint = "/data";
mountOptions = ["compress=zstd" "noatime"];
};
};
};
};
};
};
};
};
};
};
}
| 23:14:51 |
| 20 Jan 2025 |
|  sboe joined the room. | 09:16:48 |
|  srestegosaurio (on tchncs.de) joined the room. | 15:34:52 |
| srestegosaurio (on tchncs.de) | Redacted or Malformed Event | 15:36:03 |
| srestegosaurio (on tchncs.de) | Redacted or Malformed Event | 15:36:19 |
| srestegosaurio (on tchncs.de) | I really want to avoid blowing up my computer.
| 15:36:33 |
| srestegosaurio (on tchncs.de) | Hello, I have a quick doubt: I want to add a BTRFS subvol to my system. I modified the disko coinfig in my flake, how should I apply those changes?
| 15:36:53 |
| srestegosaurio (on tchncs.de) | Redacted or Malformed Event | 15:38:05 |
| srestegosaurio (on tchncs.de) | Redacted or Malformed Event | 15:38:32 |
 nim65s | Redacted or Malformed Event | 18:12:02 |
| nim65s changed their display name from Guilhem to nim65s. | 18:12:17 |
|  Anton (he/him) joined the room. | 20:51:35 |
|  guiniol joined the room. | 21:03:45 |
| guiniol | So. I wanted to create a couple of extra datasets in an existing ZFS pool without wiping everything. Is there a way to either get disko to not remove existing data (is this what the mount mode does? I couldn't find much about it in the docs) or to get disko to give me the commands it would run to create those datasets (which I would the run myself). | 21:05:48 |
