On 3/26/2025 at 2:28 AM, mgutt said:

I already tested this. No problem so far as those QVO SSDs have a low power consumption and in addition the default airflow keeps them already cool enough. But I repeat the test next week as then 6 additional SSDs will be connected since the last test.

 

Is there a specific reason why the Auto Fan plugin does not use the CPU temps? I would like to use all temp sensors.

Autofan was designed to be hdd based, if you want to use cpu or other sensors use a board with ipmi

I can pick only 1 Network Interface, is it possible to pick multiple to monitor them at the same time?

Thanks!

On 11/12/2024 at 4:51 PM, spl147 said:

if you did your homework you would have your answer. on unraid open the terminal and run sensors-detect to see if your board is supported.

 

post the output

 

 

So, I've tried to do my homework and follow along in this thread for a while.  170+ pages gets a bit overwhelming.

 

I've run the sensors-detect and gone through all the steps and now I'm presented with this last bit of info:

 

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

 

 

How do I start the lm_sensors service??

2 hours ago, CoZ said:

 

 

So, I've tried to do my homework and follow along in this thread for a while.  170+ pages gets a bit overwhelming.

 

I've run the sensors-detect and gone through all the steps and now I'm presented with this last bit of info:

 

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

 

 

How do I start the lm_sensors service??

No need, post the full output of sensors detect

1 hour ago, spl147 said:

No need, post the full output of sensors detect

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'...               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'...               Yes
Found unknown chip with ID 0x0101

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...       Success!
    (confidence 6, driver `lm78')
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
Found unknown SMBus adapter 8086:43a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
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)

Next adapter: i915 gmbus dpa (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc1 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc2 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc4 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc5 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc6 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AUX C/DDI C/PHY C (i2c-10)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AUX D/DDI D/PHY D (i2c-11)
Do you want to scan it? (yes/NO/selectively): yes


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)

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9)

 

7 hours ago, CoZ said:

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'...               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'...               Yes
Found unknown chip with ID 0x0101

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...       Success!
    (confidence 6, driver `lm78')
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
Found unknown SMBus adapter 8086:43a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
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)

Next adapter: i915 gmbus dpa (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc1 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc2 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc4 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc5 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc6 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AUX C/DDI C/PHY C (i2c-10)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AUX D/DDI D/PHY D (i2c-11)
Do you want to scan it? (yes/NO/selectively): yes


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)

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9)

 

Ok,

run modprobe coretemp nct6775

15 hours ago, spl147 said:

Ok,

run modprobe coretemp nct6775

I'm not getting anything back at all in the CLI

Would it be possible to get the System statistics page to have a Graph showing Temperatures? I am mainly looking for drive temps. Or is there a way currently to get historical drive temps?

I have also an odd problem with System Temperature plugin, it puzzles me a bit.

It was working for a short time but suddenly after a reboot (I think I was installing the newest intel microcode that time) I see the fans twice and some temperatures look wrong:

 

216 °C for PICe x1 and M2_1?

 

Here are the fans:

 

I can uncheck either the upper or the lower 2 but they are checked automatically again.
If I uncheck all 4, they stay unchecked.

 

Now, if I unload the driver above, I still see temperatures that I can select, but only 2 fans are left. Some temperature entries are missing with unloaded driver.

 

To actually see anything in the drop down menus I had to install the Nuvoton NCT6687 Driver first, but now it somehow works without loading it?

 

On 1/31/2025 at 4:16 AM, kaneda79 said:

Hi, I'm having problems with system auto fan on Lincstation N1.

Whenever I shutdown/power on or reboot the device the fan doesn't work until I fake a modification in the Dynamix Auto fan plugin settings

 

The auto fan plugin starts at power on, because I've added the following script to the go file:

# Start Dynamix Auto Fan Control plugin
/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan start &>/dev/null.

 

Under /boot/config/plugins/dynamix.system.autofan/ i have the config file dynamix.system.autofan1.cfg, with the following configuration (thanks to the forum i know pwm3 is the right one to use):

options="-c /sys/devices/platform/it87.2608/hwmon/hwmon6/pwm3 -f /sys/devices/platform/it87.2608/hwmon/hwmon6/fan3_input -l 5 -t 33 -T 60 -m 5 -e sdc"
service="1"
controller="/sys/devices/platform/it87.2608/hwmon/hwmon6/pwm3"
fan="/sys/devices/platform/it87.2608/hwmon/hwmon6/fan3_input"
pwm="5"
low="33"
high="60"
interval="5"
exclude="sdc"

 

