Surprisingly Smooth Upgrade 7 -> 8

  • I decided to try upgrading 7 -> 8 today using a cloned copy of my current OMV 7 SSD system disk.


    Although I have not yet to begin looking around OMV 8 much yet, at least all my dockers are running well.


    The only thing I had to do was to solve the 502 gateway not found error on the GUI login screen. Running the fix7to8upgrade script solved that one for me.


    I really like the new login screen artwork. That's me! (inside joke some of you might get) :)


    Thanks to the devs for all the hard work on this.

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


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    good to hear. I have upgraded seven systems now and other than the nut plugin issue, I really didn't have any problems either.

    That's me! (inside joke some of you might get)

    I get it : )

    omv 8.0.8-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.4 | compose 8.1.2 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 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!

    • Official Post

    I really like the new login screen artwork. That's me! (inside joke some of you might get)

    ^^ :thumbup:

  • I can only confirm this. This morning I saw OMV8 was released, so I did upgrade my Beelink ME mini. I had made an image of the boot disk just to be sure. No issues to report.


    I did the upgrade on my vm install with the release candidate to see what would happen last week, that was also a smooth upgrade.

    Beelink ME mini OMV 8, OMV-Backup, OMV-Writecache, OMV-Kernel, OVM-LVM2, OMV-MD, OMV-Nut, OMV-Tftp, OMV-TGT, Zabbly kernel 6.17.x

    OMV 8 in Hyper-V for testing, OMV-Backup, OMV-Writecache, OMV-Kernel, OVM-LVM2, OMV-MD, OMV-Nut, OMV-Tftp, OMV-TGT, Zabbly kernel 6.17.x

  • "Surprisingly smooth" seems a bit rude to votdev and other contributors, as well as all the Debian maintainers. Anyway, my two upgrades also went well. Thanks!

    It's honest, given the difficulties I and others have had with the upgrades.

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


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • only had one niggle, got this email:


    Code
    /etc/cron.daily/openmediavault-mdadm:
    mdadm: DeviceDisappeared event detected on md device /dev/md/md0
    mdadm: NewArray event detected on md device /dev/md0

    turned out mdadm --monitor --scan --oneshot gave the same output. I checked my md array, nothing was wrong with that. After googling I found this workaround:

    edit /etc/udev/rules.d/99-openmediavault-md-raid.rules


    SUBSYSTEM=="block", KERNEL=="md*", ACTION=="add|change", TEST=="md/stripe_cache_size", ATTR{md/stripe_cache_size}="8192", SYMLINK+="md/md0"


    I've added the bold statements and now I don't get DeviceDisappeared event notifications anymore.


    found solution here: https://discourse.ubuntu.com/t…red-newarray-alerts/56076

    more background info here: https://linux.debian.bugs.dist…ssage-every-day-from-cron

    Beelink ME mini OMV 8, OMV-Backup, OMV-Writecache, OMV-Kernel, OVM-LVM2, OMV-MD, OMV-Nut, OMV-Tftp, OMV-TGT, Zabbly kernel 6.17.x

    OMV 8 in Hyper-V for testing, OMV-Backup, OMV-Writecache, OMV-Kernel, OVM-LVM2, OMV-MD, OMV-Nut, OMV-Tftp, OMV-TGT, Zabbly kernel 6.17.x

  • Hy guys. I planned to do my first release upgrade from OMV7 to 8 in 2026, since OMV7 is so stable, but I just couldn't resist doing it today, Boxing Day...

    a.) The system: current OMV-7 on a Raspberry Pi 5 8GB and Raspberry OS-lite with an externally powered SATA enclosure (icybox)

    b.) Backup of all data (using OMV-USB-backup) to an external hard drive.

    c.) Update OMV7 to the latest version with `sudo omv-upgrade`

    d.) Create a backup of the OMV system SD card

    e.) I thought it would be a good idea to connect a monitor and keyboard (I later read that there are no problems with an upgrade via SSH)

    f.) Log in and switch to `su`. Then: `omv-release-upgrade`

    g.) Upgrade running... finishing... manual reboot.

    h.) 8.0.2-2 (Synchrony) is running


    Guys, I want to thank everyone involved. OMV is the best NAS for me (system & support). And I know what I'm talking about, because I previously had a Synology that suddenly stopped receiving updates...


    Was I surprised? not really ;)



    There is one thing left, I "had" this error "Skipping acquire of configured file 'main/binary-armhf/Packages'...."

    A post from ryecoaaron 30.11.25 helped me (again) a lot...


    dpkg allows additional architectures. With the rpi, you can likely remove the second architecture.

    dpkg --print-foreign-architectures

    armhf


    Check to see if you have any armhf packages installed

    dpkg -l | grep armhf


    I had none. So I disabled armhf with:

    sudo dpkg --remove-architecture armhf


    done :)

    OMV7 on Raspberry-OS-Lite (bookworm) aarch64

    OMV8 on Raspberry-OS-Lite (trixie) aarch64

    Edited 5 times, last by seiha011 ().

  • I JUST setup an RPi 4 (4GB variant) with OMV 7 a couple of days ago and it seemed like the perfect candidate to upgrade to 8 since my other hosts are more mission critical. The RPi 4 is using the Wireguard, NUT, and Timeshift plugins along with the phased out FlashMemory.


    Zero issues with the upgrade, took about 10 minutes. Very stable, as advertised. I would highly encourage anyone with RPi 4 to backup their system and proceed with the upgrade if their installation is fairly typical. In my case, I had made a few small changes in Linux but none of them created any problems.


    I'll be upgrading the remaining hosts once I do a few backups. Remarkable turnaround given how recently Debian 13 came out.


    EDIT: I upgraded the other two hosts with zero issues as well. Both are running OMV bare metal on AMD64. One of them has a lot of customization in Linux as well as a number of wacky Docker configurations and I was curious what might happen. But overall a pleasant and uneventful experience.

Participate now!

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