Hello
I've seen hard disks being referenced by their IDs, i.e. /dev/disk/by-id/something in some threats (example) as well as the mail archives, which is IMO quite useful - partition labels do the job elsewhere but I read recommendations everywhere to use whole disks for zpool-vdevs.
My problem is, that I don't even have the /dev/disk directory to begin with. I guess it's a kernel module or config option that needs to be loaded/set (since zfsboot eventually can't access /etc/devd.conf when booting to zfs-root backed by disk-id vdevs), but I don't know which one...
... can anyone tell me?
I've seen hard disks being referenced by their IDs, i.e. /dev/disk/by-id/something in some threats (example) as well as the mail archives, which is IMO quite useful - partition labels do the job elsewhere but I read recommendations everywhere to use whole disks for zpool-vdevs.
My problem is, that I don't even have the /dev/disk directory to begin with. I guess it's a kernel module or config option that needs to be loaded/set (since zfsboot eventually can't access /etc/devd.conf when booting to zfs-root backed by disk-id vdevs), but I don't know which one...
... can anyone tell me?