dlandon

Reboot.

From what I’ve seen, it’s not a problem with using Jumbo frames, it’s that people don’t set it up right. Your complete network has to be configured for Jumbo frames. I would post separately and ask for assistance on setting up Jumbo frames.

They all look like they are mounted to me. The log shows: Feb 15 09:28:47 UNRAID2 nmbd[5426]: [2021/02/15 09:28:47.368021, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 15 09:28:47 UNRAID2 nmbd[5426]: ***** Feb 15 09:28:47 UNRAID2 nmbd[5426]: Feb 15 09:28:47 UNRAID2 nmbd[5426]: Samba name server UNRAID2 is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Feb 15 09:28:47 UNRAID2 nmbd[5426]: Feb 15 09:28:47 UNRAID2 nmbd[5426]: ***** Feb 15 09:28:47 UNRAID2 nmbd[5426]: [2021/02/15 09:28:47.368139, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 15 09:28:47 UNRAID2 nmbd[5426]: ***** Feb 15 09:28:47 UNRAID2 nmbd[5426]: Feb 15 09:28:47 UNRAID2 nmbd[5426]: Samba name server UNRAID2 is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Feb 15 09:28:47 UNRAID2 nmbd[5426]: Feb 15 09:28:47 UNRAID2 nmbd[5426]: ***** Feb 15 09:28:47 UNRAID2 nmbd[5426]: [2021/02/15 09:28:47.368226, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 15 09:28:47 UNRAID2 nmbd[5426]: ***** Feb 15 09:28:47 UNRAID2 nmbd[5426]: Feb 15 09:28:47 UNRAID2 nmbd[5426]: Samba name server UNRAID2 is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Feb 15 09:28:47 UNRAID2 nmbd[5426]: Feb 15 09:28:47 UNRAID2 nmbd[5426]: ***** \ and Feb 16 15:37:09 UNRAID2 kernel: CIFS: VFS: BAD_NETWORK_NAME: \\UNRAID1\tdarr-cache Feb 16 15:37:09 UNRAID2 kernel: CIFS: VFS: cifs_mount failed w/return code = -2 Feb 16 15:37:09 UNRAID2 unassigned.devices: SMB default protocol mount failed: mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages I think UD is having trouble looking up the server name. Try using IP addresses instead.

This has come up before. Set all devices to default MTU. It can be a challenge to set up a network properly for Jumbo frames, and I doubt you are really getting any throughput advantage. It's not worth the aggravation.

Don't use Jumbo shares. Set MTUs to default.

Are you using Jumbo frames?

The only remote share I see is '//UNRAID2/nextcloud' and it successfully mounted.

Post diagnostics.

New release of Recycle Bin: - Added a permissions setting to set the permissions on the .Recycle.Bin directories. This sets the directory permissions when files are deleted. If you change the permissions setting, all existing directories in the .Recycle.Bin are updated to the new permissions. - Added a confirm check box to enable destructive buttons to help with accidental clicking of empty trash buttons.

That looks like a disk problem. You have physical disks. They will mount to /mnt/disks/, not /mnt/remotes/ regardless of the legacy setting. I've said this before - please read this carefully.

The UD pass through setting is more of a convenience than a requirement. You can pass through a disk any time without the 'Pass Through' switch being on. With it on though, UD will not allow mounting of the disk. If UD mounts a passed through disk, the file system will be corrupted.

Remote shares, not physical disks. Legacy mode maps these to /mnt/disks. Physical disks mount to /mnt/disks/. What doesn't work?

Disks without a file system will not show the settings icon (three gears) as the settings there do not apply.

Click on the settings icon (three gears) and turn off the "Pass through" switch. As for the time out, try another USB port, change the USB cable.

The sdt disk is marked as pass through. UD will not mount a passed through disk. Feb 14 16:04:26 Tower kernel: sd 12:0:0:0: [sdt] Attached SCSI disk Feb 14 16:04:27 Tower unassigned.devices: Disk with serial 'nal_USB_3.0_2015033100081', mountpoint 'TO_Exter_nal_USB_3.0' is set as pass through. Feb 14 16:36:21 Tower unassigned.devices: Error: shell_exec(/usr/sbin/hdparm -C /dev/sdt 2>/dev/null | /bin/grep -c standby) took longer than 10s! The timeout error is UD trying to get the disk standby status. That's probably a USB cable or port issue, or an issue if the disk is in an external bay.

I just looked through the diagnostics and it appears you have assigned USB disks to the array. If that's true, that's not a good idea. I suspect you are also using external drive bays. That might also be a problem.

The diagnostics you gave me only go through Feb 12th. The log snippet you posted was for Feb 14th. Please update the diagnostics to cover Feb 14th and post those.

Delete the /flash/config/plugins/unassigned.disks/unassigned.devices.cfg file, then click on the 'Refresh Disks and Configuration" icon (double arrows in the upper right) and see if it doesn't clear up the automount.

Go to the settings and then turn on and back off the automount. That should clear it up.

Update UD to get the automount switches working properly.

Log snippets are not very useful in troubleshooting problems. Please post diagnostics for better support.

The disk has no file system. You'll need to format it. You'll need to install the Unassigned Devices plus plugin to format it.

Click the 'Mount' button on the UD disk.

You have put your UD devices in the pool. Stop the array and remove them from the pool. You will then see them in the Unassigned Devices.

It doesn't appear to be related solely to unmounting of the disk. I recommend the following: Remove the preclear plugin. Set the drive in question to not automount. Remove the drive in question. USB drives should be unmounted and removed from the system when you reboot. Reboot the server. Plug the USB disk back in and mount it manually. Check the log for errors before unmounting it. I suspect that the drive has some issues. Post diagnostics again if the log has errors. Why are you using EXT4 on the disk?