!oNSIfazDqEcwhcOjSL:matrix.org

disko

349 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko87 Servers

Load older messages


SenderMessageTime
23 Nov 2025
@d:metropolis.nexusdave :3 set a profile picture.16:52:42
@nagasaki:matrix.pyxiss.deNagasakiMy best use case is in virtualisation. Like declaring how big your disk in a virtual machine is.20:21:16
@spewdins:beeper.comspewdinsooo that’s a really good use case…20:21:43
@debtquity:matrix.orgdebtquity

can disko be used to re-configure partitions?

currently, system is setup like this:

NAME          MOUNTPOINT LABEL      SIZE
sda                               223.6G
├─sda1                                1M
├─sda2        /boot                 500M
└─sda3                            223.1G
  ├─pool-app  /app                   10G
  └─pool-root /                   213.1G
sdb                                28.9G
├─sdb1                   FIRMWARE    30M
└─sdb2                   NIXOS_SD  28.9G

But really, I want to move the FIRMWARE labeled partition on sdb to sda

23:58:16
25 Nov 2025
@sylvie:karp.lolSylvie (They/She) 🏳️‍⚧️ changed their display name from Sylvie (any) 🏳️‍⚧️ to Sylvie (They/She) 🏳️‍⚧️.15:49:18
@steeringwheelrules:tchncs.de@steeringwheelrules:tchncs.de left the room.18:12:22
@disco_stick:matrix.orgredesign your logo changed their display name from Juggalo Championship Wrestling to redesign your logo.19:51:37
28 Nov 2025
@mou_bugtracker:matrix.orgmou joined the room.18:22:34
29 Nov 2025
@not-jack:matrix.orgnot-jack joined the room.18:37:29
30 Nov 2025
@not-jack:matrix.orgnot-jack

whats the advantage to having both boot and an ESP partitions?

          partitions = {
            boot = {
              size = "1M";
              type = "EF02"; # for grub MBR
            };
            ESP = {
              size = "1G";
              type = "EF00";
              content = {
                type = "filesystem";
                format = "vfat";
                mountpoint = "/boot";
                mountOptions = [ "umask=0077" ];
              };
            };
13:39:39
@not-jack:matrix.orgnot-jack *

whats the advantage to having both boot and an ESP partitions?

          partitions = {
            boot = {
              size = "1M";
              type = "EF02"; # for grub MBR
            };
            ESP = {
              size = "1G";
              type = "EF00";
              content = {
                type = "filesystem";
                format = "vfat";
                mountpoint = "/boot";
                mountOptions = [ "umask=0077" ];
              };
            };
13:39:49
@not-jack:matrix.orgnot-jack what does the boot partition do here? 13:44:42
@hexa:lossy.networkhexathat's called hybrid14:04:27
@hexa:lossy.networkhexaif you don't care or the thing needs to be portable14:04:36
@not-jack:matrix.orgnot-jackso i can get rid of it?14:05:47
@mou_bugtracker:matrix.orgmou

I'm using systemd-boot (no grub) with UEFI, and for this it is enought to have single /boot with ESP like this

          type = "gpt";
          partitions = {
            ESP = {
              type = "EF00";
              size = "2G";
              content = {
                type = "filesystem";
                format = "vfat";
                mountpoint = "/boot";
              };
            };
14:08:25
@mou_bugtracker:matrix.orgmoubut your config mentioned MBR in comments, so it might be different situation for you14:09:13
@not-jack:matrix.orgnot-jackthis is the default config for single disk ext414:10:19
@not-jack:matrix.orgnot-jackso i think we're in the same situation14:11:48
@mou_bugtracker:matrix.orgmouAs i understand logic of the boot process, the important part is decide are you using UEFI. If yes, you have to have GPT partition table (not mbr) and old MBR requirement to have bootloader in first 512K of the drive is no longer reuirement. So this reservation for grub is not needed 14:15:35
@not-jack:matrix.orgnot-jackaha, so it's legacy for backwards compat with grum14:16:46
@not-jack:matrix.orgnot-jack* aha, so it's legacy for backwards compat with grub14:16:48
@mou_bugtracker:matrix.orgmouIt is not grub specific. It is applicable to any bootloader for MBR partitioned drive. All bootloader put their initialization code into first 512K right after partition table14:17:51
@not-jack:matrix.orgnot-jack * aha, so it's legacy for backwards compat with grub MBR 14:19:33
@mou_bugtracker:matrix.orgmouBut i did not refreshed my knowledge in this area for last decade, so i might mix things up. So, if you want to be sure, do additional check.14:19:34
@not-jack:matrix.orgnot-jackthe check will be seeing if i can boot!14:19:50
@mou_bugtracker:matrix.orgmouHere is more in depth explanation of the logic. https://superuser.com/questions/1566558/is-a-boot-sector-considered-to-be-a-partition14:22:28
@not-jack:matrix.orgnot-jackthanks, that helps :)14:26:46
@spewdins:beeper.comspewdins

For those using disko for vm’s disk sizes…

I wonder. Are you declaratively setting your vm .qcow2 for example, from the host system? Or from inside the vm.

17:03:16
@not-jack:matrix.orgnot-jackWhen using disko-install, i get no space left on device19:59:11

Show newer messages


Back to Room ListRoom Version: 10