dlandon

When looking at the diagnostics, I see the Multichannel feature of SMB is enabled. That feature requires two NICs and special setup to work properly. I suggest turning it off and see if it helps.

After some research, it seems the turbo control is planned, but not ready yet for the amd-pstate-epp driver. In the meantime, you can disable the amd-pstate-epp driver using this procedure: Go to a command line and enter this command: 'echo "blacklist amd-pstate-epp" > /boot/config/modprobe.d/amd-pstate-epp.conf'. Reboot Unraid. You should see the ACPI CPU Freq driver that will allow turbo control.

The 'amd_pstate' is new and the boost might not be implemented yet. Give me the output of this command: cat /sys/devices/system/cpu/amd_pstate/cpb_boost if that file is there, the boost should be configurable.

Yes. Install the recycle bin plugin and set the the "Recycle Bin Parameters" for what you want to show for a deleted file. Click on the 'Help' icon in the upper right corner of the recycle bin page to see some options. Currently the logging is not working reliably because of some samba changes, but I will have that fixed soon.

Why do you want to do that?

I don't know what you are trying to do, but putting settings in the global section is not a good idea and will override any share settings. No.

Give me the output of this command: ls /sys/devices/system/cpu/amd_pstate/

That should mean turbo mode is off. I need the info from Unraid 7.0.

Give me the output of this command: cat /sys/devices/system/cpu/cpufreq/boost

Your screen shots show up as a tiny icon and not a screen shot. I don't think screen shots are showing properly in the forum right now. What I need is the driver information. In my case it is "Driver: Intel CPU Freq".

Not that I know of. I can't help with a downloader as LT does not support downloading. Other users may be of some help.

Your screen shots do not show. I believe the CPU Scaling Governor changed with the Linux update in 7.0 and I need to see a screen shot with the CPU Governor showing on the Tips and Tweaks page.

The newer version of Unraid has an updated version of Linux and the CPU driver probably changed and Tips and Tweaks doesn't work with the new driver. On the right side of the page, show the CPU Scaling Driver for 7.0.

You can assign a disk alias. Go to the disk settings (three gears icon) and change the disk name.

I think you have enable disk shares as yes in global share settings. A root share won't work with disk shares enabled.

Your processor does not support boost.

Yes, use the UD unmount command and check the return code. It will be 'success' if it successfully unmounts the drive. Let UD unmount the disk and do the cleanup. A luks disk has to be closed as part of the unmount. If you don't do that you will get the above issue. Go to the UD page and click on the 'Help' icon and you will see how to use the UD 'rc.unassigned' command.

Because of recent changes in Samba, some deleted files are not logged as being deleted but moved. This is actually a good thing if the file doesn't have to actually be copied to the .Recycle.Bin, but can be moved instead - a move is much faster. This causes the plugin logging to miss the fact that a file was deleted from a share. The actual file deletion (file going to the .Recycle.Bin) works, but is not always loggged. The Samba logging mechanism is not easy to work with and I am considering ditching it and possibly using an inotify on each .Recycle.Bin. I'm also considering dropping logging altogether, but I suspect this move might not be well received.

It appears the disk was not unmounted properly because the luks device was not closed. When you try to remount the disk, the luks disk is cleaned up with a close and the next attempt (manually) will succeed. Be sure to unmount the device before removing it with the device script or manually and confirm the disk successfully unmounted. If it is busy and didn't unmount, that will create this situation.

UD used to add the local tld to the tag. Yes, based on what you've said this should have come up last year from an update to UD. Caps don't matter. I thought you said somewhere that your local tld was blank.

Post your diagnostics.

Post your diagnostics.

Post your diagnostics and I'll look into it.

There a few tennents I need to mention: UD does not make any changes to config files unless user initiated. No changes in the latest version of UD would have caused this. Changes were made to UD last year to clean up server names entered by users that caused issues in the tags. A server name entered such as "SERVER.LOCAL" would cause issues in the tag. The ".LOCAL" was removed from the server name in the tag, but left in the "ip" field of the config file so the lookup of the server name would be successful. Changes were made then to indicate an invalid configuration, so a user could tell there was a problem and take action to correct. Part of the reason for the change to indicate an invalid configuration was that users were modifying the config file to try to address a problem with name resolution that has been corrected in UD. Back then the invalid configuration came up a lot when that message was added. These are the ways the invalid configuration can occur: Updating from a very old version of UD to the latest version. Restoring an older samba_mount.cfg file with the incorrect tags. Incorrect user modifications to the samba_mount.cfg file. Since you did not post a diagnostics, I (incorrectly) assumed you updated from an older version of UD because that is normally how this happens. Just as a heads up, the "Local TLD" when blank defaults to "LOCAL". In your case, you should set it to "KNET". Appologies if I offended you, but I am not fond of posts that encourage manually editing config files as mistakes made can create user problems and support issues to be addressed.

Post diagnostics.