dlandon

You will probably see the CPU Scaling governor driver says "intel_cpufreq" driver on the right side of Tips and Tweaks. This appears to be a new driver for some Intel CPUs. I am working on a change to Tips and Tweaks so this driver will be handled properly. That's why you are not seeing Turbo Boost as an option. Right now it only shows as an option for the intel_pstate (Intel Pstate in Tips and Tweaks) driver. It is recommended that you use 'Performance' for the best power savings and performance. I don't believe "On Demand" is an option to the intel_cpufreq driver. Tips and Tweaks is showing it as an option and probably shouldn't.

You'll notice off to the right the CPU Scaling driver is intel_cpufreq. This is apparently a new governor for some Intel CPUs and replaces the intel_pstate driver. Tips and Tweaks is not setup for the intel_cpufreq driver. I am adding that driver and will issue an update once it is tested.

Yes.

Neither. It would be best done as a feature request for Unraid.

There's a problem with redis in the docker. I'm working on an update and will release it soon.

The UD plugin only manages the 'Unassigned Devices' tab. The Dashboard is stock Unraid and not managed by UD,

Post diagnostics.

The display of UD devices is controlled by the 'Disks', 'Shares', and 'Historical' switches in the upper right. See if changing them shows the devices.

Remove and re-install the docker, or force update the docker.

Your config.php should have these lines: 'filelocking.enabled' => true, 'memcache.locking' => '\\OC\\Memcache\\Redis', 'redis' => array ( 'host' => '/var/run/redis/redis-server.sock', 'port' => 0, 'timeout' => 0.0, ),

Post diagnostics.

You can clean it up manually, but reboot is the easiest way.

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.