Is there a guide to in place upgrade?

    Hi, I want to upgrade too. How should I backup the os disk?

    Other than that I don't need to to anything particular right? As stated before I don't need to unplug the other disks

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

    Quote from Blabla

    How should I backup the os disk?

    I use dd run out of an automated script that runs daily.


    Any backup strategy is worthless unless you have proven to yourself that the backups can be successfully restored. The time to find out that your backups fail to restore is during testing, not when you have experienced a real system drive failure.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 6.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Like 1
    • Official Post
    Quote from metRo_

    How do I know if they have been ported to 6?

    Thread
    omv-extras plugins - porting progress to OMV 6.x (done)
    Here is the current status of porting omv-extras plugins to OMV 6.x. If the plugin isn't on the list, it won't be ported or is a core OMV plugin.

    25 of 25 - done


    openmediavault-anacron - done
    openmediavault-apttool - done
    openmediavault-autoshutdown - done (thanks to nrandon)
    openmediavault-backup - done
    openmediavault-borgbackup - done
    openmediavault-developer - done
    openmediavault-downloader - done
    openmediavault-fail2ban - done
    openmediavault-flashmemory - done
    openmediavault-kvm - done
    …
    ryecoaaron
    • Official Post
    Quote from metRo_

    Is my version too old?

    Your version is OMV5. You should be able to upgrade to OMV6 by following the instructions in this thread if you don't want to do a fresh install.

    Be careful with the omv-extras repositories, they changed to github a long time ago, I think you have them wrong.

    • Official Post
    Thread
    omv-extras repos moving to github
    Because Bintray is dropping their repo hosting service (https://jfrog.com/blog/into-th…gocenter-and-chartcenter/) on 2021-05-01, I have moved the omv-extras repos to github. omv-extras 5.5 will change the repos to point to github. This package is in the testing repo now. People will have until bintray is shutdown to upgrade. I will move the 5.5 package of omv-extras to the regular OMV 5.x repo in a few days. I might release an OMV 4.x package with the updated repos but I am not releasing a…
    ryecoaaron

    In this thread they explain how to solve the repository change.

    If you don't have much experience, I recommend that you do a fresh installation of OMV6. I think you will avoid problems.

    Quote from Zoki

    Contributions wanted:

    1. Backup the OS drive (this is allways a good idea, not only for upgrades)
    2. Make sure, you have enough free space on your os drive
    3. Check any installed plugins if they have been ported to OMV6
      If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
      (Many plugins can be replaced by docker containers. Do this before upgrading)
    4. If you installed software from foreign repos make sure they have a release for bullseye or remove the repos / software
    5. Go to the cli (Putty, ssh, keyboard) and run these commands (In case of errors stop and ask on the forum before makingthings worse)
      1. Make sure your current install is correct all configs can be deployed by running sudo omv-salt stage run deploy
      2. Get the current install up to date: sudo omv-upgrade
      3. Do the release upgrade by running sudo omv-release-upgrade
        If you see an error message from patch which says a patch has alredy been applied, ignore it. (this is the only error to be ignored)
    6. Wait for the last script to finish and reboot.
    7. Refresh/clear browser cache (Crtl-Shift R on most browsers)
    8. Check if all services and docker containers are running as you expect.
    9. If you see Linux image Updates you can not install on the UI, go to the cli and run omv-upgrade once more.


    Edit:

    • Added hint to run omv-upgrade if images can not be updated in UI

    Thank you for this!!! WHY is this not posted on the OMV home page? 1. I was not aware that the upgrade was available. 2. When I found out 6 was out, I looked on the web page, and NOTHING was mentioned about how to upgrade. Usually "how to upgrade" is an important factor in most software systems. Am I missing something???


    OMV has been rock solid for our needs, upgrade was extremely smooth.

    • Official Post
    Quote from sak.rice

    1. I was not aware that the upgrade was available. 2. When I found out 6 was out, I looked on the web page, and NOTHING was mentioned about how to upgrade. Usually "how to upgrade" is an important factor in most software systems. Am I missing something???

    https://www.openmediavault.org/?p=3201

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


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


    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!

    Quote from ryecoaaron

    https://www.openmediavault.org/?p=3201

    My "it isn't mentioned" complaint is about the upgrade procedure. It is mentioned in the next to last line on that page, but very easy to miss, and unclear.

    Also the EOL for v5 should be a sticky on the main page for a few months to make it very clear to everyone. I didn't know it was no longer maintained. I just think it could have been more clear and obvious how to upgrade. I ended up searching the forums and finding the very clear instructions in the second post on this thread.

    • Official Post
    Quote from sak.rice

    My "it isn't mentioned" complaint is about the upgrade procedure. It is mentioned in the next to last line

    But it is mentioned. And it is in the official docs - https://openmediavault.readthe…n/latest/various/apt.html. And it hasn't changed in all versions of OMV that were upgradable. I personally don't think the home page or blog should have upgrade instructions. There are almost always other questions and the official docs and forum are the best place for those.

    Quote from sak.rice

    Also the EOL for v5 should be a sticky on the main page for a few months to make it very clear to everyone. I didn't know it was no longer maintained

    There is a blog announcing it - https://www.openmediavault.org/?p=3259 - and a twitter post. As for a sticky, I can tell you that barely anyone reads those. Trust me. Just remember Volker is one guy. It takes a lot of time to put the info people want in every location they think it should be in.

    Quote from sak.rice

    I just think it could have been more clear and obvious how to upgrade

    It is literally one command - omv-release-upgrade. The other posts have more steps when omv-extras is involved. Volker should not be responsible for those steps. The forum is the right place to look for that info.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


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


    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!

    I agree that the sticking the post in the blog wouldn't solve much. I think it would be better to push a small update on OMV that will prompt the user with a warning "this version is EOL, it will keep working but it won't recieve any new update" or something like that.

    I would also add a link to the wiki page for the upgrade just in case.

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

    Quote from macom

    Try to configure the network interface using omv-firstaid


    If that is not working, remove the mentioned file and try again.

    rm /etc/netplan/20-openmediavault-enx001e0632bfca.yaml

    sudo omv-salt stage run deploy

    Still the same error.

    No access via ssh.

    nano /etc/netplan/20-openmediavault-enx001e0632bfca.yaml

    It was enough to put manually MAC in lane:

    Code
    network:
  ethernets:
    enx001e0632bfca:
      match:
        macaddress: HERE
      dhcp4: true
      dhcp6: false
      link-local: []
      wakeonlan: true

    I have access to my odroid. And after:

    Code
    sudo omv-upgrade
sudo omv-release-upgrade

    I got a message that upgrade was successfull

    reboot

    but in ssh:

    root@OMV:~# uname -a

    Linux OMV 4.14.222-odroidxu4 #1 SMP PREEMPT Mon Nov 22 12:13:27 UTC 2021 armv7l GNU/Linux


    It's a new version? In GUI system information is empty.


    dpkg -l | grep openmediavault

    ii openmediavault 5.6.26-1 all openmediavault - The open network attached storage solution

    ii openmediavault-backup 5.2.4 all backup plugin for OpenMediaVault.

    ii openmediavault-flashmemory 5.0.9 all folder2ram plugin for OpenMediaVault

    ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

    ii openmediavault-omvextrasorg 5.6.6 all OMV-Extras.org Package Repositories for OpenMediaVault

    ii openmediavault-resetperms 5.0 all Reset Permissions


    Is not.

    But why?

Participate now!

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

Register Yourself Login