Closed Finkregh closed 8 years ago
The plugin has not been adapted to work with versions higher than 3.0.15. You'll have to go back to .13 version of Omv if you want to keep using the plugin.
hmm, the depends seems not to work as intended, as i was able to install these versions w/o problems...
AFAIR it should not be
openmediavault (>= 1.7) | openmediavault (<= 3.0.13)
(X OR Y)
but
openmediavault (>= 1.7), openmediavault (<= 3.0.13)
(X AND Y)
this is not tested, so i wont create a merge-request :o
I have the same problem, therefore OMV is practically unusable if you are using ZFS. I don't know how to test the solution of @Finkregh, but would love to test it.
He didn't have a solution other than to keep the plugin from installing on OMV > 3.0.13. Until it is ported you will have to use zfs manually or wait. OMV 3.x hasn't been released yet anyway.
Why close this if there is a possible fix available?
There isn't a "fix" available. This just keeps someone from installing the current plugin on a version of OMV newer than 3.0.13. Making code changes to let someone stay on an old version is bad idea in my opinion and the plugin needs a lot of code re-written to work on the latest OMV.
When i install omv-zfs as described in http://forums.openmediavault.org/index.php/Thread/7633-HOWTO-Instal-ZFS-Plugin-use-ZFS-on-OMV/ the omv-engined wont start anymore.
ZFS is installed and works properly, i can see filsystems running e.g.
zpool import -d /dev/
; i did reboot after installation.