dlandon

Delete the samba_mount.cfg, then click on the double arrows icon in the upper right of the UD page. You will then have to re-enter your remote share mounts.

Thank you. That's what I needed. Let me take a look.

Run preclear again and choose verify disk.

Post the file '/flash/config/plugins/unassigned.devices/samba_config.cfg'.

Post diagnostics.

It looks like your share /mnt/user/macos is an exclusive share. Change the VM xml to map to the actual share location i.e. /mnt/cache/macos. EDIT: Or add a trailing slash '/mnt/user/macos/'.

Post diagnostics.

See if your router or switch has any diagnostic tools like cable tests. Try rebooting all your network equipment.

Ok. Looking at your logs again, I see you took care of the TRUENAS and JOHN-PC issues. I see this in your logs that shows a network issue of some sort: May 23 02:40:01 Tower root: Fix Common Problems: Warning: Share wikijs database set to cache-only, but files / folders exist on the array May 23 02:40:01 Tower root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored May 23 02:40:02 Tower root: Fix Common Problems: Warning: unRaids built in FTP server is currently disabled, but users are defined May 23 02:40:02 Tower root: Fix Common Problems: Other Warning: Could not check for blacklisted plugins May 23 02:40:05 Tower root: Fix Common Problems: Other Warning: Background notifications not enabled May 23 02:40:09 Tower kernel: igb 0000:09:00.0 eth0: igb: eth0 NIC Link is Down May 23 02:40:09 Tower kernel: bond0: (slave eth0): link status definitely down, disabling slave May 23 02:40:09 Tower kernel: device eth0 left promiscuous mode May 23 02:40:09 Tower kernel: bond0: now running without any active interface! May 23 02:40:09 Tower kernel: br0: port 1(bond0) entered disabled state May 23 02:40:11 Tower ntpd[1656]: Deleting interface #4 br0, 10.10.20.8#123, interface stats: received=0, sent=0, dropped=0, active_time=804 secs May 23 02:40:21 Tower kernel: igb 0000:09:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX May 23 02:40:21 Tower kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex May 23 02:40:21 Tower kernel: bond0: (slave eth0): making interface the new active one May 23 02:40:21 Tower kernel: device eth0 entered promiscuous mode May 23 02:40:21 Tower kernel: bond0: active interface up! May 23 02:40:21 Tower kernel: br0: port 1(bond0) entered blocking state May 23 02:40:21 Tower kernel: br0: port 1(bond0) entered forwarding state May 23 02:40:22 Tower ntpd[1656]: Listen normally on 5 br0 10.10.20.8:123 May 23 02:40:22 Tower ntpd[1656]: new interface(s) found: waking up resolver May 23 02:40:23 Tower root: Fix Common Problems: Other Warning: Could not perform unknown plugins installed checks May 23 02:40:23 Tower root: Fix Common Problems: Warning: Share system set to use pool optane, but files / folders exist on the cache pool At one point you had no active interface for at least twelve seconds. FCP is also struggling to connect to the internet.

Your screen shot is for UD didks. It looks like you have some remote shares assigned to TRUENAS and JOHNS-PC. You need to remove those if they are no longer being used. Show a full screen shot of UD.

Boot in safe mode and see if the issue persists.

UD is trying to connect to the TRUENAS server on your network. There seems to be an issue with JOHN-PC also. Even if UD has nothing mounted, it is still trying to poll your remote servers to get an online status. Remove the remote shares from UD that are no longer being used. That will stop the logging of the UD messages, but probably not solve the server issues. Then reboot and post new dagnostics.

Unassigned Devices is timing out when trying to perform operations on your remote server (TRUENAS).

I'm not seeing anything in the logs that offers any insight on what's going on. Some things to try: Remove the disk location plugin. I'm not sure this will fix the issue, but give it a try. Check your Unraid network settings. Boot in safe mode, start the array and try to update docker containers. This will keep all the plugins from being installed and will eliminate any plugin issues. If the issue continues, you need to review your router setup, check your Internet speed, and check for any networking issues.

It's only array shares at /mnt/user/. UD does not have exclusive shares because UD mounts are not managed by Unraid shfs.

Yes, the /mnt/addons/ was a recent addition.

Have you enabled NFS on Unraid and set up the share to be shared with NFS?

Several issues with what you are doing: A mount point has been created for these kinds of mounts. Use /mnt/addons/. It used to be recommended to use /mnt/disks/ so FCP wouldn't flag a problem with your mounts. That's why UD creates the /mnt/addons/. So users have a place for special mounts that do't interfere with UD. UD adds some protection and FCP will not flag anything there as a problem. Your ZFS mount needs to happen after the array is running and UD has been installed on a reboot. Updates of UD won't flag the issue because the protection mount has already been applied at boot.

