Of course, I already attached a new disk to my VMware VM (hosted on ESXi).
I also tried to format it in ext4 and mount it, but still get the same error.
You can see below that the disk sdb and its partition exist:
I don’t know if it’s important to know but it seems that the script unmount my secondary disk since it’s up before running the script but then, it doesn’t appear anymore in my “fdisk -l” result command.
Why do I get this error?
Should I set up the ZFS partition myself?
Is it a bug from the script?
@enoch85 - quick question. I’m having a similar problem with the script not picking up a second drive. Am I right in assuming that it’s looking for “sda” and “sdb”?
Because I’m using /vda and /vdb and whether i use the manual or automatic 2-disk option, neither way will pick up that I have a second drive. fdisk is quite happy that it is there, and not mounted, but the script doesn’t want to see it.
Happy to try a workaround if there is one, otherwise I can just burn this VM and create a new one using SATA emulation as opposed to VirtIO.