dlandon

Try restarting the Docker. I don't understand the server name issue. Where do you see this?

Why do you stop and then restart the dockers?

The encrypted disk feature of UD is only there to support mounting a disk from the array. Mounting encrypted disks from other computers is not supported at this time and future support will be a decision LT will have to make and implement in UD once they merge it into unRAID. I have been asked by LT to not support encrypted drives other than array drives because of the possible loss of data access from a user not having the correct passphrase for the drive. The encrypted disk support in UD is limited to disks formatted by unRAID and use the array passphrase.

Look on the flash drive in the /logs/ folder.

UD handles all that for you. It works. I use it in my scripts.

UD passes in the device as an environment variable.

Load the default script then look at the comments in the script. There is an environment variable that will give you the information you need.

These log entries indicate a hardware problem and have nothing to do with the format of the drive. Post your diagnostics for further help.

Why do you think Zoneminder is using up all the memory? Post diagnostics.

You have to be more specific on what didn't work. Verify that the 'cron' file was loaded properly. You can check if your 'cron' file is being loaded by getting into the Zoneminder command line: docker exec -it Zoneminder bash Then type the following command: crontab -l You should see your cron entries. If not, troubleshoot the 'cron' file name and placement. Be sure you are using a Linux type editor to create the 'cron' file. If the 'cron file is loaded properly but still not doing what you want, check that you have created the events properly. You can test that on the command line of the docker: /usr/bin/zmpkg.pl Daytime This will put Zoneminder in the Daytime mode of operation. /usr/bin/zmpkg.pl Nightime This will put Zoneminder in the Nightime mode of operation. You'll have to consult the Zoneminder documentation on configuring these different modes.

Surprise, read it again. Wrong file name.

Mount the disk and the sizes of the partitions will show.

The first posting of this thread.

For those of you having issues with ownCloud, please note the support links I provided in the original post. I have provided a Docker that packages the ownCloud application in an easy to install Docker with MariaDB in the Docker so getting it running takes minimal effort. I can and will support the Docker implementation of ownCloud, but I can't offer support on ownCloud or the ownCloud apps. Please take your ownCloud issues to the ownCloud support forum. To get the fastest response, please refrain from posting any issues in multiple threads on the forum.

Not at this time. UD can only mount one from the array.

I would suggest you take your issue to the owncloud forum. That's not a container issue.

10.0.7 is the latest stable version. The oauth2 addon works fine for me. When you see the login, you need to sign in so the client has access. This is the way it works.

Take a look at the admin documentation on uploading large files.

Seems to be working nicely. Hopefully @bonienl can make it official. @bonienl let me know if you meed any help.

Your shutdown occurred within a few minutes. It doesn't seem like the timers worked at all. Double check the settings. Your shutdown timer is set to 60 seconds. Your VM timer is set to 60 seconds.

No. You have two timers running at the same time. The VM shutdown timer needs to be shorter than the shutdown timer so the VMs have a chance to time out. If the VM timer runs out, the VMs are forced to shut down. VM timer =======================> VMs are forced to shut down if the timer runs out Shutdown Timer ========================================================> Unraid is forced to shutdown if the timer runs out

Disks formatted XFS are mounted with "noatime" and "nodiratime".

That is probably happening because you are stressing the server. Check to see what the cpu usage is when Zoneminder is running. You may see that the cpu utilization is running at 100%.

Read your log: Apr 18 19:17:00 Tower unassigned.devices: Adding disk '/dev/sdk1'... Apr 18 19:17:00 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdk1' '/mnt/disks/Network_Storage_HDD' Apr 18 19:17:01 Tower ntfs-3g[27708]: Version 2017.3.23 integrated FUSE 27 Apr 18 19:17:01 Tower ntfs-3g[27708]: Mounted /dev/sdk1 (Read-Only, label "Network Storage HDD", NTFS 3.1) Apr 18 19:17:01 Tower ntfs-3g[27708]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Apr 18 19:17:01 Tower ntfs-3g[27708]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sdk1,blkdev,blksize=4096 Apr 18 19:17:01 Tower ntfs-3g[27708]: Global ownership and permissions enforced, configuration type 1 Apr 18 19:17:01 Tower unassigned.devices: Mount error: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) The last line indicates the problem.

Use CA (Community Applications) to find and install the Zoneminder Docker.