dlandon

New rrelease of UD. A tab is added to the UD Settings page to test for a Remote Server being considered 'online' for UD remote mounts. Go to the UD Settings page and click on the "Remote Servers" tab. You'll enter a server name or IP address and UD will test whether that server is considered online for remote share mounting. Several users are seeing issues with the previous release of UD where NFS servers are now being checked for the 'showmount -e' command displaying the NFS shares available. Right now if seems to be with Synology NAS devices. Just because the NFS port is open, does not guarantee that the remote server is actually able to server NFS shares. This tool can also be valuable when you aren't able to see the server when adding a remote share, or the share is added but the 'Mount' button is greyed out preventing the mounting of the share.

Keep in mind that Unraid supports NFSv3 and NFSv4. Your other systems may not. I think Synology can be configured to support one or the other or both.

Your issue is not with UD or Unraid, it is with the Synology. The reason this has shown up for you now is from a change in UD requiring a proper response from 'showmount' before a remote is determined to be online and ready for NFS mounts. This is why you see the greyed 'Mount' button. If there is a condition that might prevent a remote share mount, it doesn't make sense to enable the 'Mount' button if the mount would fail. If 'showmount' does not show any NFS shares, then UD has to assume none are available and the Remote Server is considered offline. I know in your case the mount would be successful, but the Synology situation is unique and wouldn't necessarily be the case with other Remote Servers. You should check with Synology about why 'showmount' is not working. I suspect your issue is network related. One user recently found the solution to this was to remove a static IP address from an unused NIC. I am adding a tool to UD settings that will let you enter a Remote Server name or IP address and check a server. UD will report what it sees from that server and whether a Remote Server SMB or NFS will be considered online.

UD checks for the port to be open for SMB and NFS on the remote server. Go to a command line on the Unraid server and enter this command: /usr/bin/timeout 10 bash -c '(echo >/dev/tcp/<server name or ip address>/445) &>/dev/null'; echo $? Put your server name or IP address in place of <server name or ip address> and post the results. The '445' is the port used by Samba for SMB shares. A value of '0' indicates the port is open.

An update to UD yesterday.

What version of Unraid are you using?

When showmout does not show the NFS shares, there is a configuration issue. The latest release of UD does an additional check now when it checks for a remote NFS server being online. If the NFS port (2049) is open, UD also checks that showmount shows NFS shares. The last user I worked with on this found a network issue on the Synology. If showmount does not return any NFS shares on a reachable remote server like a Synology, it generally means one of the following: 1. No NFS Shares Exported: The server might not have any directories configured for NFS export. Check the NFS configuration on the Synology device and ensure that folders intended for NFS sharing are explicitly exported. 2. Access Restrictions: NFS shares may be configured with IP-based access restrictions. Synology devices allow you to specify which IP addresses or networks can access each NFS share. If your IP address is not allowed, the NFS share won’t appear in showmount output. 3. NFS Service Not Enabled: The NFS service on the Synology might not be enabled. Verify this in the Synology DSM settings under Control Panel > File Services > NFS. Enable NFS if it’s currently disabled. 4. Firewall or Network Configuration: The Synology device may have firewall rules blocking the showmount request or the required RPC communication. Ensure that the firewall settings allow traffic on NFS-related ports (typically 2049 for NFS and 111 for RPC). 5. Synology Export Options: Synology’s NFS settings can sometimes require enabling Enable NFS at the top level and specifying Allow NFSv3 if you’re using clients that expect NFSv3. Check Control Panel > File Services > NFS to ensure proper configuration. By ensuring that NFS is enabled, configured with the correct permissions, and exported directories are allowed for your client IP, showmount should list the available exports.

We have been working on this. It should be fixed in Unraid 7.0, and we will be releasing an update to 6.12 that should also be fixed. Your server at 10.10.10.2 has an NFS configuration issue you need to solve. The showmount command has to show proper NFS mounts. Check your Synology NFS configuration.

UD can only mount devices that are formatted with a partition. If you can mount the device in another computer, you can then set up a remote share with UD. Another option is to set up a n Ubuntu VM and mount it with the VM.

Go to UD Settings and check the SMB and NFS share settings. UD does not share devices with SMB or NFS by default.

Glad you got it going. Sounds like today's update highlighted the issue with your Synology. That's probably a good thing that it is now fixed.

What is the output of: showmount -e <server name> and showmount -e <server ip_address>

Go to a command line and type 'ud_diagnostics', then post the /flash/logs/ud_diagnotics.zip.

Zero length files are not saved to the recycle bin. The file has to have at least one character in the file.

Just offering some options. I understand if they won't work for you.

Of course you would have to move the data off the disk, reformat, and then move the data back.

I just checked and I didn't have any problems. You may have an issue with your Internet, or you may have a memory issue. Try a reboot then update again.

You could also mount the disk on another computer and then add a remote share with UD.

Unraid Array and Pool disks are all formtted with partitions. UD follows that scheme so a disk can be created in UD (BTRFS, XFS, or ZFS) and then added to the Array or a Pool created without having to reformat.

UD doesn't recognize those disks as encrypted because they are formatted without a partition. That's what the 'Mount' button is showing - that there is no partition. Reformat them with UD and they will mount properly.

If you have an encrypted array and the passphrase on the UD disk is the same as the array, it will mount. If you don't have an encrypted array or the UD disk passphrase is not the same as the array, go to Settings->Unassigned Devices and set the passphrase for the UD disk. It will then mount.

In a command line type 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip file. Also post a screen shot of the UD page showing that disk.

Set the passphrase for the disk in UD settings. Mount the disk and run your tasks. Unmount the disk. Then go to the UD settings and clear the passphrase. I'm making a change in the UD passphrase settings to show "*****" when a password is set, and blank when the password is clear.

If you remove UD, do they continue?

Any disk that is unmounted and encrypted will show on that dropdown. I am making a change to not show one that is passed through. You can ignore that disk in the dropdown. It will not have a UD passphrase unless you previously set one. If you save a blank passphrase, that will clear it for that disk device in UD. Is that not what you are looking for?