You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When partitioning disks with "disko" (another nix tool) that builds your partition table we can't grep and guess on scsi-0QEMU_QEMU_HARDDISK_.+ sadly, we must provide the full device name.
It would be nice if block device id's are available through the API somehow so we can build an inventory ahead of time! 😄
[lillecarl@hetzner2:~]$ ls -lah /dev/disk/by-id/
total 0
drwxr-xr-x 2 root root 220 Dec 15 18:48 .
drwxr-xr-x 8 root root 160 Dec 15 18:48 ..
lrwxrwxrwx 1 root root 9 Dec 15 18:48 scsi-0HC_Volume_101788715 -> ../../sda
lrwxrwxrwx 1 root root 9 Dec 15 18:48 scsi-0QEMU_QEMU_HARDDISK_55932380 -> ../../sdb
I've compared the ID of my server with the ID of 0QEMU_QEMU_HARDDISK_.+ and it doesn't match.
The text was updated successfully, but these errors were encountered:
What whould you like to see?
When infecting hosts with nixos-anywhere the block device order is all fuzzed. I figured out that the naming scheme for volumes is
and the naming scheme for locally attached disks is
When partitioning disks with "disko" (another nix tool) that builds your partition table we can't grep and guess on
scsi-0QEMU_QEMU_HARDDISK_.+
sadly, we must provide the full device name.It would be nice if block device id's are available through the API somehow so we can build an inventory ahead of time! 😄
I've compared the ID of my server with the ID of 0QEMU_QEMU_HARDDISK_.+ and it doesn't match.
The text was updated successfully, but these errors were encountered: