I've had a great experience with ZFS up until something strange happened. I downloaded the most recent version of this menu bar application https://github.com/cbreak-black/ZetaWatch to help me manage my zpools at boot. I have 4 pools of mirrored vdevs and they each have an encrypted dataset except for Fentanyl where I store data directly on the pool (Fentanyl 2x1.5TB SATA motherboard controller, Ketamina 2x3TB SATA motherboard controller, Diprivan 2x3TB LSI PCIe SAS HBA, Midazolam 2x3TB LSI PCIe SAS HBA). I ran ZetaWatch and it failed to import the pools that had an encrypted dataset on it but it did report that the plain unencrypted pool Fentanyl was OK.
After this I tried to zpool import -a and got an error "zfs: cannot import Diprivan: I/O error Destroy and re-create the pool from a backup" and the same error for Midazolam. I exported all pools and rebooted. This time Fentanyl still worked fine and Midazolam was able to be imported zpool import Midazolam and the encrypted dataset within mounted, but Diprivan had the same I/O error. Ketamina no longer existed at all. It wasn't in disk utility and when I ran diskutil list the two disks that used to be called Ketamina are now called Midazolam also. Four disks in diskutil were reporting their names as Midazolam. I exported everything, shutdown and removed the disks that make up my two working pools, Fentanyl and Midazolam. I rebooted and tried to import Ketamina, no pool exists and when I tried to import Midazolam (falsely named) I got "cannot import 'Midazolam': one or more devices is currently unavailable". I have not tried to fix Diprivan yet fearing I could make this situation worse so only work with one at a time.
Reading up on the FreeNAS and zfsonlinux boards haven't given me any leads. Thank you for your time and any ideas you can give me how to fix this.
macos high sierra 10.13.6
OpenZFS on OS X 1.8.2