dlandon

You need to review your shutdown timers. You have the disk shutdown time out and the VM shutdown time out both set to 60 seconds. That's generally not enough time for Unraid to shutdown. Read this post and see if you need to make any changes. You are giving me snipets of logs that have little to no value. Run your system until you have problems. Then reboot and let Unraid time out on shutdown. Don't force a shutdown. Then post the diagnostics that Unraid collects at /flash/logs/. If the diagnostics aren't collected, then post your syslog server log for the server. Give me the full log, not just the last few entries.

Setup the syslog server on your Unraid server to capture the log. You can then post the log after a reboot so I can see what it shows when the situation happens.

I have several remote mounted shares using a VPN and I don't have this issue. Post diagnostics before the system hangs so I can look at your setup.

Post diagnostics.

I've seen this issue when I backup shares from my main server to a backup server using robocopy. If I exclude the .Recycle.Bin folders, it doesn't seem to happen. I have been unable to determine how/why this happens.

Click on the help button while on the UD page and you will find the answer.

That’s how it should work. SMB should work the same.

Go to a command line and type this command and post the output: /usr/bin/timeout 1 /bin/df

I have spent a lot of time on the UD plugin to keep it from appearing to 'hang'. The issue comes from some commands UD uses to get the mounted devices information. Remote mounted devices using CIFS mounts are particularly messy because of the 'df' command used to get remote mounted devices information and the way servers going off-line are handled. I've set timeouts on all commands that I can to keep UD from hanging, but there may be more that needs to be done. I can't reproduce the problem with the setup I have, so it is very difficult to fix the issues you are seeing because it is probably related to your particular setup. You can't unmount a remote mounted share when it goes off-line because CIFS reports the mount as busy. Unless UD does a forced unmount, the device won't unmount. It is not a good idea for UD to do a forced unmount, because the device could actually be busy. My suggestion is to unmount any remote mounted shares before you take the remote server off-line. Also, any of you having any issues with UD, please remove the preclear plugin and reboot your server. The preclear plugin is partially integrated with UD (that's why you can see preclear information in UD), and there is a background preclear task that collects device information that may have some issues. I don't have the time or desire to troubleshoot preclear. There has been a lot of discussion about the need to preclear disks. It really isn't necessary and the preclearing has been a source of problems. I know all you preclear fanatics will want to start a debate about it, but for troubleshooting these issues, please get it out of the way. Post your diagnostics from normal operation.

You need to post this as an feature request. The UD plugin doesn't have any control over the dashboard page.

UD uses the 'df' command to get the mounted devices size information. 'df' has a nasty habit of hanging indefinitely if a device is off-line. Because of all the issues with 'hangs' on remote mounted devices, I have set a timeout of 1 second on the 'df' command. After 1 second, the 'df' command fails and the size is set to 0B. It may be that the timeout is too short. I have to balance the timeout to be long enough to get the information in normal operation vs. having UD appear to hang when the 'df' command is taking too long. Post your diagnostics.

Remove the preclear plugin: Jun 27 01:03:27 Twins rc.diskinfo[5826]: SIGHUP received, forcing refresh of disks info. Jun 27 01:03:29 Twins rc.diskinfo[5826]: SIGHUP received, forcing refresh of disks info. Disk controller/cable problem? Jun 27 10:00:02 Twins kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen Jun 27 10:00:02 Twins kernel: ata2.00: irq_stat 0x00400040, connection status changed Jun 27 10:00:02 Twins kernel: ata2: SError: { PHYRdyChg DevExch } Jun 27 10:00:02 Twins kernel: ata2.00: failed command: WRITE DMA EXT Jun 27 10:00:02 Twins kernel: ata2.00: cmd 35/00:08:68:76:38/00:00:3a:00:00/e0 tag 16 dma 4096 out Jun 27 10:00:02 Twins kernel: res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) Jun 27 10:00:02 Twins kernel: ata2.00: status: { DRDY } Jun 27 10:00:02 Twins kernel: ata2: hard resetting link Jun 27 10:00:12 Twins kernel: ata2: softreset failed (1st FIS failed) Jun 27 10:00:12 Twins kernel: ata2: hard resetting link Jun 27 10:00:13 Twins kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 27 10:00:13 Twins kernel: ata2.00: configured for UDMA/133 Jun 27 10:00:13 Twins kernel: ata2: EH complete Work on keeping the remote server on-line: Jun 27 07:30:04 Twins kernel: CIFS VFS: Server Brahms1 has not responded in 120 seconds. Reconnecting... This may be a remote server or network problem.

Post your diagnostics when this happens.

No.

How are you using the drive as a VM? If you're not using the extra partitions, delete them.

Why is this so much of a concern? Just ignore the partitions you aren't interested in.

The Zoneminder docker is unable to update the OS. It might be a temporary issue with the update servers.

Auto mount applies to the disk and not individual partitions.

The best way to handle this is to create a User Script that will run this at Unraid startup.

Remove the spaces. "appdata,system,AppDataBackup,Downloads"

The time zone is set from your Unraid server when the docker is started. What time do you see that is off?

Movies-A has an unclean file system and is being mounted read only because of that. Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Mounted /dev/sdm2 (Read-Only, label "Movies-A", NTFS 3.1) Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sdm2,blkdev,blksize=4096 Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Global ownership and permissions enforced, configuration type 1 Jun 1 15:49:46 AnimNAS 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.) You need to fix that before the file system will be mounted r/w.

Hibernated means that it was hibernated from a Windows computer and the file system is in a hibernated state. It doesn't mean the disk is hibernated in Unraid. UD logs to the system log. You probably can't unmount the drive because it is busy. You may have created some additional issues by messing around with the NTFS driver package. Don't do anything with the NTFS driver package. It is built into Unraid and UD mounts NTFS disks r/w except as I said in certain cases where it is not safe to mount it r/w. Your syslog will show the status of mounting the disk file system and why it is mounted read only. Start by posting your diagnostics so we can help you. Tools->DIagnostics. Don't do any other messing around until we can see where you are.

UD already does this. Take a look at the log. A disk with the NTFS file system will be mounted read only under certain conditions - like the disk is hibernated.

The size information showing as 0B is because it is taking too long and UD eventually gives up trying to determine the size so the UI is not totally frozen. It sounds like a network issue. It would help if you could post diagnostics for us to look at.