In reply to @magic_rb:matrix.redalder.org
i wanted to ask: on systems with a MBR parttable i keep getting the warning about it being deprecated and from what i read on the github page of disko, the path forward is to switch to GPT, but i have at least one system where that is impossible and multiple where switching it right now would be very very impractical. Is MBR supported some other way or are you just deprecating support for it completely?

In reply to @magic_rb:matrix.redalder.org
On my ereader the gpt parttable collides with where uboot needs to be, can it be moved somehow? Uboot needs to be at 1k offset from the start of the sd and takes up 3MB roughly

In reply to @annaaurora:artemislena.eu
you're running nixos on you ereader?

then since i couldnt create the diskoImage, i built and booted sd-image-aarch64-installer then tried nixos-anywhere to build the proper system but even that has problems and cant create the partitions

#......
Creating new GPT entries in memory.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
+ sgdisk --align-end --new=1:0:+30M --change-name=1:disk-disk1-firmware --typecode=1:0700 /dev/mmcblk0
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
+ partprobe /dev/mmcblk0
Error: Partition(s) 2 on /dev/mmcblk0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
# it repeats partprobe three times then stops at
mkfs.vfat: unable to open /dev/disk/by-partlabel/disk-disk1-boot: No such file or directory

In reply to @joerg:thalheim.io
I would say it's a bit about expectation management, we won't implement new features for these old stuff and we added the warning to get most people to migrate. But realistically there are enough systems with it still out there that we won't remove it any time soon.

then since i couldnt create the diskoImage, i built and booted sd-image-aarch64-installer then tried nixos-anywhere to build the proper system but even that has problems and cant create the partitions (im guessing i cant install to the same sdcard that im booting from, so i gotta make diskoImages work)

#......
Creating new GPT entries in memory.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
+ sgdisk --align-end --new=1:0:+30M --change-name=1:disk-disk1-firmware --typecode=1:0700 /dev/mmcblk0
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
+ partprobe /dev/mmcblk0
Error: Partition(s) 2 on /dev/mmcblk0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
# it repeats partprobe three times then stops at
mkfs.vfat: unable to open /dev/disk/by-partlabel/disk-disk1-boot: No such file or directory

hi im having trouble creating diskoImages for aarch64-linux. the configuration builds successfully then hangs when creating the diskoImage

EFI stub: Decompressing Linux Kernel...
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Generating empty DTB
EFI stub: Exiting boot services...
# ... was stuck here overnight

ok so i:

• enabled nix-serve binary cache on host1 (x86_64-linux) which has already built the large configuration but got stuck at Exiting boot services...
• tried building on host2 (aarch64-linux) that pulled from cache of host1, and it got stuck at exactly the same step. The assumption was that i was getting stuck on the exiting boot services because i was not aarch64, but now i dont know

ok so i:

• enabled nix-serve binary cache on host1 (x86_64-linux) which has already built the large configuration in qemu but got stuck at Exiting boot services...
• tried building on host2 (aarch64-linux) that pulled from cache of host1, and it got stuck at exactly the same step. The assumption was that i was getting stuck on the exiting boot services because i was not aarch64, but now i dont know

In reply to @lassulus:lassul.us

should be already possible, you are using flakes I guess? you could say something like:

system.build.diskoScript = lib.mkForce (pkgs.writeScriptBin "disko-without-wipe" ''
  ${config.system.build.formatScript}
  ${config.system.build.mountScript}
'');