dlandon

Set it as they recommend. The 50% and below is just a starting point.

I've updated the ownCloud docker and it won't break the older ownCloud versions because of a php incompatibility. There is a new environment variable in the docker template to set the php version. It defaults to 7.2 which is compatible several versions back. Once you've updated ownCloud, I recommend increasing the php version to 7.4 for security reasons.

Add more shm-size to see if it will get going. Add half of your available memory to start and then adjust to get closer to 50% /dev/shm on the Zoneminder console.

Server is offline: Dec 31 00:42:03 Nostromo unassigned.devices: Mounting 'Auto Mount' Remote Shares... Dec 31 00:42:04 Nostromo unassigned.devices: Remote SMB/NFS server '192.168.3.110' is offline and share '192.168.3.110:/volume1/Backup' cannot be mounted. Are you sure the server was online when Unraid was started?

Post diagnostics so I can a look.

Yes, 5G is the fixed size the docker allocates to a mount called /dev/shm when the docker starts. Yes, it comes from the total installed memory. Each system and configuration of cameras will be different for each Zoneminder installation. The 5G I set in the template is just a good starting point.

Zoneminder is a beast. The last time I checked, there were over 5 Million downloads over about 2 years. Whenever I update the docker, it spikes. I'll see how it goes.

When the docker was originally authored, the SHMEM=50% was somewhat arbitrary, but pretty much guaranteed that Zoneminder got enough shared memory. You just now have to tweak it to be sure there is enough. All Zoneminder needs is 50% or below utilization to be sure it has enough.

Well I just ran into the pull rate limit on Zoneminder. I went ahead and signed up for the Pro docker subscription. $60 a year for all my dockers.

Look at the syslog. You'll probably see that it can't be mounted because it is offline. The Synology NAS has to be online before it will mount.

Because of the change in how shared memory is set up, you will need to use the new Zoneminder template:;, Do this procedure: - Remove the docker image. All your data and settings will be kept. - Click on add a container and delete the Zoneminder template. - Go to he apps and get the new template. Read about adjusting shared memory and be sure to increase until you get to less than 50% on the Zoneminder console.

There is an new docker available that is upgraded to Ubuntu 20.04 (for better hardware support), and ES 6.1.0. These changes should resolve some outstanding issues with ES. I've also made a change to how shm is configured. I pushed a new docker xml that has the a different way of setting shm memory. Your existing docker xml will continue to work fine though.

I've added an indicator to UD whenever preclear is running. It will show the format button as 'Preclear' while the script is running, and turn off when the script is finished. You definitely don't want to try any disk operations in UD (like Format) when a disk is preclearing. This will be in the next release.

I just found out that UD is constantly reading unformatted disks looking for a preclear signature. I will disable that check. I can't believe this has been there forever and I never caught it.

No problem.

I have a fix for the file system not showing 'precleared' in UD. I also implemented the temperature display and reads and writes during a preclear. @gfjardim I see the problem with the blinking of the preclear status line in UD. UD does a refresh of the page every 3 seconds. You are updating the status periodically like when UD did not refresh itself. They are clashing. The best bet is to let UD do the page update and preclear just provides the information. Also take a look at the /usr/local/state/devs.ini file in 6.9 RC2. Unraid is providing disk information for Unassigned Devices. I use this for disk spin, reads, writes, and temperature information. I don't query the disk. UD keeps this file current when a hot plug event occurs.

Please mark this as solved.

Unraid does not spin up the drives. There is probably something else.

I do need to point out that the UD disks are now monitored by Unraid just like array disks, so a small amount of reads will occur. Unraid monitors disks for SMART issues and over temperature. You've not seen this before because UD hasn't shown reads and writes until now.

A small amount of reads is normal. Unraid monitors drive status and temperatures on RC2. Any drive over temperature or SMART issue is reported just like array drives.

The tracking of reads and writes on UD disks is the same logic as on the array disks. I also do not see any of this behavior. UD does not do any reading or writing of disks. It only mounts/unmounts them. How fast are the reads incrementing? Spin down the UD disk and see if it is spun back up while being unmounted. On your next post, include diagnostics.

It is not a bug with either Unraid 6.9 or UD. Something is reading from the disk. If you have preclear installed, remove it and see if the reads stop.

It's not a bug. The reads are legit. You've never noticed it before because UD didn't show reads and writes until 6.9 and UD now refreshes those periodically so you can see them change. I suspect that the preclear plugin is monitoring the disk. Remove the preclear plugin and see if the reads stop.

New release of UD: Biggest change is the move from polling to event driven UI updates. This cuts down on excessive polling and improves responsiveness. Several minor cosmetic changes and bug fixes.