I added a setting to hide the recycle bin folders and had the default set to 'Yes', instead of 'No'. Update and it should fix it.

Your queston is confusing. Are you trying to access an Ubuntu share on your Unraid server?

You have an issue with the remote server or the network.

When UD is installed, it applies a protective mount on the mount points it uses. This only allows 1MB of data on the mountpoints. If a Docker Containr or VM has an incorrect mapping to one of thee mount points, the mount point fills up and prevents any more writes so the ramfs is not filled. The banner that you see is because UD detected something already mounted at one of it's mount points and wants a reboot to clear up the mount. Do this: Make sure all devices are unmounted in UD - disks, remote shares, and iso mounts. Go to a command prompt and do an ls on '/mnt/didks/', /mnt/remotes/', /mnt/rootshare/', and '/mnt/addons/'. If you see anything at any of the mount points, it must be removed so UD can complete an update. The exception is '/mnt/addons/' that is intended for users to mount their unique stuff. If you are mounting something there, be sure it does it's mount after UD has installed.

There is a lot of this in your log: May 20 10:07:14 Tower smbd[32664]: synthetic_pathref: opening [BILDER/DIV/_MG_1428.JPG] failed May 20 10:07:15 Tower smbd[32664]: [2023/05/20 10:07:15.260677, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:15 Tower smbd[32664]: synthetic_pathref: opening [BILDER/DIV/_MG_1429.CR2] failed May 20 10:07:15 Tower smbd[32664]: [2023/05/20 10:07:15.272700, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:15 Tower smbd[32664]: synthetic_pathref: opening [PLEX/FILME/poe-faf6-xvid.avi.mp4] failed May 20 10:07:15 Tower smbd[32664]: [2023/05/20 10:07:15.281814, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:15 Tower smbd[32664]: synthetic_pathref: opening [DOKUMENTE/3D Scanned/Scans/2020-12-31_10_48_30.skn/images/0000000000000000-0/view-00129198/calibration.yml] failed May 20 10:07:17 Tower smbd[32664]: [2023/05/20 10:07:17.601704, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:17 Tower smbd[32664]: synthetic_pathref: opening [DOKUMENTE/3D Scanned/Scans/2020-12-31_10_48_30.skn/images/0000000000000000-0/view-00129198/grabber-type] failed May 20 10:07:19 Tower smbd[32664]: [2023/05/20 10:07:19.054329, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:19 Tower smbd[32664]: synthetic_pathref: opening [BILDER/DIV/_MG_1429.JPG] failed May 20 10:07:20 Tower smbd[32664]: [2023/05/20 10:07:20.801702, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:20 Tower smbd[32664]: synthetic_pathref: opening [DOKUMENTE/3D Scanned/Scans/2020-12-31_10_48_30.skn/images/0000000000000000-0/view-00129198/rgb_pose.avs] failed May 20 10:07:25 Tower smbd[32664]: [2023/05/20 10:07:25.054177, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:25 Tower smbd[32664]: synthetic_pathref: opening [BILDER/DIV/_MG_1430.CR2] failed May 20 10:07:31 Tower smbd[32664]: [2023/05/20 10:07:31.099917, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:31 Tower smbd[32664]: synthetic_pathref: opening [DOKUMENTE/3D Scanned/Scans/2020-12-31_10_48_30.skn/images/0000000000000000-0/view-00129198/sensor_properties.txt] failed May 20 10:07:39 Tower smbd[32664]: [2023/05/20 10:07:39.930268, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:39 Tower smbd[32664]: synthetic_pathref: opening [BILDER/DIV/_MG_1430.JPG] failed May 20 10:07:42 Tower smbd[32664]: [2023/05/20 10:07:42.114140, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:42 Tower smbd[32664]: synthetic_pathref: opening [DOKUMENTE/3D Scanned/Scans/2020-12-31_10_48_30.skn/images/0000000000000000-0/view-00129198/serial] failed May 20 10:07:48 Tower smbd[32664]: [2023/05/20 10:07:48.657620, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 20 10:07:48 Tower smbd[32664]: synthetic_pathref: opening [BILDER/DIV/_MG_1431.CR2] failed This is most likely causing your slow transfers. Couple of things to try: Turn off the macOs Interoperability and see if that makes any difference. I doubt it will. Use Tips and Tweaks to adjust disk caching. If you left the defaults, you're probably OK. Replace your NIC or add a NIC.. You are using s Realtek NIC and they are known to be troublesome with Linux because the drivers are not well maintained.

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've added a Recycle Bin setting to hide the .Recycle.Bin folder in the next release.