I recently setup my second UNRAID-Server since i really did like experience with the first one.
This new instance is ment to replayce my old Debian Server running some LinuxRaid fileshares and my Docker Containers.
So far so good.
Most of the applications are running without problems and even the data "migration" was as painless as it could get (copy folder and run the container.)
Except for my Owncloud Setup.
I use Portainer for creating all my containers and for the owncloud Setup i used the docker-compose provided via the official documentation: Installing with Docker :: ownCloud Documentation
except for the volumes beeing just host-mounts to /mnt/user/appdata/owncloud
The installation was working somewhat okay after the migration to UNRAID.
To be precice the Desktop app as well as the mobile apps for Android and IOS were working well and all the data is still available.
But when i start to browse pictures via the WebUI after some seconds the App locks up and won't respond anymore.
Any other file types seem to work fine.
The UNRAID WebUI is still accessible but you can see in the "Array Devices" that there is no activity on the drives at all anymore.
In the Syslog is no log message at all but when trying to do any fs actions (ls or lsof for example) within /mnt/ they simply won't return.
When trying to restart the system is see the following logs in the syslog:
Feb 3 20:26:11 Thor shutdown[18556]: shutting down for system reboot
Feb 3 20:26:11 Thor init: Switching to runlevel: 6
Feb 3 20:26:11 Thor init: Trying to re-exec init
Feb 3 20:26:29 Thor monitor: Stop running nchan processes
Feb 3 20:29:13 Thor root: Status of all loop devices
Feb 3 20:29:13 Thor root: /dev/loop1: [2049]:12 (/boot/bzfirmware)
Feb 3 20:29:13 Thor root: /dev/loop2: [2305]:2147483777 (/mnt/disk1/system/docker/docker.img)
Feb 3 20:29:13 Thor root: /dev/loop0: [2049]:10 (/boot/bzmodules)
Feb 3 20:29:13 Thor root: /dev/loop3: [2305]:6442451073 (/mnt/disk1/system/libvirt/libvirt.img)
Feb 3 20:29:13 Thor root: Active pids left on /mnt/*
i tried to stop all docker containers in order to stop everything but i cant stop any of them with the following message:
Error response from daemon: cannot stop container: Portainer: tried to kill container, but did not receive an exit event
Restarting works by issuing a secont `reboot` from within a ssh session.
But then again after the reboot the server complains about a unclean shutdown and starts a parity check.
I have no clue what could cause this issue since the same setup worked well on my Debian system.
I hope maybe one of you encountered a similar problem or has any ideas as of what i can try resolving the Problem.
Thank you for your help
Best Regards