!oNSIfazDqEcwhcOjSL:matrix.org

disko

366 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko94 Servers

Load older messages


SenderMessageTime
19 May 2024
@matthewcroughan:defenestrate.itmatthewcroughanFFFFFFFFFFFFFF21:18:34
@matthewcroughan:defenestrate.itmatthewcroughanAlthough it does highlight that disko shouldn't be using the target kernel, just to make the disk image for the target21:19:38
@matthewcroughan:defenestrate.itmatthewcroughanIt was me who implemented that though, so I should feel bad21:44:38
@matthewcroughan:defenestrate.itmatthewcroughanhttps://github.com/nix-community/disko/pull/46721:44:53
@matthewcroughan:defenestrate.itmatthewcroughanThe solution is uefi, but is there a use case for not using UEFI?22:05:38
@matthewcroughan:defenestrate.itmatthewcroughanI can make the PR, but wondering if I should make it boolean22:06:10
20 May 2024
@matthewcroughan:defenestrate.itmatthewcroughanhttps://github.com/nix-community/disko/pull/64308:46:42
@matthewcroughan:defenestrate.itmatthewcroughanCloser to finding memory leaks..09:34:35
@matthewcroughan:defenestrate.itmatthewcroughanI switched to systemd-boot from generic-extlinux, and now I'm getting the "Cannot allocate memory" all the time09:34:50
@matthewcroughan:defenestrate.itmatthewcroughanincreasing memory to 16384 fixed it09:40:09
@matthewcroughan:defenestrate.itmatthewcroughan
corpo-disko-images> setting up /etc...
corpo-disko-images> Initializing machine ID from random generator.
corpo-disko-images> File system "/boot" is not a FAT EFI System Partition (ESP) file system.
corpo-disko-images> Traceback (most recent call last):
corpo-disko-images>   File "/nix/store/hk9khalas7ig9lpd8xygb00jgx9kjv2d-4d4f3f52hgwgk63d4fjg1rj4c1jdg9mn-systemd-boot", line 394, in <module>
corpo-disko-images>     main()
corpo-disko-images>   File "/nix/store/hk9khalas7ig9lpd8xygb00jgx9kjv2d-4d4f3f52hgwgk63d4fjg1rj4c1jdg9mn-systemd-boot", line 377, in main
corpo-disko-images>     install_bootloader(args)
corpo-disko-images>   File "/nix/store/hk9khalas7ig9lpd8xygb00jgx9kjv2d-4d4f3f52hgwgk63d4fjg1rj4c1jdg9mn-systemd-boot", line 292, in install_bootloader
corpo-disko-images>     subprocess.check_call([f"{SYSTEMD}/bin/bootctl", f"--esp-path={EFI_SYS_MOUNT_POINT}"] + bootctl_flags + ["install"])
corpo-disko-images>   File "/nix/store/vbfsfi87f7ks3hndbvn72n4334f9xll0-python3-3.11.9/lib/python3.11/subprocess.py", line 413, in check_call
corpo-disko-images>     raise CalledProcessError(retcode, cmd)
corpo-disko-images> subprocess.CalledProcessError: Command '['/nix/store/wh5wyrs4nxdx7kh3ip0psn11rc2kknl1-systemd-255.4/bin/bootctl', '--esp-path=/boot', '--no-variables', 'install']' returned non-zero exit status 1.
09:40:12
@matthewcroughan:defenestrate.itmatthewcroughanAnd then I see this for the first time, which is good. It warns me that my FS hasn't got the right type09:40:38
@matthewcroughan:defenestrate.itmatthewcroughanbut this part of the build never arrives unless I increase the memory size09:40:51
@matthewcroughan:defenestrate.itmatthewcroughan though the "Cannot allocate memory" errors come from cp.. actually. 09:41:18
@matthewcroughan:defenestrate.itmatthewcroughan The bootloader install is probably calling cp, 09:41:38
@matthewcroughan:defenestrate.itmatthewcroughan * The bootloader install is probably calling cp 09:41:40
@matthewcroughan:defenestrate.itmatthewcroughan
corpo-disko-images> + /nix/store/gc39rhvazg28s7y80c4c0a24x3hsv92p-postMountHook.sh
corpo-disko-images> + rm -rf /tmp/tmp.qOc2Qrmj2x
corpo-disko-images> warning: the group 'nixbld' specified in 'build-users-group' does not exist
corpo-disko-images> cp: cannot access '/nix/store/flqdgxi79hgv69k8vc1rdcxvn30m0i3r-perl5.38.2-HTTP-Cookies-6.10': Cannot allocate memory
corpo-disko-images> cp: cannot access '/nix/store/fzh5aadrdl76f7cn930ls979x6cgblyd-libsoup-2.74.3/share/locale/gl/LC_MESSAGES': Cannot allocate memory
09:41:58
21 May 2024
@bumperboat:matrix.orgbumperboat changed their display name from bumperboat (UTC+8) to bumperboat (UTC+7).04:34:19
@matthewcroughan:defenestrate.itmatthewcroughan lassulus: any comments on https://github.com/nix-community/disko/pull/643 ? 11:31:00
@matthewcroughan:defenestrate.itmatthewcroughanI didn't really think it's worth setting up a boolean, since it passes all the tests and I can't yet imagine a use-case where you'd want to disable EFI, especially given that legacy types are not supported in disko properly anymore11:31:46
@tanja:catgirl.cloudTanja (she/her) joined the room.11:37:13
@matthewcroughan:defenestrate.itmatthewcroughanthanks for the merge :D11:42:14
22 May 2024
@aciceri:nixos.devzrsk joined the room.10:05:06
@aciceri:nixos.devzrsk

