Dynamix - V6 Plugins


bonienl

Recommended Posts

Auto Fan Control stopped working on Asus Z390M-PLUS (NCT6796D / NCT6798D) when upgrading to 6.8.x

I built my third UnRAID server last summer running with version 6.7.1. Out of the box most sensors were not detected (eg. the fan speeds), only temperatures were. After a quite a bit of reading in this thread and else where I managed to understand that I needed to manually load the correct driver module with command "modprobe nct6775" which I also put to my go file to make it persist over boot. Everything was fine from sensors perspective and Auto fan control was working pretty nicely (except for the nvme exclusion issue).

 

I recently discovered that the Auto Fan Control had stopped working at some point. It's been several months since I updated to 6.8.x but I suspect it stopped working at that point. I've made zero changes to core/plugin settings in between, only adding/changing dockers.

 

Any help is well appreciated. This is a really long post but it is mostly debugging info for the devs. It could well be that this will be solved when moving to 5.x kernal with Unraid 6.9.

 

This is how it shows in the UI comparing 6.7.x and 6.8.3. I took the 6.7.x screenshot last summer when I got it working. Unfortunately I did not take notes about the results of "sensors" or "sensors-detect" outputs or any other debugging I did back then.

 

6.7.x Fan Auto Control UI

image.thumb.png.a8040b742ef713bce42805180022e7a7.png

 

 

6.8.3 Fan Auto Control UI

image.thumb.png.ca0ede29aae22f59f552c8b4ab2464d7.png

 

Some facts:

  • Unraid 6.7.x included lm-sensors 3.5.0 which added support for "Nuvoton NCT6796D" detection.
  • Unraid 6.8.0 included lm-sensors 3.6.0 which adds support for "Nuvoton NCT6798D " detection.
  • sensor-detect actually now detects my chipset "Found `Nuvoton NCT6798D Super IO Sensors' Success!(address 0x290, driver `nct6775')"

What I'm confused / unsure of:

  • Which sensors my Z390M-PLUS actually has, Nuvoton NCT6796D or Nuvoton NCT6796D? 6.7.x said it was NCT6796D as some other internet sources but now in 6.8.3 it is detected as NCT6798D.
  • "modprobe nct6775" seems to run fine, there are no error messages displayed like in this report from 5.4/5.5 kernel version.
  • Dynamix System Temp plugin change log states on 2019.11.03 "Do not load script 'sensors-detect' when Unraid version is 6.8 or higher". There is no similar change on Dynamix System Autofan plugin change log.

6.8.3 sensors output

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +119.0°C)

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:       +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:       +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:       +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:       +44.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:       +45.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:       +44.0°C  (high = +82.0°C, crit = +100.0°C)

 

6.8.3 sensors-detect output (the first two essential parts)

# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. PRIME Z390M-PLUS
# Kernel: 4.19.107-Unraid x86_64
# Processor: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz (6/158/10)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6798D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

6.8.3 lsmod | grep "nct6775\|coretemp"

root@TMS-740:~# lsmod | grep "nct6775\|coretemp"
nct6775                53248  0
hwmon_vid              16384  1 nct6775
coretemp               16384  0

6.8.3 modinfo nct6775

root@TMS-740:~# modinfo nct6775
filename:       /lib/modules/4.19.107-Unraid/kernel/drivers/hwmon/nct6775.ko.xz
license:        GPL
description:    Driver for NCT6775F and compatible chips
author:         Guenter Roeck <linux@roeck-us.net>
depends:        hwmon-vid
retpoline:      Y
intree:         Y
name:           nct6775
vermagic:       4.19.107-Unraid SMP mod_unload
parm:           force_id:Override the detected device ID (ushort)
parm:           fan_debounce:Enable debouncing for fan RPM signal (ushort)

6.8.3 "modprobe -r nct6775", "modprobe nct6775", "dmesg | grep nct6775"

root@TMS-740:~# modprobe -r nct6775
root@TMS-740:~# modprobe nct6775
root@TMS-740:~# dmesg | grep nct6775
[   54.436001] nct6775: Enabling hardware monitor logical device mappings.
[   54.436046] nct6775: Found NCT6796D or compatible chip at 0x2e:0x290
[ 2567.110309] nct6775: Found NCT6796D or compatible chip at 0x2e:0x290

 

