Not sure if this is the right place, but I'd like to share my experience with migration from OMV4 to OMV5.
Initially, my migration failed, because of UPS plugin; thx to Ryecoaaron, we have been able to fix that by uninstalling this ups plugin prior to the migration.
Then with OMV5, I faced 2 issues:
#1 erratic reboot of my NAS
#2 remote mount failed to mount automatically after reboot. I have to mount it manually in the GUI, after each reboot
As I had Plex, JDownloader, OwnCloud installed on my NAS with OMV4, I suspected they polluted my system and the migration was not so good, so I decided to do a fresh installation of OMV5.
Thx to that fresh install, issue #2 is fixed: my advise here, as expressed by OMV experts, USE DOCKER As soon as your container is built, it's super easy to run and it does not pollute your base system.
But issue #1 was still there with 2 or 3 reboot per day. In my syslog, I've seen that just before reboot sequence I get systematically the following error:
I'm using extensively NFS in my home network and I've also noticed that my NAS reboots when my Linux client resumes from hybernate and setups the NFS mount.
I've found the following thread in the forum: OMV4->5 residue cleanup blkmapd: open pipe file /run/rpc_pipefs/nfs/blocklayout
It seems others are facing the same issue, but I'm surprised it's not so common as I have a fresh install and it fails systematically.
As advised in this last thread, I've disabled the nfs-blkmap service by renaming it, and after reboot the issue #1 just vanished; my system is completely stable and I don't get anymore this issue in my syslog.
My apologies for this long thread... but I'd like to get feedbacks from expert on this issue, at least to know if I did right and also to warn other users.