dlandon
-
Posts
10151 -
Joined
-
Last visited
-
Days Won
19
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dlandon
-
-
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.
-
4 hours ago, kontraschub said:
If re-enter means to set the permision to a share again using a Windows machine, then I did it already. Even new shares don't work.
If I add "full control" to "everyone" then it works. But that's not what I want.
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.
-
30 minutes ago, Original_Vecna said:
192.168.1.187(rw,sync,no_subtree_check)
This is your rule. IP address and options.
-
3 hours ago, Gico said:
Same happens with a different HBA: LSI PCI-E card.
Is there anyway to limit the available disk size to 22000000000000?I can also try zeroing it on my main machine (the one in my signature).
Update UD Preclear and see if it solves your issue.
-
1
-
-
3 hours ago, Gico said:
Same happens with a different HBA: LSI PCI-E card.
Is there anyway to limit the available disk size to 22000000000000?I can also try zeroing it on my main machine (the one in my signature).
Apr 23 14:23:27 preclear_disk_ZGG46T0A_10952: Zeroing: dd output: 22000449880064 bytes (22 TB, 20 TiB) copied, 98245.7 s, 224 MB/s Apr 23 14:23:27 preclear_disk_ZGG46T0A_10952: dd process hung at 22000451977216, killing ... Apr 23 14:23:27 preclear_disk_ZGG46T0A_10952: Zeroing: zeroing the disk started 2 of 5 retries... Apr 23 14:23:27 preclear_disk_ZGG46T0A_10952: Continuing disk write on byte 22000449880064 Apr 23 14:31:52 preclear_disk_ZGG46T0A_10952: Zeroing: dd output: Apr 23 14:31:52 preclear_disk_ZGG46T0A_10952: dd process hung at 0, killing ... Apr 23 14:31:52 preclear_disk_ZGG46T0A_10952: Zeroing: zeroing the disk started 3 of 5 retries... Apr 23 14:31:52 preclear_disk_ZGG46T0A_10952: Zeroing: emptying the MBR.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.
-
1
-
-
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.
-
1 hour ago, Hammerfest said:
refresh was done of course, no visual change noted
Go to a command line and run this command:
ud_diagnosticsThen post the /flash/logs/ud_diagnostics.zip file. There are some things I need to confirm in your setup.
-
1 minute ago, Allram said:
It still says "1".
Also tried to increase the timeout to 20 and still got "1".
Ok, it's not timing out. The issue is the NFS port (2049) on your remote server is not open.
-
3 minutes ago, Allram said:
The result was "1".
root@Tower:~# /usr/bin/nice /usr/bin/timeout 1 bash -c '(echo >/dev/tcp/100.67.144.43/2049) &>/dev/null'; echo $? 1 root@Tower:~#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.
-
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.
-
19 minutes ago, Hammerfest said:
refresh was done of course, no visual change noted
On the UD page, do the device settings show as 'Dev X'?
-
2 hours ago, Allram said:
Tried the new UD_diagnostics, seems like since the server is not answering on ping (ping_status.txt) it automatically sets it as offline? It works fine on my other UnRaid server with an older version of the plugin, so is this something new?
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 $? -
Just now, Hammerfest said:
did not even have to use the refresh, soon as it was installed, boom, they all show up
❤️
Yes, but please do the refresh so the device designations show up correctly.
-
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.
-
On 4/19/2024 at 1:17 AM, Hammerfest said:
HP DL380 Gen9 with only drive bays, none of the drives where physically removed at all during any of the testing mentioned
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.
-
2 hours ago, kontraschub said:
What am I doing wrong?
Try clicking on the "Clear Cache" button.
-
Did you make any adjustments to the settings?
-
6 hours ago, Allram said:
UD says "Remote server is offline" and can't mount.
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.
-
I see several issues:
Apr 21 17:18:48 Tower unassigned.devices: Mounting 'Auto Mount' Remote Shares... ... Apr 21 17:18:54 Tower unassigned.devices: Mounting Remote Share '100.67.144.43:/mnt/user/Backup-Vegard'... Apr 21 17:18:54 Tower unassigned.devices: Remote Server '100.67.144.43' is offline and remote share '/mnt/user/Backup-Vegard' cannot be mounted.Then later:
Apr 21 17:25:37 Tower unassigned.devices: Warning: 'Backup-Vegard' is already added as a 'NFS' share.Things to look at:
- You have the default 5 seconds delay before trying to mount remote shares, but in the log I see where later you set 20 seconds. That should help.
- Can you mount the remote share after Unraid is fully started and running?
- I don't understand the "Warning: 'Backup-Vegard' is already added as a 'NFS' share.". Are you duplicating this NFS share?
-
4 minutes ago, Allram said:
Updated the plugin (about 3 weeks since the last update I did) and now it won't connect to an NFS unRAID server connected trough Tailscale.
It finds the device when I add a new share, but it refuses to mount it: "Remote server is offline", but it is indeed online.
Any tips on how to solve this?
Post diagnostics.
-
1
-
Unassigned devices failing to upgrade
in Plugin System
Posted
You will get the same issue. Post your diagnostics here.