dlandon

Community Developer
  • Posts

    10153
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by dlandon

  1. Yes, and none unless you want UD to manage the device again. Historical devices only remembers device settings so they are restored when a drive is reinstalled. This is how a auto mounted USB device for backups works. The settings are remembered in the historical devices so UD knows what to do with the drive when it is re-installed or hot plugged.
  2. You will get the same issue. Post your diagnostics here.
  3. Working for me. Try again, there may have been a temporary issue.
  4. 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.
  5. Update the plugin and reboot to clear up the tmux issue. Uninstalling and re-installing the plugin will not work.
  6. 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.
  7. This is your rule. IP address and options.
  8. 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.
  9. No, here: Go to Settings->Unassigned Devices.
  10. 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.
  11. 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.
  12. Ok, it's not timing out. The issue is the NFS port (2049) on your remote server is not open.
  13. 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.
  14. As noted on the "Active Directory Extras" page, if you change the backend database, you need to re-enter all your permissions. The default backend database in Unraid is 'hash' and if you change to 'tdb', you have to reset all your permissions.
  15. UD no longer pings remote servers. Instead it checks that the NFS port is open on the remote server. Because of security, some servers don't respond to a ping. Run this command and post the result: /usr/bin/nice /usr/bin/timeout 1 bash -c '(echo >/dev/tcp/100.67.144.43/2049) &>/dev/null'; echo $?
  16. New UD release: Fixed several situations where all unassigned disks don't show on the UD page. Added a diagnostics script for collecting information specific to UD that doesn't show in the Unraid diagnostics. This should make it easier to troubleshoot UD specific issues. It has gotten more difficult to shoot down some of the issues comming up now. This should help. For the moment, it is a command line tool only.
  17. Update UD and see if the situation is fixed. After updating, click the double arrows in the upper right of the UD page to refresh the udev and hot plug info.
  18. Nowhere in the logs is there an attempt to mount a remote share either manually or auto mount. It doesn't indicate any remote shares added. When UD gets to the point where remote shares are to be auto mounted, it will either mount the remote share or indicate it is not set for auto mount. I see none of this.