Is there a guide to in place upgrade?

  • Hi all


    Reading bits and pieces in different threads regarding the CLI upgrade path from 5 to 6, but wondered if there's a thread that covers the steps in one place that I'm struggling to find?


    My basic understanding is:


    1. Backup OS drive

    2. Check any used plugins have been ported to OMV6 and if they haven't install via Docker instead

    3. Temporarily remove data drives

    4. Disable running services

    5. Go in via CLI (Putty in my case) and run the couple of update commands (when I find them again!)

    6. Wait

    7. Most likely refresh/clear browser cache

    8. Assuming now running OMV6, stick data drives back in and start services and check everything is working


    Does that cover it? Any missing steps or detail to add to make life easier?

  • 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

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Edited once, last by Zoki ().

    • Official Post

    Is ist necessary to install usrmerge before or will this be done by omv-upgrade?

    omv-release-upgrade will install it if it is needed. https://github.com/openmediava…pre.d/05-install-usrmerge


    Nothing else will install it.

    omv 7.6.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.16 | compose 7.3.3 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    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!

  • Thanks both for contributions - will give this a go in the next couple of days :)


    Zoki - have run that first command - took a little while (thought initially it hadn't done anything) but from what I can see it made quite a number of changes (and nothing appeared to have failed). I managed to lose the text while trying to copy it.....

  • The first command should not change anything on the disk, as all changes should have already been applied. No need to post the output if it did not fail.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Well I'm pleased to report that the installation appears to have gone entirely smoothly! I had to manually remove diskstats and clamav plugins before updating, as they're not on the list. Now I'm in 6 I found them in the list of available plugins to install.


    ETA = link to the list of plugins for folk to check, if they are wanting to follow this


    So far so good - folders all still accessible, updates run and the only oddity is there's a couple of amd64 updates which don't seem to want to play ball:


    Code
    Reading package lists...
    Building dependency tree...
    Reading state information...
    Calculating upgrade...
    The following packages have been kept back:
      linux-image-amd64
    0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

    the other one not mentioned there is linux-image-5.15.0-0.bpo.3-amd64 Linux 5.15 for 64-bit PCs (signed)


    My hardware is an elderly (but entirely reliable) HP N54L