dlandon

You are using 'smb encrypt' in the smb-extra.conf file. I have not tested this to see if it has any affect on the recycle bin operation.

Read the first post about 'User Script'.

That indicates that the disk is spun up. When a disk is preclearing, UD does not scan to see if the disk is spun up so it doesn't interfere with the preclear.

UD mounts the remote mount, but has no control over the operation of the NFS share. Linux manages the remote share. UD does not unmount the share if the server goes off-line. With that said, please post diagnostics when this happens and I'll see if here is more that can be done to prevent hangs.

You appear to have a corruption in your /config/plugins/unassigned.devices/unassigned.devices.cfg file. Several options: Reboot server to see if it clears up. That file is copied to ram disk and it may have been corrupted. Remove the unassigned.devices.cfg file and reboot. You will have to re-do any UD mounted disks. If it does not clear up, you'll need to shutdown the server and put your flash drive in another computer and check for issues.

Be sure you have the run time and dev packages. Version 10.2.

Some partition layouts are not seen by Linux as valid partitions. Take it to a Windows computer and see if the partition layout makes sense.

The disk format is not detected by Linux.

Remove the preclear plugin and see if it makes a difference. What does the UD page show? The ST6000 seems to be having a lot of read issues - look at the SMART report.

Are these the disks you are having trouble with? May 5 00:55:29 media01 kernel: sd 3:0:0:0: [sdd] tag#1432 Sense Key : 0x1 [current] May 5 00:55:29 media01 kernel: sd 3:0:0:0: [sdd] tag#1432 ASC=0x1c ASCQ=0x2 May 5 00:55:29 media01 kernel: sd 3:0:2:0: [sdf] tag#1436 Sense Key : 0x1 [current] May 5 00:55:29 media01 kernel: sd 3:0:2:0: [sdf] tag#1436 ASC=0x1c ASCQ=0x2 May 5 01:01:11 media01 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog May 5 01:02:36 media01 kernel: sd 3:0:2:0: [sdf] tag#433 Sense Key : 0x1 [current] May 5 01:02:36 media01 kernel: sd 3:0:2:0: [sdf] tag#433 ASC=0x1c ASCQ=0x2 May 5 01:02:36 media01 kernel: sd 3:0:0:0: [sdd] tag#334 Sense Key : 0x1 [current] May 5 01:02:36 media01 kernel: sd 3:0:0:0: [sdd] tag#334 ASC=0x1c ASCQ=0x2

That was changed years ago. The issue was that people that were not tech savy were mounting devices all over the place and causing a lot of support issues. I'll take a look at your diagnostics later when I have some time.

You have the "Pass Thru" switch on which will prevent auto and manual mount. Turn off that switch.

Spend a minute and get all your dockers and plugins up to date. May 2 04:40:01 VH1 root: Fix Common Problems Version 2020.04.19 May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application jackett has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application lidarr has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application netdata has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application nzbhydra2 has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application ombi has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application PlexMediaServer has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application radarr has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application sabnzbd has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application sonarr has an update available for it May 2 04:40:02 VH1 root: Fix Common Problems: Warning: Docker Application unifi-controller has an update available for it UD is currently at 2020.04.27, your system is at 2020..04.03a. The first thing you should do before asking for help is to be sure all plugins and dockers are up to date. Also verify that Jumbo Frames are disabled on both servers and switch and MTU is set to default on all devices (usually 1500).

Set the frame size to default on all devices. Incorrect Jumbo Frame setting is known to cause the issues you are seeing. You can't set only one device to Jumbo Frames.

No. Are you using Jumbo Frames anywhere in your network?

You really need to solve some of these problems first: Apr 30 02:01:30 VH1 shfs: cache disk full ### [PREVIOUS LINE REPEATED 10 TIMES] ### Apr 30 02:03:18 VH1 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 30 02:04:04 VH1 emhttpd: shcmd (15922): /usr/local/sbin/mover &> /dev/null & Apr 30 02:04:23 VH1 kernel: CIFS VFS: Close unmatched open Apr 30 02:06:36 VH1 shfs: cache disk full ### [PREVIOUS LINE REPEATED 766 TIMES] ### Apr 30 02:07:34 VH1 move: error: move, 397: No such file or directory (2): lstat: /mnt/disk2/downloads-inprogress/sabincomplete/Miles.Davis.Birth.Of.The.Cool.2019.1080p.BluRay.x264-GETiT/__ADMIN__/SABnzbd_article_e03H9A Apr 30 02:07:34 VH1 move: error: move, 397: No such file or directory (2): lstat: /mnt/disk2/downloads-inprogress/sabincomplete/Miles.Davis.Birth.Of.The.Cool.2019.1080p.BluRay.x264-GETiT/__ADMIN__/SABnzbd_article_xRsFx4

The ACPI Driver is a generic driver. You need to load the CPU scaling driver specific to your CPU. I'n not an expert on the Ryzen processors, so I don't know which driver applies.

What driver shows in the "CPU Frequency Scaling"?

This hasn't been done because the Enhanced Syslog doesn't work with the Syslog Server.

If someone will post diagnostics, I can take a look.

The color was to indicate highlighted text. I agree, I have put back the '+' and removed the highlight. Not all my ideas work out.

I just released an update to UD. The changes are all related to the UI. The most noticeable change is that the '+' icon has been removed. You click on the serial number to access the partitions and mount points. The other changes are related to page layout to better match the Unraid standard and fit things better on the page.

UD works on the premise that each disk has a unique identifier (serial number) and was not built to handle duplicates because they should never come up. Each disk is expected to have a unique serial number. I think you are confused about the 'rename'. It appears you think by setting the mountpoint name, the disk will then be unique,. The name you are setting is the mountpoint for the disk and has nothing to do with making each disk 'unique' to UD. The serial number is the only thing used to identify the disk.

UD checks for a disk busy error when a disk is unmounted and if it is busy, it checks for open files. If no files are open, the unmount is forced. If you look at the log, you'll see the log messages showing this action. If UD operated as you suggest, and this situation was to come up during a shutdown, you would get an unclean shutdown and I'd be hearing about a 'bug' in UD that would not allow the array to shutdown cleanly. The problem is the mountpoint could not be removed because you were on the cli accessing files at the mountpoint. While this situation might be an annoyance to you, it is really the best way for UD to operate. Fix: Don't unmount a disk if you are in the cli on that disk.

Remove both disks and then delete all references to their serial numbers in the "Historical Devices" section. The unique data point is the serial number. The best way to handle this is to install disks with unique serial numbers.