| 29 Jul 2025 |
 sinan | * on kexec installer i can see all the drives in /dev/disk/by-partlabel/*, but reboot fails with "timed out waiting for device ..." | 12:23:00 |
| sinan | nixos-anywhere, azure | 12:23:10 |
 robsliwi | Which filesystem? | 12:24:16 |
| sinan | ext4 | 12:25:49 |
| sinan | disko conf, https://0x0.st/8RjT.nix | 12:26:19 |
| robsliwi | If you pass generate-hardware-config to nixos-anywhere is there some additional kernel module that is missing in your configuration? | 12:29:04 |
| sinan | no luck
nixos-generate-config just added kvm-amd, also tried out nixos-factor | 12:59:43 |
| sinan | made a repair vm && attached disk image copy
all the partlabels are there & and i was able to mount root drive
| 13:22:24 |
| sinan |
[ 177.907351] EXT4-fs (nvme0n2p3): mounted filesystem eb1db1a9-316b-42d4-a7d1-0483b34255fa r/w with ordered data mode. Quota mode: none.
| 13:22:36 |
| sinan | but when i tried to mount /boot it errored out and i got the following in dmesg
[ 263.242473] FAT-fs (nvme0n2p1): invalid media value (0x7d)
[ 263.242947] FAT-fs (nvme0n2p1): Can't find a valid FAT filesystem
| 13:23:18 |
| sinan | i don't think it's related since the original error was about the root volume | 13:23:38 |
| sinan | as a last effort, i'll switch away from nvme and try booting from a normal disk
i don't think it's diskio related, should be probably handled by nixos-hardware
i recall having a similar problem when using diskio+aws, it's not just azure, worked on hetzner tho | 13:27:26 |
| sinan | nope, no luck | 13:51:59 |
| 30 Jul 2025 |
| sinan | got serial, the drive is not showing up in initrd
https://md-visiqgtxcng5llql.z50.blob.storage.azure.net/10226849-9c65-4a95-be56-538fbc5d6d27/devbox-master.e245caec-1370-4dfa-af2f-019b16af6308.serialconsole.log?sv=2018-03-28&sr=b&sig=8nfIKVbk6%2bf2%2bJ%2fRiI4Eil6rBEuC6ehEIorhID9VbNk%3d&se=2025-07-30T05%3a44%3a26Z&sp=r | 03:44:59 |
| sinan | finally worked, about fuking time
just lsmod | cut -f1 -d' ' from the ubuntu vm, got rid of zfs & spl and added rest to boot.initrd.kernelModules | 06:05:27 |
| 31 Jul 2025 |
|  Max joined the room. | 17:11:35 |
| 2 Aug 2025 |
| sinan changed their profile picture. | 06:58:26 |
| sinan | 06:58:39 |
| sinan | 06:58:46 |
| 3 Aug 2025 |
|  prescientmoon changed their display name from Adriel to prescientmoon. | 14:31:40 |
| sinan changed their profile picture. | 15:07:47 |
|  zsuper joined the room. | 20:28:38 |
| zsuper | hey everyone, im very new to disko and disk partitioning/management in general, but i had a few questions as i prep to use nixos-anywhere to setup/expand my homelab.
i have 5 Intel NUC computers, each with a SSD and a 1.8T HDD. The issue is that some of them report /dev/sda to be the SSD and /dev/sdb to be the HDD, while some do reverse. is this a problem when working with disko? aka would i be able to reuse the same disko config for each one? or do i necessarily need to tailor each one specifically to the output of lsblk?
| 20:33:01 |
| zsuper | * hey everyone, im very new to disko and disk partitioning/management in general, but i had a few questions as i prep to use nixos-anywhere to setup/expand my homelab.
i have 5 Intel NUC computers, each with a SSD and a 1.8T HDD. The issue is that some of them report /dev/sda to be the SSD and /dev/sdb to be the HDD, while some do reverse. is this a problem when working with disko? aka would i be able to reuse the same disko config for each of the 5 computers? or do i necessarily need to tailor each one specifically to the output of lsblk?
| 20:33:24 |
| zsuper | * hey everyone, im very new to disko and disk partitioning/management in general, but i had a few questions as i prep to use nixos-anywhere to setup/expand my homelab.
i have 5 Intel NUC computers, each with a SSD and a 1.8T HDD. The issue is that some of them report /dev/sda to be the SSD and /dev/sdb to be the HDD, while some do reverse. is this a problem when working with disko? aka would i be able to reuse the same disko config for each of the 5 computers? or do i necessarily need to tailor each one specifically to the output of its respective host's lsblk?
| 20:33:41 |
 caraiiwala | I tailor mine with /dev/disk/by-id/... You can still reuse the config though. Unfortunately disko still has issues merging modules so you'd have to import a common config file and override with recursiveUpdate, for example, to declare in full for each host | 20:38:05 |
| caraiiwala | https://github.com/nix-community/disko/issues/678 is what I'm referring to | 20:39:12 |
| zsuper | could you explain how you use disk/by-id/? i guess from the nixos-anywhere POV, what steps would i have to take? | 20:46:50 |
| zsuper | im not super familiar with device names and whatnot, and im moreso nervous here since one of the devs is a HDD while the other is an SSD, so i want to make sure the SSD is prioritized to have the boot partition or whatever | 20:47:59 |
| zsuper | im especially confused here:
{
disko.devices.disk.example = {
type = "disk";
device = "/dev/nvme0n1";
content = {
type = "gpt";
partitions = {
ESP = {
size = "512MiB";
type = "EF00";
priority = 1;
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = [ "umask=0077" ];
};
};
root = {
size = "100%";
priority = 2;
content.format = "ext4";
};
};
};
};
}
how do i know what the Type of the partition is? and also the file system format (i.e. "vfat" vs "ext4")? are these things i just need to know about the hardware beforehand?
| 20:52:32 |
