dlandon

Looks like a bug in that preclear thinks the serial number is the same for all three even though they are not. You'll have to just preclear them one at a time by removing the other two disks.

Post Unraid diagnostics.

Has your problem been resolved?

New release of UD: Change in remote server online check that should solve the situation where a remote share can be successfully added but then shows as being offline. Some code cleanup for robustness.

Unzip the attached file and copy it to: cp get_ud_stats /usr/local/emhttp/plugins/unassigned.devices/scripts/ and see if the name works and your shares show up as online. get_ud_stats.zip

Unraid uses avahi (nDNS) to look up names and if the DAASTATION doesn't use mDNS, Unraid will probably not be able to look it up by name. This is only a situation in UD and shouldn't affect anything else in your system. I'm trying to find a way to get around this issue if I can. Give me the output of this command: arp -a DATASTATION.LOCAL

Go to a command line and give me the output of these comands: /usr/bin/timeout 1 bash -c '(echo >/dev/tcp/DATASTATION/445) &>/dev/null'; echo $? and /usr/bin/timeout 1 bash -c '(echo >/dev/tcp/DATASTATION.LOCAL/445) &>/dev/null'; echo $? UD has been changed and now relies on a local DNS server for name resolution.

I don't see any remote shares defined. Have you gone through the process of adding the remote shares with UD? If you add them with UD and they don't show as being online, you'll need to use the DATASTATION IP address. instead of the name Be sure it is a static IP.

Go to a command line and type ‘ud_diagnostics’, then post /flash/logs/ud_diagnostics.zip.

Update to 6.12.10. There is a bug in 6.12.9 that causes this problem.

I would try to find another way as this affects performance on all SMB shares if you do this globally in smb-extras.

Rsync is trying to write extended attributes and the vfat file system does not support extended attributes, You have several options: Reformat the drive to another file system that supports extended attributes. Tell rsync to not write extended attributes.

What file system is the UD disk?

Post your diagnostics.

Excellent. Glad you got it sorted.

You'll have to post UD diagnostics so I can take a look at it.

Both sdl and sdm have the same mount point: "EFI". Each mount point has to be unique. Either don't mount these partitions at the same time, remove them if they are not needed, or rename them to be unique (best choice). UD thinks the disk (sdl) was not unmounted and then reinserted, and marked the mount button "Reboot" because it thinks the disk was not properly unmounted.

The mount button indicators are documented in the first post. For me to investigate further, please supply the ud diagnostics. Go to a command line and type 'ud_diagnostics'. Then post the /flash/logs/ud_diagnostics.zip file here.

That does pretty much the same thing as the port check commands I posted. I do find them to be slightly faster.

It wasn't you. Sometime ago I made a change that borke it and it hasn't come up until now. It was pretty messy as it actually deleted all the configuration.

Use the IP address and not the name.

The recent changes to the way UD checks for remote servers being online were done to eliminate the inappropriate way UD was managing remote server names trying to get around local DNS name lookup issues. The way it works now is using several methods to lookup server names after an IP address is found to have an open SMB or NFS port when searching for servers. Nmblookup and avahi are used to find the names. The issue comes when UD tries to verify the server is online with the servername and not the IP address. There are several things that can cause this to not work related to local DNS lookups: You need to be sure that your Unraid and the remote server have the same local TLD. In Unraid, this is on the Settings->Management Access tab. When this is set to blank or "local", the Local TLD is "LOCAL" and will be appended to the server name. You have an issue with mDNS on a remote server and avahi can't resolve the name. Your network setup is not allowing local DNS to resolve the name. I'm still looking into how this works to see if there are things UD can do to get around some of this. The solution for now is to use a static IP address on the remote server, and use the IP address of the remote server in UD. EDIT: Try re-adding the remote share first to see if UD picks up the right server name and can resolve the name for online status check.

Use an IP address for your remote server instead of the name.

If you use the IP address, the command checking the ports will show as open. That's what the initial server scan does. After the server scan returns the list of IP addresses with open ports, I try to find the name for that server. Apparently there are issues with the name resolution on some machines as it works fine for me.

I'm putting out a release this evening. For the time being I'll increase the time out to 30 seconds. Let's see if the UD page will refresh for you.