I'm running OMV 7.5.0-1 on Armbian 24.11.1 on a Radxa Rock Pi 4A. Like so many others, I fell prey to the loss of network access after the update to OMV 7.5, but being a hoarder of computer equipment -- and existing in the same physical space as my device, unlike some unfortunate souls -- I was able to connect a monitor and keyboard, run omv-firstaid, and get back in business. That's not what this post is about, though.
Another automated update occurred shortly after the one above, including the following items: armbian-firmware, base-files, linux-dtb-current-rockchip64, linux-headers-current-rockchip64, linux-image-current-rockchip64. When I rebooted the system as instructed, the device would no longer boot to completion.
I have since disassembled my NAS, which required disconnecting the drive array (4 SSDs in a RAID 5 configuration), and now my device will boot again (though I have no HOME partition, since that's located on the array). This leads me to believe that OMV is no longer able to mount the drive array, and that this is preventing the boot process from continuing.
Can someone with the relevant knowledge suggest to me what the best course of action would be to solve this issue? I have a high level of comfort with Linux, but physical devices have never been my strong suit.
Thanks!
Matt