OMV upgrade 5 to 6 error

  • Hi,


    To start it off, I'm not a tech savvy person when it comes to Linux or programming, I can follow through videos (this is how I installed OMV and created my stand alone server, running Plex) which helped me immensely.

    I still run OMV 5.6.26-1 (Usul) on my server and would love to upgrade to OMV 6.

    I follow instruction videos from Techno Dad on the tube.

    I use Putty to access the server and to do the upgrade but after running the command sudo omv-upgrade I got an error.

    I did the sudo omv-salt stage run deploy first which give no error.


    I'm trying to upgrade rather than fresh install due to setting up docker and portainer again.


    Hope someone able to help.



    I attached the stage run deploy as well as the error file.


    *Edit: I tried to update OMV from the Update manager and failed also, please see attached file as well.


    Many thanks,

    Viktor

  • votdev

    Approved the thread.
  • I am new to omv myself, but I noticed some errors in your attached files.


    "upgrade error.txt" shows connection problems.

    What is your network setup? Have you changed sth in https://[OPENMEDIAVAULT-INSTALLATION]/#/network/interfaces?

    Can you connect/ping any other address? What is the command-line output of ping deb.debian.org and nslookup deb.debian.org?


    And OMV 5 is quite old. You should consider upgrading to OMV 7. As far as I can tell, OMV5 -> OMV6 -> OMV7, should be possible.

    See here:

    https://forum.openmediavault.org/index.php?thread/51753-excellent-omv6-7-upgrade-experience-and-thank-you/&postID=384421#post384421

  • Thank you for he reply.

    I have changed the IPv4 settings from DHCP to Static and added in the relevant information to address, netmask, gateway.

    I changed it back to Static and run the command still the same. (I did the change since it could lose the IP address)


    I tried to follow the post you mentioned from Zoki as well, which is the upgrade error file after typing in step 2.

    Edited 2 times, last by vitya: Adding more info: root@Viktor:~# ping deb.debian.org PING debian.map.fastlydns.net (151.101.130.132) 56(84) bytes of data. 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=1 ttl=55 time=21.3 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=2 ttl=55 time=21.1 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=3 ttl=55 time=21.0 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=4 ttl=55 time=21.3 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=5 ttl=55 time=22.1 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=6 ttl=55 time=21.3 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=7 ttl=55 time=22.0 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=8 ttl=55 time=22.0 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=9 ttl=55 time=21.7 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=10 ttl=55 time=22.2 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=11 ttl=55 time=21.6 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=12 ttl=55 time=21.3 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=13 ttl=55 time=21.5 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=14 ttl=55 time=21.8 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=15 ttl=55 time=22.1 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=16 ttl=55 time=21.9 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=17 ttl=55 time=21.2 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=18 ttl=55 time=21.8 ms 64 bytes from 151.101.130.132 (151.101.130.132): icmp_seq=19 ttl=55 time=22.1 ms ().

  • ryecoaaron

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!