dlandon

Only NFSv3 is supported on your remote server. Go to the UD Settings and set the "NFS Version to use when Mounting Remote Shares:" to "Auto" so NFSv3 qwill be used.

Please retest this with 6.12.14.

Some work was done on this issue and it should be resolved.

When you updated Unraid, UD was also updated. There have been changes in UD that do wome additional checking for remote shares to be on line and ready to mount NFS shares. Go to Settings->Unassigned Devices and then click on the 'Remote Servers' and enter your server name or IP address and click "Test". You will then see the results of UD testing the remote server. If you need further assistance, post the results from the remote server test.

The inotify user watches are now adjusted if there aren't enough when the plugin is started. This is in the latest release. This should stop the inotify start failure when there aren't enough user watches.

I don't know what they changed, but it was an easy fix.

You can eliminate the cache and pool disks from the file activity, or install the Tips and Tweaks plugin and increase the inotify watches.

That is a browser problem that does not show the dropwown correctly we are seeing with Chrome and Brave. Try a different browser. This will be fixed in the next release of Unraid. The blank in the first screen shot next to 'clash' means it is available. The 'Not Available' in the second screen shot means if has gone off-line.

There is currently no way to do that.

I can add the 'docker' share.

The plugin automatically ignores appdata, syslogs, and system.

The idea is to track file activity. It works in the background, not just when the UI is active. It's best for troubleshooting file activity issues. If you don't want the CPU spikes, turn it off. It isn't really intended to leave on all the time.

It works fine for me, and no one else is reporting this. I suspect an issue with your system. Try it again after a reboot.

There is no way currently to do that. I will consider this. I assume you only want to look at certain shares or disks?

If I understand what you are wanting to do, enter 'SOME_GROUPING/disk-001' as the SMB share.

I like simple answers like that.

You are using Jumbo frames: Nov 21 16:00:18 Cube root: Fix Common Problems: Warning: Jumbo Frames detected on eth0 ** Ignored Nov 21 16:00:18 Cube root: Fix Common Problems: Warning: Jumbo Frames detected on eth6 ** Ignored We do not recommend that because it is a challenge to get it set up correctly on your network. It really doesn't do anything to improve your network throughput these days because the NIC cards are much better at handling LAN traffic, and it causes issues when not done correctly. Set all your NIC cards back to the default mtu.

I'll put it in my feature list and see if it makes sense for the wider user base.

Unraid and UD only mount disks with partitions. The not 'Partition' means that the disk does not have a partition. Can you format the virtual disk with a partition?

This error message is coming from your remote server: Nov 21 16:32:10 Unraid unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,hard,relatime '10.10.10.6:/export/Cold_backups' '/mnt/remotes/10.10.10.6_Cold_backups' Nov 21 16:32:10 Unraid unassigned.devices: NFS mount failed: 'mount.nfs: mounting 10.10.10.6:/export/Cold_backups failed, reason given by server: No such file or directory'. The "No such file or directory' is coming from the remote server. I don't see anything that UD is doing to cause this reply from the server. Try this mount command at the command line: mkdir /mnt/remotes/10.10.10.6_Cold_backups /sbin/mount -t 'nfs4' -o rw,hard,relatime '10.10.10.6:/export/Cold_backups' '/mnt/remotes/10.10.10.6_Cold_backups' Then try: /sbin/mount -o rw,hard,relatime '10.10.10.6:/export/Cold_backups' '/mnt/remotes/10.10.10.6_Cold_backups' Show the output of the 'mount' command if it mounts.

The 'cache=strict' is the best option for performance and consistency If you do a 'sync -f {mountpoint}' when checking for the files on Unraid, this invalidates the cache and the files will then be made current. Adding a cache setting will only complicate UD for a corner use case.

Go to Settings->Unassigned Devices and enable the destructive mode. Then go to the UD page and click on the red 'X' on that drive and the partition will be removed. Then you can format the drive.

It looks like the credentials failed. Add the remote share back and confirm the credentials.

Several things to look at: The remote share is at 'OMV.LOCAL/export/Cold_backups'. Confirm this is the actual mount point on the OMV server. Log in to the NFS server and check the permissions of the /export/Cold_backups directory. Check the remote server (OMV) logs. Go to the Settings->Unassigned Devices anc click on the 'Remote Servers' tab and enter the OMV.LOCAL server name, then click the 'Test' button. Look in the results and be sure your Unraid server has access to the /export/Cold_backup share. Also verify the NFS versions that are supported. Post the results if you continue to have issues.

Post ud_diagnostics by going to a command line and entering 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip.