dlandon

You can enter a disk password for that disk.  Go to the UD Settings and set a password for the disk.

The 'Reboot" label means the disk was not unmounted properly before being removed.  If you reboot the server, it will clear it up.

Your boot flash is having problems:
Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Nov 21 09:56:43 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 52 00 00 28 00 Nov 21 09:56:43 LOF1-NAS kernel: critical medium error, dev sda, sector 11627346 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2 Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Nov 21 10:01:02 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 22 00 00 b0 00 Nov 21 10:01:02 LOF1-NAS kernel: critical medium error, dev sda, sector 11627298 op 0x0:(READ) flags 0x80700 phys_seg 22 prio class 2 Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 5a 00 00 08 00 Nov 21 10:01:03 LOF1-NAS kernel: critical medium error, dev sda, sector 11627354 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 21 10:01:03 LOF1-NAS kernel: I/O error, dev loop1, sector 300480 op 0x0:(READ) flags 0x800 phys_seg 15 prio class 2 Nov 21 10:01:03 LOF1-NAS kernel: SQUASHFS error: Failed to read block 0x92b88c0: -5 Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Nov 21 10:01:03 LOF1-NAS kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 b1 6b 62 00 00 08 00 Nov 21 10:01:03 LOF1-NAS kernel: critical medium error, dev sda, sector 11627362 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 21 10:01:03 LOF1-NAS kernel: I/O error, dev loop1, sector 300480 op 0x0:(READ) flags 0x800 phys_seg 16 prio class 2 Nov 21 10:01:03 LOF1-NAS kernel: SQUASHFS error: Failed to read block 0x92b88c0: -5  
Shut down and take your flash to a PC and do a file check.  You might have to reformat the flash and start over, or use a new one.  Be sure to save and restore the /flash/config/ folder.
 
Samba is crashing.

Docker appears to be having issues right now and that is causing your EOF error.  Give it some time and try again.  It should clear up.

Update alll your plugins.  Your UD plugin is a year old!
 
It is recommended that all plugins be updated before updating Unraid.

Update UD.

You have several issues:
There is an issue with 6.12.3 with the version of NFS being mounted with UD.  Set the 'Settings->Unassigned Devices->Common Settings->NFS' Version to use to NFSv4.  This will have UD mount NFS devices with NFSv4.  This has been fixed in 6.12.4 and the setting can be set to 'Auto'. You have an issue with one of the servers being 'online': Sep 5 16:39:17 utility unassigned.devices: Remote server '10.10.0.2' is not responding to a ping and appears to be offline.  

//1.2.3.4/ refers to a server, and is not a share.  Your attempts to enter an empty share won't work.  UD accepting the " " and "/" is really a bug.  The share has to be specified and be a valid share.  The 'Done' button won't work until some text is entered.  The share field can't be empty.
 
Try setting up a root share on the remote server and you can then add that as a remote share which will refer to the remote shares as //1.2.3.4/rootshare/ that will contain all your shares.

You can update UD without it affecting the preclear.  All UD does is show the preclear status.

I found a problem and I am fixing it now.  Wait for the newest version of UD, update UD, and then remove the samba_mount.cfg file and add your remote shares back.

You have issues with a remote share:
May 19 12:47:35 Tower emhttpd: read SMART /dev/sdo May 19 12:50:53 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close unmatched open for MID:1457021 May 19 12:52:07 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close unmatched open for MID:1475270 May 19 12:53:18 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close interrupted close May 19 12:53:52 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close unmatched open for MID:1510647 May 19 12:55:05 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close interrupted close May 19 12:55:08 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close cancelled mid failed rc:-9 May 19 12:56:08 Tower unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/PLEXINGTON_data' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s! May 19 12:57:22 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close interrupted close May 19 12:57:24 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close cancelled mid failed rc:-9 May 19 12:59:12 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close unmatched open for MID:1586268 May 19 12:59:46 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close interrupted close May 19 12:59:47 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close cancelled mid failed rc:-9 May 19 13:01:32 Tower kernel: CIFS: VFS: \\PLEXINGTON\data Close unmatched open for MID:1626809 That shouldn't cause the constant Unraid wave, but that may be the cause.
 
I would do the following:
Click on the double arrows icon in the upper right hand corner of the UD page and see if it comes back to life. Remove the /flash/config/plugins/unassigned.devices/samba_mount.cfg file.  This will remove all your remote share configurations.  You can add them back later. Try clicking on the double arrows icon and see if UD comes back to life. Reboot both servers.

I'm going to guess that the Drobo disks may have some errors?
 
I like your idea of only mounting the remote share when it is needed and then unmounting it when you are done.  You can mount and unmount remote shares in a script using rc.unassigned.  Go to the UD webpage and enable 'Help', then scroll down the page to see the rc.unassigned commands for mounting a remote share.  You can do the same to unmount it.

Start by removing the smb-extra.conf entries:
path = /mnt/disks/gDrive comment = browseable = yes # Public public = yes writeable = yes vfs objects = That's a UD disk and UD can do the sharing for you.

In your log:
Mar 12 17:38:43 Tower unassigned.devices: Unassigned Devices are not set to be shared with SMB. Mar 12 17:38:43 Tower unassigned.devices: Unassigned Devices are not set to be shared with NFS.  
Go to Settings->Unassigned Devices and set the SMB security to something other than "No".

There are several issues:
You are very far behind in updating UD. There are disk issues: Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 60976: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 721727062, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 60976: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read $MFT bitmap: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 721727062, async page read Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 37, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 5739: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 435373662, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 5739: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[8797]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[8797]: Failed to read vcn 0x0 from inode 5: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 435373662, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 5739: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error The 'Reboot' indicator on the 'Mount' Button indicates that the disk was not unmounted before being removed You can click the check mark icon next to the partition to check the disk.. Do This:
Update UD. Turn off 'Auto Mount" on those disks. Reboot the server. Run a file system check on both disks. Mount the disks and verify everything is ok.  

Your log says:
Mar 13 09:55:08 Phoenix unassigned.devices: Unassigned Devices are not set to be shared with SMB. Mar 13 09:55:08 Phoenix unassigned.devices: Unassigned Devices are not set to be shared with NFS.  
Go to Settings->Unassigned Devices and set SMB security to something other than no.

Ignore it or wait for another FCP update.

There is a fix in the latest samba release that will be included in Unraid 6.12.  Until that is released, add the following to your SMB Extras file:
logging = 0  

You need to do the following:
Remove "statistics.sender.plg".  It's part of the old preclear.  It is no longer needed and is not compatible with 6.11. Remove "modprobe i915" from the go.txt file, Unraid takes care of that in 6.11. Remove all the stuff in the smb-extra.conf file and install UD to create a rootshare. Put "[global]" and "logging = 0" in the smb-extra.conf. Reboot.

Put this in your /flash/config/go file or create a User Script to run when the array is first started:
ulimit -Sn 40960  
You can't edit the /etc/security/limits/conf file because it is not persistent on reboots.  This command will apply the soft limit at the start of the array.
 
The soft limit should apply to any non root users.
 
Is there a way to apply the ulimit in the backup system script?  That would apply the ulimit when it runs.

I just did a little research on AD and based on what I found is yes, AD can be used for share permissions on an Unraid share.  You need to enable AD on Unraid in SMB settings.  If you switch back to WORKGROUP, you need to run the fix permissions script on the AD shares to get permissions back to nobody:users.

Yes.
 
Add more memory.

Python 2 is available as a plugin in CA.  Search python.

It doesn't look like you are mapping the folders properly.  Emby is set to use /mnt/ and you map the media folders in the docker itself:

 
Once inside Emby, you select the folders for the media you want to use:

and choose the folders for each media type:

or probably the best approach:

 
Substitute your server name for 'Tower'.

UD Preclear writes a disk signature and partition so that the disk is ready for Unraid.  To format it for UD, you will need to clear the disk as you have shown above.  You can then format the disk with UD.