Updating after conversion breaks ZFS

    • OMV 4.x
    • Upgrade 3.x -> 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Updating after conversion breaks ZFS

      I am testing out the conversion from OMV 3.x to 4.x with a ZFS volume. Once the conversion is done, everything works fine; then I go into 'Change Management' and update everything including firmware, python, ZFS and the Linux base files (kernel). However, every time I do this and then reboot the server, ZFS fails - it's like somehow the updates (especially the Linux base/kernel update) remove or unlink the ZFS files.

      Is there a certain order that the first-time updates need to be run in after a 4.x upgrade so that ZFS doesn't get broken?

      UPDATE: Never mind, I got my answer in a previous post - has to do with the headers package (guess it's broke for now)

      The post was edited 1 time, last by SimpTheChimp ().