Edited by henris
Link to comment
On 4/13/2020 at 7:10 AM, henris said:

Auto Fan Control stopped working on Asus Z390M-PLUS (NCT6796D / NCT6798D) when upgrading to 6.8.x

 

 

Same here except I have a SuperMicro X9SRL-F and am on Unraid 6.8.2 and the bad behavior started after updating dynamix.system.autofan from the previously working 2017.10.15 version.

 

It's worth noting I saw and reported this kind of behavior before last year.  In those cases it seemed to be related to changes in Unraid (6.7.0) 

 

Either way none of the reports here were acknowledged.  See posts 1234

 

Same as before I am reverting to unraid-fan-speed.sh called from the User Scripts plugin. 

 

The best and most helpful write up I found implementing unraid-fan-speed.sh from another user also noting the broken Dynamix System AutoFan, is here.

 

One additional oddity in behavior with dynamix.system.autofan 1.6 on my system is that after entering a stopped state I set the plugin to disabled and sometime after that the plugin state changed to running again.

 

 

dynamix auto fan broken 01.PNG

Edited by dabl
Link to comment

I have a ASUS Z170 PRO GAMING and cant see any status of my new PWM fans. I've changed the fans in BIOS from DC to PWM.
I've run sensors-detect and also tried with https://github.com/lm-sensors/lm-sensors/blob/master/prog/detect/sensors-detect
I've added modprobe coretemp and modeprobe nct6775 to the "go"-file. Still nothing :(. Ideas?

root@Tower:~# pwmconfig
# pwmconfig version 3.6.0

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed


EDIT. Unraid 6.8.3

Edited by Daggr
Link to comment

Fan speed is changing speed very often and setting for refresh interval is not working

 

my fans are switching speed 2 or 3 times a minute.

and when i go into Fan Auto Control it show as disabled. but running.
i just did a reinstall of the plugin.

From log :
Apr 16 23:11:40 UNRAID autofan: Highest disk temp is 35C, adjusting fan speed from: 70 (27% @ 390rpm) to: OFF (0% @ 356rpm)

Apr 16 23:12:25 UNRAID autofan: killing autofan process 25151

Apr 16 23:12:25 UNRAID ool www[25734]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start'

Apr 16 23:12:25 UNRAID autofan: autofan process ID 22862 started, To terminate it, type: autofan -q -c /sys/devices/platform/nct6775.656/hwmon/hwmon2/pwm2 -f /sys/devices/platform/nct6775.656/hwmon/hwmon2/fan2_input

Apr 16 23:12:31 UNRAID autofan: Highest disk temp is 35C, adjusting fan speed from: FULL (100% @ 355rpm) to: OFF (0% @ 363rpm)

Apr 16 23:14:24 UNRAID autofan: killing autofan process 22862 Apr 16 23:14:33 UNRAID ool www[25734]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start'

keep repeating itself.

i have tried detected "Minimum PWM value:" and setting it lower like 50.
its  really anoying to hear fans ramp up and down all the time...  

 

But great work... really like Unraid and all the work you guys do.
i have run Dynamix System Autofan for over a year on this system now.. first time i have had issues.

Edited by mdsloop
Link to comment
17 hours ago, mdsloop said:

Fan speed is changing speed very often and setting for refresh interval is not working

my fans are switching speed 2 or 3 times a minute.
...
i have run Dynamix System Autofan for over a year on this system now.. first time i have had issues.

Is your motherboard made by Supermicro?  

Link to comment
2 hours ago, mdsloop said:

its an old asus H87-PRO with an i5-4570S CPU and 16GB RAM

