Transferring drive pool from OMV2.x to OMV4.x

    • OMV 2.x
    • Resolved
    • Transferring drive pool from OMV2.x to OMV4.x

      So I am beginning my journey to upgrade from OMV 2.x to OMV 4.x. I'm a bit of a noob, but I had help from a friend

      The system is used solely for media, Plex and Torrenting.

      I have an OS drive, 5 content drives arranged in a union filesystem, and a SnapRAID drive for parity.

      I decided to try a fresh install over the weekend. It went well getting everything set up, until I connected the content drives. I made a new Union Filesystem from the same drives, and then tried to connect them to Plex. Well, it didn't work. The system appeared to be rearranging files and chowning them, but then it errored out, and the Plex web interface wouldn't even load when I tried get to it.

      The question I have is, what is the best course of action to move a union filesystem over to the new version of OMV? It appears that even drive naming conventions have changed on the new OMV, so I'm a bit lost.

      This is not to mention the fact that I pulled my Plex data backup (which is HUGE... over 60GB) to the new system, only to have it all erased when I tried to install Plex using the OMVExtras Plex plugin. But one problem at a time I suppose.

      Thanks in advance.

      EDIT: Apologies for not selecting the current version, which is 2.x. When I try to edit the post I get an error.

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

    • winemaster wrote:

      only to have it all erased when I tried to install Plex using the OMVExtras Plex plugin
      It only removes the library after copying it to the new location. That said, I have been telling people for months to not use the plugin. use docker instead.

      winemaster wrote:

      what is the best course of action to move a union filesystem over to the new version of OMV?
      Which union filesystem were you using? OMV 2.x had three available. And you don't really move the union filesystem. You are just creating a new pool on top of existing filesystems. When you created the pool, it was most likely fine but the plex plugin was moving files to the new shared folder you selected. This does not do things in the best way. Just one of the many reasons I want to kill the plex plugin with fire.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      It only removes the library after copying it to the new location. That said, I have been telling people for months to not use the plugin. use docker instead.
      This worked like a dream, thank you. Docker is love. Docker is life.


      ryecoaaron wrote:

      Which union filesystem were you using? OMV 2.x had three available. And you don't really move the union filesystem. You are just creating a new pool on top of existing filesystems. When you created the pool, it was most likely fine but the plex plugin was moving files to the new shared folder you selected. This does not do things in the best way. Just one of the many reasons I want to kill the plex plugin with fire.
      It was aufs. And as you said, once I moved to the docker Plex Media Server, it worked perfectly.

      Thanks for your help. I tried to mark the thread resolved, but it wouldn't let me.
    • Users Online 1

      1 Guest