disko

Sender	Message	Time
8 Jun 2024
lassulus	so maybe you don't need mountpoint?	15:17:12
wieldable9080	In reply to @lassulus:lassul.us maybe you want to set swap.swapfile.path instead of mountpoint? this is the easy way of doing this :D	15:18:37
wieldable9080	In reply to @lassulus:lassul.us so maybe you don't need mountpoint? btrfs subvolume swap has its pros, also it just looks nice	15:19:05
lassulus	hmm, ok, reading the code again, it should also work with a mountpoint set	15:20:24
wieldable9080	doing btrfs swapfile outside of a separate volume is probably a bad idea (has something to do with compression i think)	15:20:26
wieldable9080	In reply to @lassulus:lassul.us hmm, ok, reading the code again, it should also work with a mountpoint set i think i took this code from the main repo :D	15:20:55
wieldable9080	i mean, except the subvolume naming	15:21:12
lassulus	whats the error you see on boot?	15:24:17
wieldable9080	In reply to @lassulus:lassul.us whats the error you see on boot? timeout waiting for the device which somewhere shows as this swap swap	15:25:34
wieldable9080	In reply to @lassulus:lassul.us whats the error you see on boot? *	15:25:41
9 Jun 2024
	magic_rb joined the room.	14:19:18
11 Jun 2024
Vilsol	What is the intended way of using disko when doing a clean install with an existing config? Or do I need to do a non-graphical (manual) install?	10:12:25
SigmaSquadron	In reply to @thevilsol:matrix.org What is the intended way of using disko when doing a clean install with an existing config? Or do I need to do a non-graphical (manual) install? Get your hardware configuration, and delete the fileSystems options. Import your disko configuration in your configuration.nix, and use disko-install to format and install the system.	11:45:09
netpleb	if I want disko to make a partition but not cause the partition to be formatted or mounted, how do I do that?	16:33:19
wieldable9080	In reply to @netpleb:matrix.org if I want disko to make a partition but not cause the partition to be formatted or mounted, how do I do that? Ammm, I saw this message and came to find out, like, what do you mean by "make"??	16:34:13
netpleb	In reply to @wieldable9080:matrix.im Ammm, I saw this message and came to find out, like, what do you mean by "make"?? I have a disk-config.nix that does my partitioning for whenever provision a new instance of this type of machine (so I am just using `nixos-anywhere ...`). Can I just leave out the `mountPoint` and `mountOptions` in that disk-config?	16:38:09
netpleb	In reply to @wieldable9080:matrix.im Ammm, I saw this message and came to find out, like, what do you mean by "make"?? * I have a disk-config.nix that does my partitioning for whenever provision a new instance of this type of machine (so I am just using `nixos-anywhere ...`). Can I just leave out the `mountPoint` and `mountOptions` in that disk-config for that partition?	16:38:20
netpleb	here is the disk-config.nix: { disko.devices = { disk = { sda = { type = "disk"; device = "/dev/sda"; content = { type = "gpt"; partitions = { boot = { name = "boot"; size = "1M"; type = "EF02"; }; esp = { name = "ESP"; size = "500M"; type = "EF00"; content = { type = "filesystem"; format = "vfat"; mountpoint = "/boot"; }; }; root = { size = "40G"; content = { type = "btrfs"; extraArgs = [ "-f" ]; # Override existing partition mountpoint = "/"; mountOptions = [ "compress=zstd" "noatime" ]; }; }; data = { size = "100%"; content = { # type = "btrfs"; extraArgs = [ "-f" ]; # Override existing partition # mountpoint = "/data"; # mountOptions = [ "compress=zstd" "noatime" ]; }; }; }; }; }; }; }; } I want that partition currently called "data" to not be mounted and I also do not really even care if it is formatted. I just want the partition to exist. Does that make sense?	16:41:42
netpleb	* here is the disk-config.nix: { disko.devices = { disk = { sda = { type = "disk"; device = "/dev/sda"; content = { type = "gpt"; partitions = { boot = { name = "boot"; size = "1M"; type = "EF02"; }; esp = { name = "ESP"; size = "500M"; type = "EF00"; content = { type = "filesystem"; format = "vfat"; mountpoint = "/boot"; }; }; root = { size = "40G"; content = { type = "btrfs"; extraArgs = [ "-f" ]; # Override existing partition mountpoint = "/"; mountOptions = [ "compress=zstd" "noatime" ]; }; }; data = { size = "100%"; content = { type = "btrfs"; extraArgs = [ "-f" ]; # Override existing partition # mountpoint = "/data"; # mountOptions = [ "compress=zstd" "noatime" ]; }; }; }; }; }; }; }; } I want that partition currently called "data" to not be mounted and I also do not really even care if it is formatted. I just want the partition to exist. Does that make sense?	16:43:56
netpleb	actually, I figured it out. Looks like just leaving out the `mountPoint` and `mountOptions` attributes did the trick!	16:46:49
netpleb	* actually, I figured it out. Looks like just leaving out the `mountPoint` and `mountOptions` attributes did the trick! (I did still have to specify the `type = btrfs` attribute, which is fine. Is there some sort of `type = raw` where it just does no formatting?	16:47:40
lassulus	You can leave content empty in the partition	16:54:39
	networkException (moving to @networkexception:nwex.de) changed their display name from networkException to networkException (moving to @networkexception:nwex.de).	18:33:42
12 Jun 2024
	networkException joined the room.	15:31:09
matthewcroughan	How come the homeless-shelter is found on images built with disko?	17:38:24
matthewcroughan	I have `/homeless-shelter`	17:38:30
matthewcroughan	maybe because of leaky builds?	17:38:36
maralorn	My luks prompt on boot says "password for disk disk-system-system-vault (system)" which is annoyingly redundant. 😄	19:13:40
maralorn	I can change three things now the name of the disk in disko, the name of the partition and the name of the mounted luks container.	19:14:35
maralorn	Question 1: Which of those identifiers is stateful on disk? i.e. I need to change it before I can reboot successfully.	19:15:31

lassulus

so maybe you don't need mountpoint?

15:17:12

wieldable9080

In reply to @lassulus:lassul.us
maybe you want to set swap.swapfile.path instead of mountpoint?

this is the easy way of doing this :D

15:18:37

wieldable9080

In reply to @lassulus:lassul.us
so maybe you don't need mountpoint?

btrfs subvolume swap has its pros, also it just looks nice

15:19:05

lassulus

hmm, ok, reading the code again, it should also work with a mountpoint set

15:20:24

wieldable9080

doing btrfs swapfile outside of a separate volume is probably a bad idea (has something to do with compression i think)

15:20:26

wieldable9080

In reply to @lassulus:lassul.us
hmm, ok, reading the code again, it should also work with a mountpoint set

i think i took this code from the main repo :D

15:20:55

wieldable9080

i mean, except the subvolume naming

15:21:12

lassulus

whats the error you see on boot?

15:24:17

wieldable9080

In reply to @lassulus:lassul.us
whats the error you see on boot?

timeout waiting for the device which somewhere shows as this swap swap

15:25:34

wieldable9080

In reply to @lassulus:lassul.us
whats the error you see on boot?

*

15:25:41

magic_rb joined the room.

14:19:18

Vilsol

What is the intended way of using disko when doing a clean install with an existing config? Or do I need to do a non-graphical (manual) install?

10:12:25

SigmaSquadron

In reply to @thevilsol:matrix.org
What is the intended way of using disko when doing a clean install with an existing config? Or do I need to do a non-graphical (manual) install?

Get your hardware configuration, and delete the fileSystems options. Import your disko configuration in your configuration.nix, and use disko-install to format and install the system.

11:45:09

netpleb

if I want disko to make a partition but not cause the partition to be formatted or mounted, how do I do that?

16:33:19

wieldable9080

In reply to @netpleb:matrix.org
if I want disko to make a partition but not cause the partition to be formatted or mounted, how do I do that?

Ammm, I saw this message and came to find out, like, what do you mean by "make"??

16:34:13

netpleb

In reply to @wieldable9080:matrix.im
Ammm, I saw this message and came to find out, like, what do you mean by "make"??

I have a disk-config.nix that does my partitioning for whenever provision a new instance of this type of machine (so I am just using nixos-anywhere ...). Can I just leave out the mountPoint and mountOptions in that disk-config?

16:38:09

netpleb

In reply to @wieldable9080:matrix.im
Ammm, I saw this message and came to find out, like, what do you mean by "make"??

* I have a disk-config.nix that does my partitioning for whenever provision a new instance of this type of machine (so I am just using nixos-anywhere ...). Can I just leave out the mountPoint and mountOptions in that disk-config for that partition?

16:38:20

netpleb

here is the disk-config.nix:

{
  disko.devices = {
    disk = {
      sda = {
        type = "disk";
        device = "/dev/sda";
        content = {
          type = "gpt";
          partitions = {
            boot = {
              name = "boot";
              size = "1M";
              type = "EF02";
            };
            esp = {
              name = "ESP";
              size = "500M";
              type = "EF00";
              content = {
                type = "filesystem";
                format = "vfat";
                mountpoint = "/boot";
              };
            };
            root = {
              size = "40G";
              content = {
                type = "btrfs";
                extraArgs = [ "-f" ]; # Override existing partition
                mountpoint = "/";
                mountOptions = [ "compress=zstd" "noatime" ];
              };
            };
            data = {
              size = "100%";
              content = {
                # type = "btrfs";
                extraArgs = [ "-f" ]; # Override existing partition
                # mountpoint = "/data";
                # mountOptions = [ "compress=zstd" "noatime" ];
              };
            };
          };
        };
      };
    };
  };
}

I want that partition currently called "data" to not be mounted and I also do not really even care if it is formatted. I just want the partition to exist. Does that make sense?

16:41:42

netpleb

*

here is the disk-config.nix:

{
  disko.devices = {
    disk = {
      sda = {
        type = "disk";
        device = "/dev/sda";
        content = {
          type = "gpt";
          partitions = {
            boot = {
              name = "boot";
              size = "1M";
              type = "EF02";
            };
            esp = {
              name = "ESP";
              size = "500M";
              type = "EF00";
              content = {
                type = "filesystem";
                format = "vfat";
                mountpoint = "/boot";
              };
            };
            root = {
              size = "40G";
              content = {
                type = "btrfs";
                extraArgs = [ "-f" ]; # Override existing partition
                mountpoint = "/";
                mountOptions = [ "compress=zstd" "noatime" ];
              };
            };
            data = {
              size = "100%";
              content = {
                type = "btrfs";
                extraArgs = [ "-f" ]; # Override existing partition
                # mountpoint = "/data";
                # mountOptions = [ "compress=zstd" "noatime" ];
              };
            };
          };
        };
      };
    };
  };
}

I want that partition currently called "data" to not be mounted and I also do not really even care if it is formatted. I just want the partition to exist. Does that make sense?

16:43:56

netpleb

actually, I figured it out. Looks like just leaving out the mountPoint and mountOptions attributes did the trick!

16:46:49

netpleb

* actually, I figured it out. Looks like just leaving out the mountPoint and mountOptions attributes did the trick! (I did still have to specify the type = btrfs attribute, which is fine. Is there some sort of type = raw where it just does no formatting?

16:47:40

lassulus

You can leave content empty in the partition

16:54:39

networkException (moving to @networkexception:nwex.de) changed their display name from networkException to networkException (moving to @networkexception:nwex.de).