Assistance required to upgrade distribution V3.0.100 to latest V5.x.x

  • Hi Guys,


    I need some guidance on upgrading my current server distribution to the latest.


    Am I safe to follow the upgrade guide https://openmediavault.readthe…o/en/5.x/various/apt.html or should I look at Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5) and do the upgrade one release at a time?


    My biggest question, which is a nightmare to confirm, is the addons. Below is some information about the addons i still have active and installed. most other addons was removed I don't need anymore or was replaced by docker containers.


    Also, there allot of errors during "apt-get update", anything to be concerned about?


    Currently on V3.0.100 (Erasmus)


    dpkg -l | grep openm

    Code
    ii  openmediavault                                                   3.0.100                              all          Open network attached storage solution
    ii  openmediavault-docker-gui                                        3.1.9                                amd64        OpenMediaVault plugin for Docker
    ii  openmediavault-fail2ban                                          1.3.1                                all          OpenMediaVault Fail2ban plugin
    ii  openmediavault-omvextrasorg                                      3.4.32                               all          OMV-Extras.org Package Repositories for OpenMediaVault
    pc  openmediavault-pyload                                            3.0                                  all          OpenMediaVault pyLoad plugin
    ii  openmediavault-virtualbox                                        3.0.8                                all          VirtualBox plugin for OpenMediaVault.


    apt list --installed | grep openmediavault-

    Code
    openmediavault-docker-gui/now 3.1.9 amd64 [installed,upgradable to: 4.1.6]
    openmediavault-fail2ban/now 1.3.1 all [installed,upgradable to: 4.0.2]
    openmediavault-omvextrasorg/now 3.4.32 all [installed,upgradable to: 4.1.16]
    openmediavault-virtualbox/now 3.0.8 all [installed,upgradable to: 4.1.2]


    apt-get update

    apt-get update.txt

    OMV - v6 - Media Server


    Lian-Li PC-Q25 | Asrock E3C226D2I | Intel® Xeon® Processor E3-1230 v3 | Kingston Valueram 8Gb ddr3-1600 with ECC | OS: Adata SP600 32GB SSD * DATA: 4 x WD 2TB RED HDD's (RAID5)

  • Sn00zE

    Hat das Label von Update auf Upgrade 3.x -> 4.x geändert.
  • There were some updates available in the UI so I tried to run them. Now i dont have a UI - 502 Bad Gateway Ngnix


    See attached list for updates output


    Dateien

    OMV - v6 - Media Server


    Lian-Li PC-Q25 | Asrock E3C226D2I | Intel® Xeon® Processor E3-1230 v3 | Kingston Valueram 8Gb ddr3-1600 with ECC | OS: Adata SP600 32GB SSD * DATA: 4 x WD 2TB RED HDD's (RAID5)

    • Offizieller Beitrag

    should I look at Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5) and do the upgrade one release at a time?

    Definitely this option.

    My biggest question, which is a nightmare to confirm, is the addons. Below is some information about the addons i still have active and installed. most other addons was removed I don't need anymore or was replaced by docker containers.

    Why is it nightmare? The docker plugin is gone but you can use portainer that has an install button in omv-extras. fail2ban is still around. The virtualbox plugin is no longer because virtualbox isn't in the debian 10 repos and phpvirtualbox isn't really maintained anymore. But I wrote a kvm plugin and it even has a feature to convert virtualbox disks to kvm.


    here were some updates available in the UI so I tried to run them. Now i dont have a UI - 502 Bad Gateway Ngnix


    See attached list for updates output

    Your system is a mess. I would consider a fresh install. As long as your docker containers and VM disks are on data disks, it should be easy to recreate everything.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Your system is a mess. I would consider a fresh install. As long as your docker containers and VM disks are on data disks, it should be easy to recreate everything.

    Damn, also think so yes, cant do any installs or even uninstalls of packages.


    Just to check, I have my docker containers on a data disk. Can the previous docker data be imported, ie. all the previous settings and docker profiles?


    Guess I have to redo all my samba folder permissions for all shares? Had ACL settings on media directories.

    OMV - v6 - Media Server


    Lian-Li PC-Q25 | Asrock E3C226D2I | Intel® Xeon® Processor E3-1230 v3 | Kingston Valueram 8Gb ddr3-1600 with ECC | OS: Adata SP600 32GB SSD * DATA: 4 x WD 2TB RED HDD's (RAID5)

    • Offizieller Beitrag

    Can the previous docker data be imported, ie. all the previous settings and docker profiles?

    Depends on where they are stored. It is probably easier to recreate the containers and keep using your old volumes to not lose config/data from the particular container.


    Guess I have to redo all my samba folder permissions for all shares? Had ACL settings on media directories.

    Technically ACLs are stored on the filesystem but they are also partially stored in the omv database. Recreating them would probably be better but might not be required. I hate ACLs and don't use them. So, I couldn't really tell you.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thank you for the input. Will see what I can do.

    OMV - v6 - Media Server


    Lian-Li PC-Q25 | Asrock E3C226D2I | Intel® Xeon® Processor E3-1230 v3 | Kingston Valueram 8Gb ddr3-1600 with ECC | OS: Adata SP600 32GB SSD * DATA: 4 x WD 2TB RED HDD's (RAID5)

  • Sn00zE

    Hat das Label von OMV 3.x auf OMV 5.x geändert.
  • Sn00zE

    Hat das Label von Upgrade 3.x -> 4.x auf Update geändert.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!