I'm interested into trying bcachefs with encryption using disko and I saw that there is a PR which is blocked because it should an abstraction for supporting multiple devices should be implemented before.
I also saw there is another PR for supporting subvolumes.
Would a PR where I try to integrate both the attempts together be appreciated? In terms of interface would you like something similar to the first proposal in this comment?

 disko.devices = {
    disk = {
      x = {
        type = "disk";
        device = "/dev/nvme0";
        content = {
          type = "gpt";
          content = {
            type = "bcachefs";
            label = "ssd.ssd1";
            pool = "rpool";
          };
        };
      };
      y = {
        type = "disk";
        device = "/dev/sda";
        content = {
          type = "bcachefs";
          label = "hdd.hdd1";
          pool = "rpool";
        };
      };
    };

    bcachefs_pool = {
      rpool = {
        type = "bcachefs_pool";
        mountpoint = "/";
        passwordFile = "secret.key";
        subvolumes = {
            "/home" = { };
            "/nix" = { };
            "/testpath" = { };
            "/testpath/subdir" = { };
          };
      };
    };
  };
10:06:36
@lassulus:lassul.uslassulusI answered in nixos-anywhere, but I can also answer here10:16:49
@lassulus:lassul.uslassulusI was a bit busy, I wil try to fix the multi disk stuff in general at some point. But not sure when I will have the time for that. I guess we could merge the encryption part without the multidisk part. I have no idea about subvolumes, but a new PR could be a good idea, just remind me every now and then to look at it :)10:17:18
@aciceri:nixos.devzrsk
In reply to @lassulus:lassul.us
I answered in nixos-anywhere, but I can also answer here
Oh I saw it too late, let's keep the discussion here then :)
Frankly I'm not particularly interested into subvolumes, which to my understanding are useful only for snapshots. I can try to rebase the first PR and see if everything works if you want.
10:28:31
@aciceri:nixos.devzrsk Nevermind, I don't think it can be easily rebased. It looks like in master you are using the filesystem type while the PR added a new custom type. 10:31:16
@aciceri:nixos.devzrsk Probably one could get encryption by simply setting extraArgs = [ "--encrypted" ] 10:32:15
@aciceri:nixos.devzrsk At least if you are interested into using a passphrase, I tried yesterday to imperatively format a disk with --encrypted and it interactively asked a passphrase 10:34:15

Show newer messages


Back to Room ListRoom Version: 10