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
Here's an interesting one. I created a pool on a thumb drive, which worked fine after using just PHYSICALDRIVE1 instead of \\.\PHYSICALDRIVE1. Wrote some data, all is well. Then I export it, and all seems well (returns 0).
Immediately attempting to import it, the pool meta is apparently read, but cannot be imported because the vdev is unavailable.
The pool does successfully import (and export) on another system. without issue, but the pool is forevermore unable to be used by ZFSin.
Not really sure what other pertinent information I can provide, other than that the drive is a multi-function device that may not be enumerated as the first physical lun on the adapter (I believe the CDROM is always first).
The text was updated successfully, but these errors were encountered:
I will note that the pool is in fact still fine and can be mounted on other official releases of OpenZFS (i.e. whatever is included by Ubuntu 20 LTS at the moment). Just that the Windows build can't import it again...
Here's an interesting one. I created a pool on a thumb drive, which worked fine after using just
PHYSICALDRIVE1
instead of\\.\PHYSICALDRIVE1
. Wrote some data, all is well. Then I export it, and all seems well (returns 0).Immediately attempting to import it, the pool meta is apparently read, but cannot be imported because the vdev is unavailable.
The pool does successfully import (and export) on another system. without issue, but the pool is forevermore unable to be used by ZFSin.
https://pastebin.com/dM24T2GT
Not really sure what other pertinent information I can provide, other than that the drive is a multi-function device that may not be enumerated as the first physical lun on the adapter (I believe the CDROM is always first).
The text was updated successfully, but these errors were encountered: