Is there a guide to in place upgrade?

Bolanger · Jul 12th 2025

Code

Unpacking shairport-sync (3.2.2-1+b2) ...
Setting up libgme0:armhf (0.6.2-1) ...
Setting up libconfig9:armhf (1.5-0.4) ...
Setting up libssh-gcrypt-4:armhf (0.8.7-1+deb10u2) ...
Setting up libx11-xcb1:armhf (2:1.6.7-1+deb10u4) ...
Setting up libmpg123-0:armhf (1.25.10-2) ...
Setting up libogg0:armhf (1.3.2-1+b2) ...
Setting up libspeex1:armhf (1.2~rc1.2-1+b2) ...
Setting up libantlr3c-3.4-0:armhf (3.4+dfsg-3) ...
Setting up libshine3:armhf (3.1.1-2+b1) ...
Setting up libplist3:armhf (2.0.1~git20190104.3f96731-1) ...
Setting up libxi6:armhf (2:1.7.9-1) ...
Setting up libtwolame0:armhf (0.3.13-4) ...
Setting up libgsm1:armhf (1.0.18-2) ...
Setting up libx264-155:armhf (2:0.155.2917+git0a84d98-2+rpi1) ...
Setting up libsoxr0:armhf (0.1.2-3) ...
Setting up libx265-165:armhf (2.9-4) ...
Setting up libev4:armhf (1:4.25-1) ...
Setting up libaom0:armhf (1.0.0-3+deb10u1) ...
Setting up libcodec2-0.8.1:armhf (0.8.1-2) ...
Setting up x11-common (1:7.7+19) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up libmysofa0:armhf (0.6~dfsg0-3+deb10u1) ...
Setting up libxvidcore4:armhf (2:1.3.5-1) ...
Setting up libsnappy1v5:armhf (1.1.7-1) ...
Setting up libflac8:armhf (1.3.2-3+deb10u3) ...
Setting up libuv1:armhf (1.24.1-1+deb10u2) ...
Setting up libass9:armhf (1:0.14.0-2) ...
Setting up libva2:armhf (2.4.0-1) ...
Setting up libxfixes3:armhf (1:5.0.3-1) ...
Setting up libopus0:armhf (1.3-1) ...
Setting up libvorbis0a:armhf (1.3.6-2) ...
Setting up libcroco3:armhf (0.6.12-3) ...
Setting up libmxml1:armhf (2.12-2) ...
Setting up libfftw3-double3:armhf (3.3.8-2) ...
Setting up libevent-core-2.1-6:armhf (2.1.8-stable-4) ...
Setting up librubberband2:armhf (1.8.1-7) ...
Setting up libvidstab1.1:armhf (1.1.0-2) ...
Setting up libflite1:armhf (2.1-release-3) ...
Setting up libasyncns0:armhf (0.8-6) ...
Setting up libvdpau1:armhf (1.1.1-10) ...
Setting up libwavpack1:armhf (5.1.0-6+deb10u1) ...
Setting up libbs2b0:armhf (3.1.0+dfsg-2.2) ...
Setting up libtheora0:armhf (1.1.1+dfsg.1-15) ...
Setting up libconfuse-common (3.2.2+dfsg-1) ...
Setting up libopenjp2-7:armhf (2.3.0-2+deb10u2) ...
Setting up libwebsockets8:armhf (2.0.3-3) ...
Setting up libconfuse2:armhf (3.2.2+dfsg-1) ...
Setting up libbluray2:armhf (1:1.1.0-1+deb10u1) ...
Setting up libwebpmux3:armhf (0.6.1-2+deb10u3) ...
Setting up libdrm-common (2.4.100-4+rpi1~bpo10+1) ...
Setting up libzvbi-common (0.2.35-16) ...
Setting up libmp3lame0:armhf (3.100-2+b1) ...
Setting up libvpx5:armhf (1.7.0-3+deb10u3) ...
Setting up libvorbisenc2:armhf (1.3.6-2) ...
Setting up libserd-0-0:armhf (0.28.0~dfsg0-1) ...
Setting up libzvbi0:armhf (0.2.35-16) ...
Setting up libevent-pthreads-2.1-6:armhf (2.1.8-stable-4) ...
Setting up libice6:armhf (2:1.0.9-2) ...
Setting up libxtst6:armhf (2:1.2.3-1) ...
Setting up librsvg2-2:armhf (2.44.10-2.1+rpi1+deb10u3) ...
Setting up libvorbisfile3:armhf (1.3.6-2) ...
Setting up libdrm2:armhf (2.4.100-4+rpi1~bpo10+1) ...
Setting up libva-drm2:armhf (2.4.0-1) ...
Setting up libsord-0-0:armhf (0.16.0~dfsg0-1+b1) ...
Setting up libsratom-0-0:armhf (0.6.0~dfsg0-1) ...
Setting up libsndfile1:armhf (1.0.28-6+deb10u2) ...
Setting up libva-x11-2:armhf (2.4.0-1) ...
Setting up libsm6:armhf (2:1.2.3-1) ...
Setting up liblilv-0-0:armhf (0.24.2~dfsg0-2) ...
Setting up libopenmpt0:armhf (0.4.3-1+deb10u1) ...
Setting up libpulse0:armhf (12.2-4+deb10u1+rpt3) ...
Setting up libavutil56:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up libpostproc55:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up libswscale5:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up shairport-sync (3.2.2-1+b2) ...
Setting up libswresample3:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up libavcodec58:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up libchromaprint1:armhf (1.4.3-3) ...
Setting up libavformat58:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up libavfilter7:armhf (7:4.1.11-0+deb10u1+rpt1) ...
Setting up forked-daapd (26.4+dfsg1-1) ...
Processing triggers for openmediavault (5.6.26-1) ...
Restarting engine daemon ...
Updating file permissions ...
Purging internal cache ...
Processing triggers for libc-bin (2.28-10+rpt2+rpi1+deb10u2) ...
Processing triggers for systemd (241-7~deb10u10) ...
Processing triggers for man-db (2.8.5-2+deb10u1) ...
Processing triggers for shared-mime-info (1.10-1) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...

