dlandon

Go to a command line and do this command 'ud_diagnostics'. Then post the /flash/logs/ud_diagnostics....zip'

It's possible you found a corner case. Give me a screen shot of that settings page. Do you have any special characters in the user names?

This should be fixed in the latest version of the plugin.

The plugin has been updated to add the 'AMD Pstate' and 'AMD Pstate EPP' cpu governor drivers. I believe the 'AMD Pstate' driver will allow boost control, but the 'AMD Pstate EPP' driver will not. The EPP driver is an energy efficient driver and it looks like it controls the boost to conserve power. The CPU modes for each driver are: AMD Pstate - performance, powersave, and schedutil. performance → Runs at the highest frequency possible. powersave → Focuses on energy efficiency by using lower frequencies. schedutil → Uses Linux's CPU scheduler to adjust frequencies dynamically. AMD Pstate EPP - powersave, balanced_power, balanced_performance, and performance. powersave → Prioritizes power efficiency. balanced_power → Balances performance and power usage, with a slight bias toward efficiency. balanced_performance → Balances power and performance, but with a slight performance bias. performance → Prioritizes maximum CPU performance. I don't have a system with an AMD processor, so I have limited testing ability. Let me know of any issues that you see.

Yes. That's what I am seeing.

What is your client side mount command?

Why is your eth0 driver "virtio_net"? Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: off Port: Other PHYAD: 0 Transceiver: internal Link detected: yes driver: virtio_net

Do the following: Click on the "Boot Device" tab. Click on the "Flash" text. Click on "Syslinux Configuration". Add the text "amd_pstate=disable" to the "Unraid OS" box. Reboot Unraid.

/var/log/recycle.bin.log and /var/log/file.activity.log

It sounds like your flash device is having problems. Shutdown your server and check the flash in a PC.

I think the best bet will be to remove the driver from the kernel until it is fully implemented.

Try a restart.

If the drive in question is sdc, there is no partition on that disk that I can see. It looks like the disk may also have some SMART issues. Someone with more experience with drives may be able to give you some suggestions.

I've been doing some testing and I think it may work with exclusive shares. I had one situation in my testing where it wouldn't work. That may be a program issue. Still testing.

There is nothing I can do to add user tracking to the file activity. The user is not known to inotify.

It takes a lot to set it up correctly, and I honestly don't think Multichannel offers any advantage on a home NAS.

What I found in my testing is that any exclusive share in a rootshare prevents the recycle bin from working on any shares. There are several choices you have: Don't use exclusive shares if you need the recycle bin and a rootshare. Don't use the recycle bin if the rootshare and exclusive shares are more important. Don't use a root share.

When you edit the file on the flash device, you need to click the double arrows icon on the UD page since the settings on the flash need to be copied to the /tmp/ file system because UD uses the /tmp/ copy to manage UD. This is done to save reads on the flash.

Yes, the exclusive shares will not show in a root share, but with changes in Samba, the recycle bin will not work with exclusive share symlinks in the root share.

I made that change so it would be clear which driver was being used. I don't know why that doesn't work. Check that the file /flash/config/modprobe.d/amd-pstate-epp.conf exists and has the appropriate contents. The driver is not fully implemented yet, so it will not work.

It is working for me. It may be something on your system. Post diagnostics.

The logging in the recycle bin has been converted to inotify. There are several reasons that the logging was not working: Samba has changed files being deleted from 'unlink' to 'moved'. The new inotify watches the share .Recycle.Bins for files moved or created in those folders. After adding a new share, the recycle bin was not updating to add the recycle bin to the new share. Probably a few other issues also. All should be working now.

Probably not for what Tips and Tweaks does. Yes, you will want to remove that entry to re-enable the the amd-pstate-epp driver. I will also have to make changes to Tips and Tweaks to handle changing the turbo mode.

The ports may be open, but with SMB disabled, nothing shoud be responding on those the ports.

There are two plugins that will partially do what you want. You will want to use the plugins and not modify files on your own. The two plugins are the Recycle Bin and File Activity plugins. The recycle Bin plugin can delete files and organize the files in the .Recycle.Bin by user using the %u parameter. The File Activity plugin will trach file activity, but does not track smb file activity separately by user. This is a really bad idea. There are several routines that manage the config file, and anything you do will interfere with smb and cause you problems.