Ok, well then this may or may not apply but I had the same sort of thing happen with my Supermicro motherboard which has a feature in the bios that cannot be shut off that wants to try and control the fans.  For unknown reasons after updating to unraid 6.8.2 my fans started behaving like yours.  This is a  known problem with some Supermicro motherboards caused by the bios thinking the fan (now otherwise being controlled by another piece of fan control software) has started spinning at too low an rpm and taking over to make it run faster.  Then the other fan control software sees this and combined with an otherwise ok temp it tries to slow the fan down. Rinse and repeat. So the bios is fighting the other fan control software, in this case the dynamix plugin.  I solved it by running a Supermicro specific utility (IPMITOOL) to lower the threshold of the fan rpm that would cause the bios to worry and take over.  No idea why I needed to do that all of a sudden though after a long time of things running fine using the dynamix plugin.  Per previous reports it seems changes in unraid can cause different behavior with the dynamix fan plugin. 

 

I'm currently running unraid 6.8.2 and reverted back to the 2019.11.03 dynamix.system.temp and 2017.10.15 v1.5 dynamix.system.autofan for the same good fan behavior I had before.  I wanted to at least get a sanity check before updating to unraid 6.8.3

Edited by dabl
Link to comment

Can´t readout the temp with ur plugin of my 3950x on a b450-prime or my new X570-F gaming, both from asus.

When im in the settings of the plugin i click detect and its saying k10temp nct6775 but there are no sensors for me not the cpu either the mainboard...

But worked flawless on my ryzen 2700 before...

Link to comment

apparently there is no fix for x570 boards..  there is another forum where they working on a driver for asus x570 boards but currently there is no fix current version of unraid  and x570... something to do with how the kernel reads  sensors   doesnt work...  and from what they were working on  current kinda fix  puts x570 in constant reboot mode..  so nothing as of a couple days ago from the people working on a wmi driver plugin fix

Link to comment

Good morning!

About cache-dirs (Folder Caching), I never managed to make it work!

All in the GUI: I tried chaging the pressure, excluding folders, including folders, changing the depth

But everytime I open a share (when disks are spun down), it takes 10 seconds to load all folders.

Any thoghts?

Thanks

Link to comment

Is any body lucky using Mapquest for Day/Night ? Mapquest makes it easiest to get an account and an API key.

However, unfortunately I always get "No geographical coordinates found for the given address. Please adjust.", no matter what address I put in.

Somebody luckier with MapQuest?

 

Maybe this is the reason: Mapquest seems to be really bad at locating addresses outside of the US.

 

PS: Bing did work but it was a lot more effort to get an account.

 

 

Edited by b0m541
Link to comment

Just noticed that Dynamix cache dirs is listed as beiing not known to Community Applications.. Seems like an error ?  Probably one of the plugins almost everyone is using ?

 

Issue Found: dynamix.cache.dirs.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.

 

Link to comment
On 4/13/2020 at 9:10 PM, henris said:

Auto Fan Control stopped working on Asus Z390M-PLUS (NCT6796D / NCT6798D) when upgrading to 6.8.x

I just did a new build (actually my first use of Unraid and went with 6.8.3) and unfortunately that is the exact motherboard I used as well and I have exactly the same issue with Autofan. For now I've just set a fixed curve in the BIOS but obviously that isn't using the HDD temps so looking forward to the issue being fixed. Given it was working in an earlier version at least it doesn't seem to be anything fundemental.

Link to comment

Hi, 

 

I have just built a backup server using an Asrock X470 Taichi and 3600X CPU and the temps are not reporting correctly (CPU always -62.5) and the others don't budge even when encoding a video.  Is this not working for this combination yet or is there anything I can do?

 

M/B: ASRock X470 Taichi Version - s/n:

BIOS: American Megatrends Inc. Version P3.90. Dated: 01/10/2020

CPU: AMD Ryzen 5 3600X 6-Core @ 4000 MHz

HVM: Enabled

IOMMU: Enabled

Cache: 384 KiB, 3072 KiB, 32768 KiB

Memory: 16 GiB DDR4 (max. installable capacity 128 GiB)

Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: 1000 Mbps, full duplex, mtu 1500

Kernel: Linux 4.19.107-Unraid x86_64

OpenSSL: 1.1.1d

 

image.png.425abecae2d24f7168abc3fee5e87d6f.png

 

 

 

Link to comment
  • 2 weeks later...

Hi there,

 