The cfg file is automatically named "dynamix.system.autofan1.cfg" because there is a pwm2 before the one in use.

I did try to fake a configuration of the pwm2 (read somewhere that the plugin doesn't work if the first pwm of the list is not configured), but it didn't work.

 

Uninstalled, cleared the config files, installed again and configured, still no joy.

 

Is there a solution or an alternative plugin to manage the fan?

Is there any hope for this bug being patched anytime soon? Or is adding a script to the go file the only solution? Same issue where I have to manually start auto fan whenever the system reboots.

@mattalat I temporarily solved the problem following the solution provided by @spl147 

On 1/31/2025 at 2:40 PM, spl147 said:

stop fan control, delete dynamix.system.autofan2.cfg rename dynamix.system.autofan1.cfg to dynamix.system.autofan.cfg, remove the line from the go script. then reboot, then start fan control

 

Sadly is not working anymore. Only a manual intervention restores the fan behaviour. Probably something changed after the last unraid update.

Edited April 22, 20251 yr by kaneda79

Can anyone recommend a separate PWM fan controller that is supported by the Dynamix plugin? It seems to me that people combine the two topics of sensors and fan control, yet they appear to be quite distinct for many of us. I had no issue getting my motherboard sensors to be detected so I can get those values without issue.

 

What I cannot do is figure out how to control the fans, as they are PWM fans plugged into the motherboard PWM headers but the PWM controller is not detected by UnRaid / Dynamix. Therefore, I cannot script or auto-control the fans.

 

I'm more than happy to buy a separate PWM controller (PCI or USB based) but cannot find any materials telling me what unRaid or Dynamix actually support.

plugin seemed to stop working since the last 7.1.0 update. fans do not stop spinning. did not change anything else except update unraid.

On 4/22/2025 at 2:25 PM, kaneda79 said:

@mattalat I temporarily solved the problem following the solution provided by @spl147 

 

Sadly is not working anymore. Only a manual intervention restores the fan behaviour. Probably something changed after the last unraid update.

I can confirm the update broke this great plugin (at least for me) and it does not control the fans anymore.

 

maybe @bonienl can take a look at this issue?

Edited May 9, 20251 yr by naddel81

On 3/25/2025 at 8:38 PM, mgutt said:

After disable and enable the first sensor it works as expected again. Settings:

 

 

@bonienl can this be fixed easily?

Edited May 10, 20251 yr by naddel81

At the moment I am very much time constraint to look into this, but keep it on my todo list.

 

Previously, in my Unraid or other Linux distro, using sensor-detect showed the driver as lm78 but failed to detect the PWM controller but only temps. Recently, when I booted the server using Windows, I discovered through AIDA64 that the sensor chip wasn't lm-series but a different one. After loading the correct driver in Unraid, the PWM controller was finally detected.

can someone explain me if it is normal that the fan control always shows "Status: Stopped"

This specific "app" has now been Blacklisted and will not function. 

On 5/12/2025 at 5:43 AM, Stephan M. said:

can someone explain me if it is normal that the fan control always shows "Status: Stopped"

No, it should be started. On 7.0.1 this is accomplished by disabling and then enabling the fan control function again. Some people reported it might be broken completely on 7.1.2. Can you confirm? I'm on 7.0.1 and afraid to upgrade now haha

On 5/9/2025 at 6:41 AM, naddel81 said:

I can confirm the update broke this great plugin (at least for me) and it does not control the fans anymore.

 

maybe @bonienl can take a look at this issue?

Does disabling fan control and re-enabling make it work again? This was a known issue 7.0.1 and earlier. Or is it broken completely now?

5 hours ago, mattalat said:

Does disabling fan control and re-enabling make it work again? This was a known issue 7.0.1 and earlier. Or is it broken completely now?

works for me on 7.1.2. I just wish it could be fixed soon. it was a great plugin. and sadly there is no alternative now for unraid.

On 5/12/2025 at 5:17 AM, MrWallopy said:

This specific "app" has now been Blacklisted and will not function. 

It certainly isn't, and checking it is available without any blacklist...

 

Checking back on the history, and the reason for the spurious blacklist flag was due to a GitHub issue where it (for 2 hours) didn't follow a redirected URL.

Is there a way to turn logging off for this plugin? I find the syslog hard to parse now and want to disable the messages.

On 5/20/2025 at 7:55 PM, Scheev said:

Is there a way to turn logging off for this plugin? I find the syslog hard to parse now and want to disable the messages.

Which plugin?