dlandon

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 $?

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.

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.

Try clicking on the "Clear Cache" button.

Did you make any adjustments to the settings?

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?

Post diagnostics.

Cache_dirs will cache everything when you use default share settings. It will even cache UD Remote Shares, which is very inappropriate. Set up cache_dirs to only include shares you want cached. Don't set it to cache SSD disks, that's not necessary.

Please install the "Active Directory Extras" plugin from CA and make the adjustments you think you need to get AD working. If there are other settings required, let me know and I'll make adjustments to the plugin. I believe it will let you make the changes needed to get AD working.

Fixed in latest release. Update again,

Install the OC docker container.

New release of UD: Fixed a case where UD could potentially cause an unclean shutdown if you have a rootshare mounted. Fixed a few issues related to remote server name lookup. Improved adding remote share to show which protocol you are working with.

I'm adding an 'Array' indicator to the mount button to indicate a possible array disk dropped offline so UD won't allow any operations on the disk. The device sdX indicates that Unraid doesn't see the disk as an unassigned disk.

These versions don't make any sense.

Are you using a docking station or drive bay?

I guess I misunderstood what you were doing. Your first screen shot is the stock Unassigned Devices display without the UD plugin being installed. Your second screen shot is with the UD plugin installed. The devices are being discovered properly. You have not setup any array devices and of course your array is not started. You are in a weird state and I'm not sure that UD is detecting unassigned devices. Unraid dynamically sets the unassigned devices for UD by assigning the 'devX' designation. I don't believe UD is keeping up with the Unraid changes in this condition because UD thinks some disks are still assigned to the array. This is not a situation I've tested before - i.e. no array disks assigned. Uninstall the UD plugin and set up your array. Once you'e done that. start the array and then install UD to manage the unassigned disks. Post back here if you still see issues after doing that.

Understood, but I need to see what udev is seeing in each case. I cannot reproduce this issue and will need your diagnostis to try to figure it out. UD+ is only some additional packages installed for additional support. I doesn't change anything that I know of that would affect what devices udev sees.

Post diagnostics when all show and when only some show.

Try doing a force update to refresh the docker container.

I was finally able to reprodice this issue, That's the good news; the bad news is there is no fix that can be done to fix this in Unraid. UD uses some built in functions to perform the script file operations. I can find no solution for Unraid to fix this. This only occurs when Private Browsing in Chrome and appears to be a bug in one of Chrome's security features causing POST failures in specific circumstances. There are no other instances of doing things like UD does in Unraid, so this should not show up anywhere else. There are several options to deal with this: Turn off security in Chrome when Private Browsing. Turn off security for Unraid only when Private Browsing in Chrome. Don't use Chrome Private Browsing when using Unraid. This comment was not very helpful at all, and was honestly quite annoying. There was an issue when some characters (e.g. '<', '>', etc) are used in file names that will cause a php warning and fail a file save or edit. I've added some code to deal with this.

Show a screen shot of the default file name in the settings after clocking on the "Default" button. I'd like to see if there are any characters in the default name causing issues with php.

Go to the Tools->PHP Settings and set the error reporting level to all caegories and the n create the issue where yoou can't save a script. The see if any warnings or errors show in the PHP log.

I'm using Brave (also based on Chromium) and don't see the issue in incognito mode. Do a few things and see if there are errors/warnings when this happens: Click on Tools->PHP Settings and see if there are any log entries. While on the UD Device Settings page hold down Ctrl-Shift keys and press 'J'. This will show the Java console. See if there are any errors there.