I just want to set up a simple scheduled sleep - see attached screenshot. 

My plan is, that my server wakes up by WOL or Bios-RTC - what ever comes first. 

Then running until 24:00 (excluded hours from 15:00 until 24:00)

And - after 24:00 AND an inactivity of the IP 192.168.1.240 (my iMac) AND after a delay of 30 minutes the server should go to sleep.

 

But that dont work and I cant see the problem. Yesterday I shut my iMac down at about 23:30.

So - if I understand it right - it should run until 00:01 and then starting the timer (30 minutes delay) so it should go to sleep at 00:31.

But as I woke up today (06:00) the server was running. 

 

I appreciate any help - thank you and have a nice weekend. 

Bildschirmfoto 2020-05-09 um 20.45.52.png

Link to comment

The latest system plugin update needs to have the max version changed:

PACKAGE DESCRIPTION:
Package dynamix.system.temp.txz installed.
Package dynamix.system.temp upgraded with new package /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz.
plugin: skipping: sensors-detect - Unraid version too high, requires at most version 6.7.2
plugin: skipping: sensors-detect - Unraid version too high, requires at most version 6.7.2

 

Link to comment

Hi all, System Temp doesn't seem to have drivers for my motherboard's temperature sensors (Gigabyte Z390 M Gaming - ITE IT8688E). Here's the "sensor-detect" output:

 

Quote

# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. Z390 M GAMING [Default string]
# Board: Gigabyte Technology Co., Ltd. Z390 M GAMING-CF
# Kernel: 4.19.107-Unraid x86_64
# Processor: Intel(R) Core(TM) i7-9700T CPU @ 2.00GHz (6/158/13)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')

Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8688

Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): YES
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Using driver `i2c-i801' for device 0000:00:1f.4: Cannon Lake-H (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

 

Here's the "sensors" output:

Quote

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +38.0°C  (high = +92.0°C, crit = +100.0°C)
Core 0:       +38.0°C  (high = +92.0°C, crit = +100.0°C)
Core 1:       +37.0°C  (high = +92.0°C, crit = +100.0°C)
Core 2:       +36.0°C  (high = +92.0°C, crit = +100.0°C)
Core 3:       +35.0°C  (high = +92.0°C, crit = +100.0°C)
Core 4:       +39.0°C  (high = +92.0°C, crit = +100.0°C)
Core 5:       +35.0°C  (high = +92.0°C, crit = +100.0°C)
Core 6:       +38.0°C  (high = +92.0°C, crit = +100.0°C)
Core 7:       +36.0°C  (high = +92.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
MB Temp:      +27.8°C  (crit = +119.0°C)

 

I set ACPI Temp 2 as MB Temp, but I have no idea if that's correct. I in fact have no idea what those 2 ACPI tempeatures are. The motherboard has 6 thermal sensors and 4 fan headers:


smart-fan5.jpg

 

Furthermore, under "Array Fan Speed" in Dynamix System Temp, I'm not able to select anything at all.

 

Any help would be appreciated.

Link to comment

@bonienl - Thanks for the hint. My log is full of this information.

Quote

Wed May 13 14:58:54 CEST 2020: Disk activity on going: sdc

 

In general this info is pretty clear - my parity drive got disk activity - fine.

But that brings me to next question. Why? 

It looks like the parity drive got a 24/7 activity... There (in the log) is not even a second in one of the times that could be run into sleep, where there is no activity. It must be a failure... 

 

I checked my settings of the parity check - but this is scheduled to monthly (first day). 

What else can cause this permanent activity? Any ideas?

 

Thanks again

Link to comment
1 hour ago, bonienl said:

Do you have any docker containers or VMs running?

Yes - a Pi-Hole docker and a plex docker. But I set the docker to "work" on the cache. So in my opinion there should be no writes to the array.

But maybe plex is scanning the folders constantly? The media folders are on the array.

 

I'll stop pi-hole and plex docker tonight, to make sure, that none of these are writing anything to the arra.

1 hour ago, bonienl said:

Check if the parity disk has a spin down time set.

Sorry - I'm new to unRAID. Where can I check this? 
 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.