IamSpartacus

I don't have the ramping issue, that is usually resolved by fixing your thresholds which is pretty easy to do. My issue is it seems I can't use the Fan Control in Unraid because any time it attempts to interact with the fans it forces Supermicro to change it's fan mode to full speed.

So I bought a new Supermicro motherboard and this plugin doesn't appear to interact with the BMC correctly. As soon as I enable Fan control, it automatically changed the Fan Mode in SuperMicro's IPMI settings to Full Speed. If I then change that to Standard or Optimal, the fan's return to normal operation as per SuperMicro's settings but do not adjust as per the fan control settings in Unraid. Has this happened to any one else in the past and know of a work around?

Yes that was one of the first things I tried since it was a quick and easy try. No dice.

Didnt think of that. I am doing PCIE ACS override and isolating some cores.

I see there was this on 10-22. My guess is you are right and AMD broke something. Hopefully it gets patched in a future kernel firmware update. 2019-10-22 linux-firmware: Update AMD cpu microcode20191022

Ahh, it is unassigned and the letter did change I believe. Good to know.

Is there a way to suppress this notification? I continue to get notified of it no matter how many times I acknowledge it. They are not new errors as the relocated sector count is at 1 and hasn't changed since I got the original error.

Not an option, latest BIOS version fixed a major issue so it's not worth even going down that path.

Just tried GUI mode, no dice. Reset the CMOS, no dice. I'm on the latest version of my BIOS which is pretty new. I'm stuck on RC3 for the foreseeable future.

It's definitely not pingable, I'm watching the system via IPMI and it just resets the server completely back to the BIOS screen.

Fresh install with the same USB did not work. Trying a fresh install with a new USB. That should tell me if it's some kind of comparability with the new kernel. I am running an EPYC 7302p system so maybe it's too new for the kernel? RC3 works without issue though. I should also note I had this same issue trying to upgrade to RC4 so that's when the change that is affecting me happened. EDIT: Yup, even a brand new USB with a fresh install of RC5 won't boot. Guess I'm stuck on RC3. Will providing diagnostics while RC3 is installed help in any way?

I've tried the update 3 times (with copying previous back to flash each time). Also tried booting to safe mode, no difference. But yea I'll do a checkdisk on the flash. EDIT: Windows found no errors on the flash drive with a chkdsk. Is there any where I can directly download RC5 so I can install it fresh on a USB to test? EDIT 2: Found the direct DL link. Gonna test installing it fresh.

I'm unable to upgrade from RC3 to RC5. My server reaches the Unraid boot screen (see attached) and just resets. It just continuously does this. Should I post diagnostics when I do the upgrade but pre reboot?

Has anyone successfully passed smartctl through to a docker container?

Trying to get telegraf to read nvme temps and hddtemp doesn't appear up to the task. Unraid is doing it somehow so curious what it's using to determine those temps. Is it just smart data?

Is it possible to run two backups on a schedule? Ideally I'd like to run one weekly backup encompassing all appdata and then a daily that only encompasses the "vital" appdata.

Wow, I've had that plugin forever and never noticed the docker update tab. Thanks.

Ahh yes my apologies I forgot there wasn't an auto update for containers, I was mistaking that setting for the plugin's setting. But either way, my request still stands as I'd love to be able to auto update on a per container basis.

I'd love to be able to use auto update of most of my docker containers. The problem is I have a handful of docker containers that I consider "production" and can't afford a bad docker update to break things. So I currently can't have auto update enabled because it's an all or none setting right now. I'd love there to be another column in the Advanced display on the docker tab that allows for one to check on/off auto update for each container.

Yes but what do they each do is my question? It's a plugin that allows for further tuning of the mover. These are the settings I'm using and I'm not having any issues with the mover affecting the rest of my system since upgrading to rc1. Before 6.8rc1 I was having lots of issues.

Is there any info on what each of the different options in `Tunable (scheduler)` are supposed to do?

I have 4 streams going right now including a 4k direct play (over 100Mbps bandwidth). I started the mover and none of the streams are being affected. I'm running rc3 currently. I will test parity check next but need mover to finish because I have mover set to be disabled during parity checks. I have the mover tuner plugin set to enable turbo write during moves so all my disks are spun up and being read at over 160MB/s during the mover process and still no streams are being affected. EDIT: Can confirm parity check does not affect my streams either.

Did you have the same issue in 6.8rc1-3? When I upgraded to rc1 it seemed to fix my issue and I'm now running rc3 with no issues.

Make sure your CPU Scaling Governor is not set to Power Save if you're using the Tips and Tweaks plugin. I found that while that setting is supposed to keep the CPU frequency at it's lowest setting regardless of load, in 6.7.x and earlier it was actually still ramping up the CPU frequency on demand. Now in 6.8 is keeps the CPU at the minimum frequency. I've since set the governor to On Demand and it's working as expected. I've heard of other users with very power system performance in 6.8 with the CPU Scaling Governor set to Power Save and switching to On Demand fixed it.

It appears the CPU Scaling Governor "Power Save" setting no longer is functioning in 6.8. It keeps the CPU scaled down and does not ramp it up on load. I have to set to "On Demand" for it to scale up.