| 3 Aug 2025 |
 zsuper | so when adding a new machine to my network, i should aim for a workflow that looks like:
- ssh into the target and run
ls -l /dev/disk/by-id/
- using that information, write a disko configuration at
./modules/node-specific/machine-X/disko.nix
- Run
nixos-anywhere using that disko.nix
- Add a node to my
deploy-rs setup, which reuses that same disko.nix (and anything else in node-specific/machine-X/)
- Future rebuilds are done via
deploy-rs
| 21:42:42 |
| zsuper | okay, and should i bother reading up on the different types? Or should I just internalize the fact that "EF00/vfat" correlates to the boot partition? | 21:45:14 |
| zsuper | * okay, and should i bother reading up on the different types? Or should I just internalize the fact that "EF00/vfat" correlates to the boot partition? and for the rest of my disk config just make it ext4 and a type = filesystem? | 21:46:07 |
 caraiiwala | Node-specific yes, just like the rest of NixOS | 21:46:18 |
| caraiiwala | Workflow is good | 21:46:33 |
| caraiiwala | It's sufficient to start simple this way but you should try to understand what you are doing. Nobody should have to tell you to educate yourself | 21:48:22 |
| zsuper | Yeah, I'm pretty confident about how the deployment tools function, but i have literally never touched file systems and device/disks before, so all of this is very alien. Plus the lack of actual documentation for disko makes it very difficult to self teach. In any case, thank you for filling the gaps in my basic understanding! | 21:50:58 |
| caraiiwala | Definitely spend some time watching YouTube videos or something to understand filesystem formatting and disk partitioning. I think disko rightfully leaves the understanding of these concepts up to the user. With a solid foundation, the disko model is very clear imo | 21:57:06 |
| 4 Aug 2025 |
| zsuper | ahh, this was the table i needed: https://askubuntu.com/questions/703443/gdisk-hex-codes
up until now the terms ESP, EF00, EF02 were completely random to me, but now I understand that ESP stands for EFI System Partition and the latter 2 are hex codes that Gdisk uses, which implies that disko likely uses Gdisk under the hood, right? | 01:44:50 |
| zsuper | this is actually super cool, i can definitely see why I should read into this stuff before jumping directly into disko. great tool! | 01:45:35 |
 lassulus | In reply to @caraiiwala:beeper.com
https://github.com/nix-community/disko/issues/678 is what I'm referring to This should be fixed in the current master | 06:26:03 |
 matthewcroughan | Getting this on a new hetzner install | 23:29:28 |
| matthewcroughan | /nix/store/4ps8pa311972zw8k9c7z21w04qhwpr8j-grub-2.12/sbin/grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
/nix/store/4ps8pa311972zw8k9c7z21w04qhwpr8j-grub-2.12/sbin/grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/nix/store/4ps8pa311972zw8k9c7z21w04qhwpr8j-grub-2.12/sbin/grub-install: error: will not proceed with blocklists.
/nix/store/dhn57d6hqajp0j77l33alsqwvv54kv5a-install-grub.pl: installation of GRUB on /dev/sda failed: No such file or directory
Failed to install bootloader
| 23:29:30 |
| 5 Aug 2025 |
 hexa | hm, I have this one machine left that doesn't want to migrate to the new GPT layout | 01:01:29 |
| hexa | Redacted or Malformed Event | 01:01:49 |
| hexa | # sgdisk -c 1:disk-nvme-ESP /dev/sda1
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Unable to set partition 1's name to 'disk-nvme-ESP'!
Error encountered; not saving changes.
| 01:02:07 |
| hexa | ach bla, das muss gegen /dev/sda | 01:03:10 |
| hexa | danke | 01:03:47 |
| hexa | 🦆 | 01:03:50 |
|  sinan changed their profile picture. | 03:58:54 |
| sinan | 03:58:56 |
