dlandon

I suppose it is possible you have a bad disk.

You will get the same issue. Post your diagnostics here.

Working for me. Try again, there may have been a temporary issue.

I forgot that different versions of tmux require different versions of libc. The version of libc in Unraid varies by Unraid version, so I have to do a version check to see which version of tmux can be installed for the version of Unraid running. I can't update libc, because it will break Unraid. It was an easy fix once I remembered what I needed to do.

Update the plugin and reboot to clear up the tmux issue. Uninstalling and re-installing the plugin will not work.

I'm working on a fix and will update the plugin shortly.

Try some of the ideas mentioned earlier in this forum post. If I can get ideas from users on what additional settings the AD Extras plugin needs, I can implement those. Unfortunately, I don't have any way of testing AD because I do not have a Windows server. I rely on the users here to give me ideas on what is needed.

This is your rule. IP address and options.

Update UD Preclear and see if it solves your issue.

At the end of a disk, the write takes longer and the dd write may time out too soon on a very large disk. I've already extended the time out, but it might need to be even longer.

No, here: Go to Settings->Unassigned Devices.

You are using UD to mount that disk. Go to the unassigned devices settings and enter your rule there. UD will then apply it to the exports file.

Go to a command line and run this command: ud_diagnostics Then post the /flash/logs/ud_diagnostics.zip file. There are some things I need to confirm in your setup.

Ok, it's not timing out. The issue is the NFS port (2049) on your remote server is not open.

Try this command: /usr/bin/nice /usr/bin/timeout 2 bash -c '(echo >/dev/tcp/100.67.144.43/2049) &>/dev/null'; echo $? I've adjusted the timeout. I think the command is timing out and returning a value that indicates the server is not available.