Display More

sorry that I couldn't get everything into one post due to the max character limitation

UKenGB · Sep 21st 2025

Preparing to upgrade OMV6->7 and as suggested first ran omv-salt stage run deploy which resulted in 2 fails:-

ext4 quota error due to OMV using deprecated external file quotas and not built-in ext4 quotas and about which I opened a thread.

Then there's this one:-

Code

                      ID: load_sysctl_settings
                  Function: cmd.run
                      Name: sysctl --load
                    Result: False
                   Comment: Command "sysctl --load" run
                   Started: 10:45:16.860352
                  Duration: 5.171 ms
                   Changes:   
                            ----------
                            pid:
                                20053
                            retcode:
                                1
                            stderr:
                                systemctl: unrecognized option '--load'
                            stdout:

Display More

This seems to imply that omv-salt stage run deploy is actually issuing an invalid command. Why would it be doing that and how can I prevent it? Can it be edited? Should that command not be run or a different command instead?

marcojump · Sep 29th 2025

Hi, I tried to update from version 5.6 to 6. Attached is the file with the error report.

Code

sudo omv-salt stage run deploy
debian:
----------
          ID: refresh_pillar
    Function: salt.state
      Result: True
     Comment: States ran successfully. Updating debian.
     Started: 19:10:45.040715
    Duration: 1348.464 ms
     Changes:
              debian:
              ----------
                        ID: refresh_grains
                  Function: module.run
                    Result: True
                   Comment: saltutil.refresh_grains: True
                   Started: 19:10:45.376066
                  Duration: 1010.523 ms
                   Changes:
                            ----------
                            saltutil.refresh_grains:
                                True

              Summary for debian
              ------------
              Succeeded: 1 (changed=1)
              Failed:    0
              ------------
              Total states run:     1
              Total run time:   1.011 s
----------
          ID: run_state_deploy
    Function: salt.state
      Result: False
     Comment: Run failed on minions: debian
     Started: 19:10:46.389509
    Duration: 8146.886 ms
     Changes:
              debian:
                  Data failed to compile:
              ----------
                  Cannot extend ID 'start_proftpd_service' in 'base:omv.deploy.proftpd.modules.20mod_wrap'. It is not part of the high state.
              This is likely due to a missing include statement or an incorrectly typed ID.
              Ensure that a state with an ID of 'start_proftpd_service' is available
              in environment 'base' and to SLS 'omv.deploy.proftpd.modules.20mod_wrap'

Summary for debian
------------
Succeeded: 1 (changed=1)
Failed:    1
------------
Total states run:     2
Total run time:   9.495 s
[ERROR   ] {'out': 'highstate', 'ret': {'debian': ["Cannot extend ID 'start_proftpd_service' in 'base:omv.deploy.proftpd.modules.20mod_wrap'. It is not part of the high state.\nThis is likely due to a missing include statement or an incorrectly typed ID.\nEnsure that a state with an ID of 'start_proftpd_service' is available\nin environment 'base' and to SLS 'omv.deploy.proftpd.modules.20mod_wrap'"]}}

Display More

marcojump · Oct 6th 2025

Can anyone help me or tell me which guide to follow?

Thanks

Quote from marcojump

Hi, I tried to update from version 5.6 to 6. Attached is the file with the error report.

Code

sudo omv-salt stage run deploy
debian:
----------
          ID: refresh_pillar
    Function: salt.state
      Result: True
     Comment: States ran successfully. Updating debian.
     Started: 19:10:45.040715
    Duration: 1348.464 ms
     Changes:
              debian:
              ----------
                        ID: refresh_grains
                  Function: module.run
                    Result: True
                   Comment: saltutil.refresh_grains: True
                   Started: 19:10:45.376066
                  Duration: 1010.523 ms
                   Changes:
                            ----------
                            saltutil.refresh_grains:
                                True

              Summary for debian
              ------------
              Succeeded: 1 (changed=1)
              Failed:    0
              ------------
              Total states run:     1
              Total run time:   1.011 s
----------
          ID: run_state_deploy
    Function: salt.state
      Result: False
     Comment: Run failed on minions: debian
     Started: 19:10:46.389509
    Duration: 8146.886 ms
     Changes:
              debian:
                  Data failed to compile:
              ----------
                  Cannot extend ID 'start_proftpd_service' in 'base:omv.deploy.proftpd.modules.20mod_wrap'. It is not part of the high state.
              This is likely due to a missing include statement or an incorrectly typed ID.
              Ensure that a state with an ID of 'start_proftpd_service' is available
              in environment 'base' and to SLS 'omv.deploy.proftpd.modules.20mod_wrap'

Summary for debian
------------
Succeeded: 1 (changed=1)
Failed:    1
------------
Total states run:     2
Total run time:   9.495 s
[ERROR   ] {'out': 'highstate', 'ret': {'debian': ["Cannot extend ID 'start_proftpd_service' in 'base:omv.deploy.proftpd.modules.20mod_wrap'. It is not part of the high state.\nThis is likely due to a missing include statement or an incorrectly typed ID.\nEnsure that a state with an ID of 'start_proftpd_service' is available\nin environment 'base' and to SLS 'omv.deploy.proftpd.modules.20mod_wrap'"]}}

Display More

Participate now!