dlandon

When the server is shutdown, a copy of the disgnostics is saved on the flash at /flash/logs/. Please post that. I need the shutdown sequence.

Give me the output of this command: timeout -s 5 1 bash -c "(echo >/dev/tcp/IP/2049)" change IP to the server IP address.

The "List Shares" for NFS shares uses showmount to list the NFS shares found on the server. That's why it finds them. The server status (online) has changed from being a ping on the server to a check if the port is open. Your server needs to use the standard port (2049) for NFS. Check that your server is using that port. The reason you're just now seeing this is you probably updated UD and the OS at the same time. This changed occurred in UD some time ago.

UD does a sync on the mount point before forcing the unmount. It has a timeout of 10 seconds. It that command times out, the remote share is force unmounted. I suspect a race condition of some sort. Post diagnostics so I can have a closer look.

That's the problem. UD needs to go ahead and unmount the share even if the server goes offline. I'll research and see if I need to apply a fix.

So that is a Docker?

I would remove and readd the remote shares and verify that UD can see the server (Search For Servers) and the NFS share (Load Shares). Use the server name UD finds and don't enter the IP address.

Someone post diagnostics when this occurs so I can investigate further.

They should be taken care of on a shutdown. Post a diagnostics.

Is this mount there at /mnt/LongTerm?

You have cache dirs installed. Eirher remove it, or set it up to include only shares you want it to work on. It has a bad habit of caching all shares including UD shares and causes problems like this.

This means the rootshare can be mounted and should be available to mount on an Unraid server. Some more things to try: Try a simpler password on the administrator account. Letters and numbers only. You have multiple IP addresses listed in the testparm output. This is where Samba is listening: interfaces = 192.168.0.6 192.XXX.XXX.6 127.0.0.1 100.XXX.XXX.115 fd7a:115c:a1e0::27a:ae73 Is the server visible on one of these interfaces? You have tailscale installed. Confirm it is set up properly. Can you see the individual shares and can those be mounted? You have a huge amount of plugins installed. One may be interferring. Boot your server in safe mode and try mounting the root share.

Did you turn on the share switch for the rootshare in device settings? It won't be shared unless you turn it on.

No, that is not your problem. Possible reasons for this error could include: Incorrect credentials (username/password) provided for accessing the CIFS share. Insufficient permissions to access the CIFS share from the system where the error occurred. Network connectivity issues preventing access to the CIFS share. Misconfiguration of the mount command or options used for mounting the CIFS share. I don't think 2 or 3 apply because UD shows the remote share as being online and available. 4 is not an issue. That leaves 1 - credentials. Several things to look for: Use UD to search the server and select the correct server from the drop down. Don't enter the IP address. Let UD search for the remote server shares after entering the credentials in UD. If UD does not list the shares, the credentials are an issue, Watch out for special characters. They can cause php issues. Choose the share from the drop down. Don't enter it. You can't use the 'root' user credentials. You are probably overthinking this issue. Let UD work out the details for you. Let it find the server and the share for you and use what it finds.

You can delay automount of remote shares by a setting in UD settings.

No, it only tries once.

It should, but start up can present some timing issues based on the order things starting. You might have to delay the starting of the VM to be sure the UD remnote share has had enough time to mount.

That sounds like USB issues - cables and connectors. You will see "Reboot" if the device is removed without being unmounted properly, or if the USB drive drops ofline.

No, but looking into it.

You have the cache dirs plugin installed. Be sure you set it to include only the shares you want it to operate on. If you don't set up include shares, it will cache all shares including UD and cause issues like this.

It works, I can do it. Post diagnostics.

If you reboot the server, that paused status gets lost, but you can still resume a preclear from where it left off on a particular disk.

Post diagnostics for further help with this. That status is lost once the server is rebooted because it is in RAM, but the drives are still precleared.

If you stop the array, UD will pause preclear on the drives being precleared and they can be continued once the array is restarted. Click on the play arrow on the UD Preclear GUI page and the paused preclears will restart.

Please answer this question previously asked. Can you ping the Unraid server when connected to WiFi or LAN and the mount fails?