OMV failed after update : solved

  • Hi.


    I'm running OMV 7. Server was swiched off for two weeks as I was away. On my return yesterday, booted up the OMV server and let it install updates, then it crashed.


    Now the OMV web GUI is not available, nor are any of the disks / volumes visible over the network. I can SSH in as root though.


    Any suggestions how best to proceed appreciated.


    Thanks.


    Update. 2 of the 3 networked Volumes are accessible. The Web page GUI just shows "Loading...."


    Problem solved.


    Finally able to connect to the dashboard, wouln't allow access until about 20 minutes after boot up.


    One of the Volumes in Dashboard > Storage > File System : showed "online" and with a valid mount point, but no data on file system (size / space available etc..). Selecting the Volume and then selecting "show details" (triangle symbol) resulted in Timeout.


    So using SSH I ran fstab command to rebuild the mount configuration table.


    All working fine now.

    Code
    sudo omv-salt deploy run fstab 
  • stephengrenfell

    Changed the title of the thread from “OMV failed after update” to “OMV failed after update : solved”.
    • Official Post

    OMV7 is EOL by the way.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    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!

  • ryecoaaron

    Added the Label resolved
  • ryecoaaron

    Added the Label OMV 7.x
  • OMV7 is EOL by the way.

    True.


    Whats the best method to do the upgrade to OMV 8 ?.


    If I follow the upgrade guide here OMV7 to OMV8 upgrade guide


    When I run: omv-release-upgrade using SSH as root then I get an error


    Code
    root@Debian-x79:~#  omv-release-upgrade
    This system is running a desktop environment! This setup is not supported.


    OMV Version 7.7.24-7 (Sandworm) Kernel Linux 6.2.16-20-pve


    Should I follow the steps suggested here : Install OMV8 on Debian 13 (Trixie)


    Thanks

    • Official Post

    This system is running a desktop environment!

    Make sure all of these packages are not installed - gdm3, sddm, lxdm, xdm, lightdm, slim, wdm apt-get purge will remove them. The run the upgrade again.


    The fact that you have a desktop environment installed is bad (servers should not have a gui installed) and uninstalling those packages might break something you are used to using.

    Should I follow the steps suggested here : Install OMV8 on Debian 13 (Trixie)

    Nope. That is to install OMV not upgrade it.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    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!

  • Make sure all of these packages are not installed - gdm3, sddm, lxdm, xdm, lightdm, slim, wdm apt-get purge will remove them. The run the upgrade again.


    The fact that you have a desktop environment installed is bad (servers should not have a gui installed) and uninstalling those packages might break something you are used to using.

    Nope. That is to install OMV not upgrade it.

    I should have mentioned, that there is no desktop environment - the video card interface (Display Port) only has command line output, but it is connected to a display. The OMV installation was not installed on top of a version of Debian.


    Should I run just apt-get purge packagename for each of the packages you listed ?, Or also apt-get autoremove , Or aptitude remove packagename ?.

    Thanks.

    • Official Post

    that there is no desktop environment

    One may not start automatically but the fact OMV isn't upgrading means one is installed.

    Should I run just apt-get purge packagename for each of the packages you listed ?, Or also apt-get autoremove , Or aptitude remove packagename ?.

    sudo apt-get purge gdm3 sddm lxdm xdm lightdm slim wdm

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    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!

  • One may not start automatically but the fact OMV isn't upgrading means one is installed.

    sudo apt-get purge gdm3 sddm lxdm xdm lightdm slim wdm

    OK so it seems gdm3 was installed.



    I then followed the upgrade guide.


    However after following all the steps there is a "Pending Configuration Changes" message. When I try to apply the "Pending Configuration Changes" there is an "500 internal server error". see attachement.


    The list of "Pending Configuration Changes" are :


    Pending configuration changes You must apply these changes in order for them to take effect. The following modules will be updated:

    • apt
    • apticron
    • avahi
    • compose
    • cpupower
    • cterm
    • issue
    • monit
    • nginx
    • nut
    • phpfpm
    • proftpd
    • samba
    • smartmontools
    • ssh
    • systemd-journald
    • systemd-networkd


    Also there are two file system volumes that are no longer visible. Status "Missing". See attached image.


    Any ideas ?.

  • I tried running omv-aptclean repos


    As mentioned here RE: OpenPGP signature verification failed


    However at step 10 : There is stil an error


    Code
    W: OpenPGP signature verification failed: https://packages.sury.org/php bookworm InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 15058500A0235D97F5D10063B188E2B695BD4743 is bad:            The primary key is not live   because: Expired on 2026-02-04T10:25:46Z

    Full output of omv-aptclean repos attached

    • Official Post

    However at step 10 : There is stil an error

    That is a repo you added. You will have to fix it. Looks like you installed a different version of php which is not supported and probably breaking lots of things. I recommend working with chatgpt or something to fix this mess. But this is why you shouldn't change core omv components like php (omv's engine is php and requires a very specific version).

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    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!

  • That is a repo you added. You will have to fix it. Looks like you installed a different version of php which is not supported and probably breaking lots of things. I recommend working with chatgpt or something to fix this mess. But this is why you shouldn't change core omv components like php (omv's engine is php and requires a very specific version).

    I don't know how that version of php got there.


    However in the result from the omv-release-upgrade I see this below, so maybe I've installed something in Docker that pulled in that version of php, I don't know.


    Code
    ----------
              ID: docker_install_packages
        Function: pkg.installed
          Result: False
         Comment: An error was encountered while installing package(s): W: OpenPGP signature verification failed: https://packages.sury.org/php bookworm InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 15058500A0235D97F5D10063B188E2B695BD4743 is bad:            The primary key is not live   because: Expired on 2026-02-04T10:25:46Z
                  E: The repository 'https://packages.sury.org/php bookworm InRelease' is not signed.
         Started: 19:08:34.502306
        Duration: 5348.065 ms
         Changes:   


    As you suggested I used chatGPT and it was solved relatively quicky.


    Thanks for your help anyway.

    • Official Post

    so maybe I've installed something in Docker that pulled in that version of php,

    Nope. Nothing docker would need to add an external php repo to the host system.


    Glad you got it fixed.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    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!

Participate now!

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