After running OMV4 since years, it was time for me to migrate to OMV5 and implement Docker for Plex, Jdownloader and Duplicati.
I started with an upgrade from OMV4 to OMV5, but I was facing many unstabilities, so I did a fresh install last week end.
My configuration is the following: 1 system disk + 1 RAID5 volume (4 disks 2TB). I've installed Docker with the 3 containers for Plex, duplicati, jdownloader. I'm using the plugins backup and RemoteMount (NFS mount of Synology array to store rsnapshot images of my RAID5 volume).
I'm using extensively NFS shares with my RAID5 volume; they are mounted by Ubuntu 18.04 clients on my internal network.
I emphasize that (except Docker) I had exactly the same configuration with OMV4 and it was very stable.
Since I moved to OMV5, my NAS reboots regularly (2-3 times a day) and I've found out that it happens when my Ubuntu clients resumes from hybernate or restart; they are mounting the NFS shares and it causes the NAS to reboot.
1/ Looking at the syslog, I've found out that there is an error message caused by blkmapd service, juste when my ubuntu clients tries to mount the NFS shares:
then it seems there are tentative to recover the system and finally system reboots. You have the syslog extract with few comments in file syslog20200725.txt.
2/ I decided to get rid of blkmapd service (the thread OMV4->5 residue cleanup blkmapd: open pipe file /run/rpc_pipefs/nfs/blocklayout relates about this issue and seems to say that this service is not required).
Since then, I do not get any error message in the syslog, my system just reboots few minutes after my ubuntu client tries to mount (unsuccessfully) the NFS shares.
You will find the syslog with my comments in file syslog20200726.txt.
Honestly, I'm completely stuck as I don't find any error or issue in the logs.
I wish someone can guide shortly to identify the root cause of this issue, as I need to rely my NAS for all my personal data.
Thx in advance for your support.