dlandon

I'm using Brave (also based on Chromium) and don't see the issue in incognito mode. Do a few things and see if there are errors/warnings when this happens: Click on Tools->PHP Settings and see if there are any log entries. While on the UD Device Settings page hold down Ctrl-Shift keys and press 'J'. This will show the Java console. See if there are any errors there.

What browser are you using?

UD creates those mount points: disks - used for mounted UD disk devices. remotes - used for mounted UD remote shares. addons - used to mount user mounted devices so FCP will not flag the mount as eroneous. rootshare - used for rootshare mounts. Why are these there if I don't use them you might ask? Those mountpoints are mounted themselves with a max size limit so misconfigured Docker Containers and VMs don't crash Unraid by writing lots of data to that mount point (tmp file system) instead of the actual device. /mnt/ is in the tmp file system and doesn't have a lot of room for eroneous data.

Yes, when the remote share has issues, I've tried to set up UD to cleanly unmount and remount the remote share so it will not hang. That's generally from a name resolution issue. Is your remote server on a static IP address? You might try using the IP address of the remote server but it needs to be static. I have put a lot of time on sorting out name resolution issues and changing IP addresses when the server is not on a static IP address. It is pretty hard to test and it may be missing a server IP address change.

I'm sure the drives have unique numbers, but the dock is not reporting them that way as udev sees one serial number for three drives. It's not UD that is duplicating the serial numbers. It's udev. There are others here that have more experience than i do.

It appears you are mounting a remote server share manually: Apr 7 13:03:36 apollo sudo: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/sbin/mount -t nfs4 -o proto=tcp,port=2049 100.69.1.200:/export/users /mnt Use UD to mount it.

Your USB dock is reporting three of the drives as the same serial number. That's why you see only one Hitachi disk. The other two, I don't understand why they are not showing. Unraid and UD require unique serial numbers to be recognized properly.

Post diagnostics. It'll help me understand your issue better.

Can't tell you how many times I've done things like that. No worries.

No. Each entry in the exports file has a unique fsid. What is the client trying to connect to Unraid?

A couple ideas for you to look at: UD uses this as the rule to mount another NFS share on another Unraid server: "*(rw,sec=sys,insecure,anongid=100,anonuid=99,no_root_squash,lock)". UD uses this command to mount a remote NFS share: "/sbin/mount -t 'nfs' -o rw,soft,relatime,retrans=4,timeo=300 'MEDIASERVER:/mnt/user/Public' '/mnt/remotes/MEDIASERVER_Public'" If you use "-t 'nfs'", nfs will negotiate the version to use, starting with v4.. This is the setup of an Unraid NFS share set to "Public": "/mnt/user/Public" -fsid=106,async,no_subtree_check *(rw,sec=sys,insecure,anongid=100,anonuid=99,all_squash)" These may give you some help in solving your issues.

03.03.2024 is the latest. The 04.01.2024 is UD+. It is working for me. Post your diagnostics so I can take a look.

The fix was already implemented. You just have to have the latest version of UD or Unraid. It only affects saving the scripts after editing them. It doesn't have anything to do with execution of the script when a device is connected. Just turn on the "Automount" switch and the script will run when the devkice is connected. Also, be sure to use the default script (click the "Default" button) and modifty it to your needs.

I'll concentrate on network issues first: You have IPV6 enabled. Do you need it? If not turn it off. I see multiple vlans. Be sure they are configured properly for your situation. Turn off NetBIOS. Use a static IP address on your server. It's set right now for DHCP. Verify network settings on your PCs. Add a second NIC and set it up with a bonding mode to spread the load over both NICs. Other factors: Upgrade to 6.12.10. Remove un-get and NerdTools plugins then reboot. Make sure no packages will install after reboot. Do this before upgrading to 6.12.10. There may be some package interference.

Give me some time to review.

Start by posting your diagnostics.

On the UI, click on the 'Boot' device label and then the "Syslinux Configuration" tab. Romove any instances of this text "root=sda" you see, save it, and then reboot. You should be able to preclear without memory issues.

Start with a fresh diagnostics.

Post diagnostics.

It's not a design issue; it's a technical limitation. The Root Share is mounted as bind mount and exclusive shares are not available because the bind mount does not allow symlinks.

This issue is in 6.12.9, but there was a change made that will be in 6.12.8 to enable client negotiation of 4.X. Boot in 6.12.8 and see if this helps your situation.

I think you are running into an issue with 6.12.9 where a changed setting in nfsmounts is causing problems. It is to be solved in 6.12.10 due out soon.

Who is the client? From the client that I assumed was Unraid.

We need more information to be able to help. Post diagnostics.

When i click on it, it sits on the Unraid wave and appears to be hung.