Post install upgrade to OMV 8 -> 8.5 (4 updates) fails on RPi4 8GB

I'm performing a clean install of OMV 8 on an RPi4 8GB Trixie with the latest OS updates. Just failed for the third time. I should mention that I had OMV 6 installed previously and running for years. Since there was no clean OS upgrade to Trixie, I backed up my NAS data and am doing a clean install. I hope to reattach the drives, but if not, I'll restore the data.

I get a clean install of OMV 8 (whatever is current on github as of today). When I select the 4 updates (OMV 8.5, etc.) the install runs to a certain point and then connection is lost. I believe it's during the Salt installs that this happens. Upon returning to the OMV UI a dialog for confirming updates is presented. When I confirm to apply updates the wait cursor is presented and eventually I'm presented with the red box system failure message. At this point the server cannot be pinged, even after rebooting. No network connections are available when I logon at the console. To test, I tried pinging cnet.com, which fails. Right now the server is set up on my bench so I do have monitor, keyboard, and mouse.

I could run the base install, but since OMV manages the machine I'm unwilling to do that. I really need to get past this but am out of ideas. FYI, I checked swap space prior to install and it was 2.0 GiB.

Any suggestion would be greatly appreciated.

Thanks chente.

I reimaged the SD card with Trixie for RPi4, updated the OS, and reinstalled the base OMV 8.1.1-1 install. All went well. After seeing your post above I did the upgrades again, and surprise, surprise, it ran to End of Line this time! I confirmed application of changes and got the red box error message again after a very long wait.

Also, my SSH session with the server was unresponsive (interestingly, it wasn't killed, one just could not type at all). Sitting at the server, again, pinging cnet.com failed, and from my workstation http://nas.local could not be reached (DNS address could not be found). Something I didn't mention yesterday; the IPV4 address no longer exists, but there is an IPV6 address. The eth0: endpoint is now end0:. My router has a reservation for a permanent IPV4 address.

So, from the console I ran apt-cache policy salt-minion openmediavault-salt and got:

salt-minion:
  Installed: 3008.1
  Candidate: 3008.1
  Version table:
 *** 3008.1 500
        500 http://packages.openmediavault.org/public synchrony/main arm64 Packages
        100 /var/lib/dpkg/status
openmediavault-salt:
  Installed: 8.1.0
  Candidate: 8.1.0
  Version table:
 *** 8.1.0 500
        500 http://packages.openmediavault.org/public synchrony/main arm64 Packages
        100 /var/lib/dpkg/status

Then I ran apt-cache madison salt-minion and got:

salt-minion |     3008.1 | http://packages.openmediavault.org/public synchrony/main arm64 Packages

At this point the OMV web interface is inaccessable.

I'll wait to hear back before doing anything else.

Cheers!

<chagrin>Oy! That's what I get for following someone else's directions! I didn't RTFM.</chagrin>

I went through the entire process again using the RPi instructions (including the pre-install script) and have success. I did get Connection Lost during the post install upgrade. The updates still showed in the list so I ran them again and it took only a second and noted that all updates were applied, so no changes were made on the second pass. I applied the changes successfully and am now at 8.5.6-1.

Thank you very much!

One note: in the Pi install instructions, a header reference an OMV7 install, but the scripts installed OMV8.

On to configuration!

Cheers!

Configuration is all done and I was able to reconnect to all my storage and recreate the shares.

Thanks for all the help! This is resolved.