Description of the bug
I cannot configure a local ZFS RAIDZ1 volume as a storage backend. I tried several times and only get an inconclusive error message:
type: AjaxError
code: UNDEFINED_CODE
message: Not Found
trace: AjaxError@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/error.js:3:9
processError@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/ajax.js:134:16
default/<@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/ajax.js:38:35
bn/</s<@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:32970
q/this._error<@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:5798
error@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:2855
_error@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:3093
error@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:2855
u@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:52116
e/Es</<@https://nxt.philps.org/assets/d41e2d63f0862e0f5d6a1ff6fd3a46966093c0b1/lib/vendor/rxjs/rxjs-shared.min.js:3:52512
I'm running this in a machine with a (old) 12-core Xeon, 16 GB RAM and 4x8TB HDD in a RAIDZ1 array (24 TB liquid before formatting.)
Step by step instructions to reproduce the bug
- Start up containers
- Log on to admin GUI
- Create admin password
- Configure local storage
- Point path to ZFS volume
- Log on to normal GUI
- Get error message above
Can you replicate that error from the demo?
No because of ZFS volume
Observed behavior
No files served
Expected behavior
Working like the demos, from a local volume
Description of the bug
I cannot configure a local ZFS RAIDZ1 volume as a storage backend. I tried several times and only get an inconclusive error message:
I'm running this in a machine with a (old) 12-core Xeon, 16 GB RAM and 4x8TB HDD in a RAIDZ1 array (24 TB liquid before formatting.)
Step by step instructions to reproduce the bug
Can you replicate that error from the demo?
No because of ZFS volume
Observed behavior
No files served
Expected behavior
Working like the demos, from a local volume