dlandon

I need more information on what you are requesting. Please show more of the UD page. I'm assuming these are individual drives?

The Docker does not install that file. You'll have to download the pushapi_pushover.py and install it at /var/lib/zmeventnotification/bin/pushapi_pushover.py. I'll have to look at updating the Docker to install that file.

Yes.

It looks like the remote server is only accepting SMB1 connections. Please post your issue in the Unassigned Devices forum and post full diagnostics.

I released a new version 2020.06.20 that fully supports 6.9 Multi Language. Those of you on 6.9 Beta will be able to download the language packs and have UD translation installed as it gets translated for each language. @ich777 is working on the German translation.

If you have CIFS mounts (remote mounts) mounted and the remote server goes off-line, there are Linux commands that will hang even when not done on the CIFS mounts. That is why UD has timeouts on all commands. If there weren't time outs, UD would hang. If I remember correctly the worst are 'lsof' and 'df'. If the remote server is only on at certain times of the day, you shoud unmount the remote shares while it is off.

The server hosting your remote shares is going off-line: Jun 19 09:54:12 Tower unassigned.devices: SMB/NFS server '192.168.1.13' is not responding to a ping and appears to be offline. This can cause issues with other UD device commands timing out.

Post your diagnostics.

Yes. But you can use the array keyfile, just not one specific to the disk.

I agree. I would use a sub-folder and not map to /tmp. The docker may change permissions and mess up other folders.

That feature is already there. Look at the UD settings. You can set a per disk password.

UD keeps working copies of it's configuration files in the /tmp file system and copies changes to the flash to cut down on flash reads and improve response time. Your docker probably interferred with the /tmp file system. I'm surpised you didn't have other issues.

The pool feature removes from UD the one thing that always belonged in Unraid itself. The other features of UD are more of what UD was designed to do - mount disks for temporary use i.e. backups, mount remote shares, and ISO images. I can't speak for LT, but there really is no reason now to add UD to Unraid. It just adds complication to Unraid and additonal support issues for LT that keeps them from concentrating on more important things.

I suspect you have a mis-configured docker. Check your mappings, especially to UD devices. If you are passing through a UD device to the docker, be sure to mark it 'Pass Thru' in UD so it does not get mounted. A disk passed through to a docker and mounted with UD will be corrupted.

I just fired up Nvidia 6.8.3 and don't see any problems.

Let me set it up on my test server and see if I can figure it out.

No.

You probably have a corrupted flash drive.

Unraid (Linux) is not recognizing a valid file system on the disk. @johnnie.black may be able to offer some steps to try to determine the problem with the file partition and system.

There is an example for backups in the first post of this forum.

ES (Event Server) is installed but not enabled until you enable it through a configuration setting in ZM. The hook processing requires additional setup through the .ini files in the appdata/Zoneminder folder after you install the docker with the environment variables set for your needs. The nice thing about this docker is that you don't need to get inside the docker image and make changes. All configuration settings are in the appdata/Zoneminder forlder. The cameras don't need any special setup. ZM collects the images from the cameras, creates the event and ES picks up the events and does it's processing.

The first partition does not have a file system. If you could delete that partition, it would be a lot cleaner in UD, or as you mentioned, re-format the drive.

The reason the disk 'Unmount' is grayed is because the first partition is not mounted. The second partition 'Unmount' is grayed out because of a recent change I made that caused that. Update to the latest version of UD and the second partition 'Unmount' will be active. It should look like this: You have to unmount the second partition by clicking on the 'Unmount' button for that partition. This happens when a multi partiton disk does not have all the partitions mounted, especially the first partition because the disk 'Unmount' button status is based on the first partition. There have been several recent changes that have made this happen.

The file name is cron, not cron.cron.

Sorry, I read the pass through switch setting wrong. I see the first partition as unmounted, but it looks like there is a second partition that is mounted. Please show all the partitions on the disk.