On 1/31/2025 at 10:40 AM, 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

It worked for me too, but I noticed that now the case fan (the one controlled by Autofan) no longer shows the (%) of RPM, just the RPM. Instead, the CPU fan (controlled by BIOS) that is not configured in Autofan, shows RPM and (%)

Hi there,

 

I'm running Unraid 7.0.0 on a Ryzen 5 4600G. When I first installed, I installed Dynamic System Temperature and it detected drivers automatically. I could see CPU and mainboard temperatures, among others.

 

At some point, after a restart or two, all temperatures have disappeared. Now, I go into the plugin, click "detect," and it returns no results.

 

I can run sensors-detect, but that returns the same result.

 

I have reseated the CPU fan header to no avail. Temperatures are being reported to BIOS just fine. I do some heavy workloads and have recently moved to a new case and cooling setup, so really need to know what my temperatures are looking like.

 

The problem has persisted across Unraid 7.0.0 and 7.0.1.

I run Unraid 7.0.1 and wanted to report that for my system, having "isolcpus=0-1" in the boot options caused the Sleep / WOL functions to stop working. The system was hanging on a WOL command, independently of the NIC.

I had to uninstall all plugins, reset everything, and try to set things back one by one, resetting bios, and so on.

Only took me 8H to figure out it was this simple cpu isolation configuration.

It's unrelated to this plugin, but it's where the information will likely be the most useful.

I don't remember adding that option recently, so it could be an update and hardware specific issues that makes it not compatible anymore. Either case, if it can save someone some headache... It's worth checking :).

Edited March 10, 20251 yr by dboris

Dynamix Auto Fan Control

 

I can get the fans controlled, Fan1 - Blows on my drives, Fan2 - Is one of the Case Fans Fan 3: The fan over my AMD 7945 APU.

 

I am having an issue when my drives go idle, the temps drop and the fans stop even though I have the lowest setting to be 15%.  I have had 3 random system shutdowns, that I believe (but not sure) are due to the APU getting hot because Fan 3 stops.

 

I have tried to disable the fan control for Fan 3, but then it runs at 100% non-stop.  Before I installed the fan control plugin, I believe the motherboard was automatically controlling the speed for that fan.  How can I restore this functionality?  Or how can I make it so Fan 3 never goes completely idle?  APU temps getting over 100c when fans go idle.

Edited March 13, 20251 yr by rbarr110

47 minutes ago, rbarr110 said:

Before I installed the fan control plugin, I believe the motherboard was automatically controlling the speed for that fan.  How can I restore this functionality?

should stay BIOS controlled as long you are not configuring it in the plugin, removing fan3 config ... reboot ...

 

48 minutes ago, rbarr110 said:

Or how can I make it so Fan 3 never goes completely idle? 

may some way (same page upper post)

 

48 minutes ago, alturismo said:

should stay BIOS controlled as long you are not configuring it in the plugin, removing fan3 config ... reboot ...

 

may some way (same page upper post)

 

Thank you for the reply, especially the REBOOT part.  Fan appears to be being controlled again by the motherboard.

7 minutes ago, rbarr110 said:

especially the REBOOT part.

yep, once the OS took control its hard to give control back to BIOS without a reboot

20 hours ago, rbarr110 said:

even though I have the lowest setting to be 15%.

It's common for fans to need at least 30-35% to start/keep running, need to test with yours.

SYSTEM AUTOFAN

 

I've been using this for a while, following a MOBO change, I have been diving more into its operation.

 

I have 2 Fans on drives. The top is on a block of 5 array drives, the bottom is on a block of 5 drives the parity, a passed drive and an SSD pool. The MOBO has 2xNVME Drives on it.

 

I was expecting the plugin to:

check the top fan PWM3 drives as set in the 'exclude drives' and set that fan

THEN

check the bottom fan on PWM4 drives again as set in 'exclude drives' and set that fan.

 

The script seams to check all the drives not excluded and then set both fans. For example in my have SDH and SDK are at the bottom so should only be on PWM4 ... PWM3 drives are all spun down so should be at 0%

 

Note: I have modified the script to report the max temp drive and fan controller to find this

 

Question : should the plugin separately control each fan based on the drives included in that PWM group?

 

 

 

1 hour ago, MrAndyBurns said:

SYSTEM AUTOFAN

 

I've been using this for a while, following a MOBO change, I have been diving more into its operation.

 

I have 2 Fans on drives. The top is on a block of 5 array drives, the bottom is on a block of 5 drives the parity, a passed drive and an SSD pool. The MOBO has 2xNVME Drives on it.

 

I was expecting the plugin to:

check the top fan PWM3 drives as set in the 'exclude drives' and set that fan

THEN

check the bottom fan on PWM4 drives again as set in 'exclude drives' and set that fan.

 

The script seams to check all the drives not excluded and then set both fans. For example in my have SDH and SDK are at the bottom so should only be on PWM4 ... PWM3 drives are all spun down so should be at 0%

 

Note: I have modified the script to report the max temp drive and fan controller to find this

 

Question : should the plugin separately control each fan based on the drives included in that PWM group?

 

 

 

not many fans can do 0% 27% seems to be your lowest

10 minutes ago, spl147 said:

not many fans can do 0% 27% seems to be your lowest

That's true, I was possibly expecting a full stop at 0% as the drives were off.

 

I've also noticed that I'm not actually able to exclude Unassigned drives as they are not in the list ... just looking at options to see if I can include those

1 minute ago, MrAndyBurns said:

That's true, I was possibly expecting a full stop at 0% as the drives were off.

 

I've also noticed that I'm not actually able to exclude Unassigned drives as they are not in the list ... just looking at options to see if I can include those

Just go to the config file to add them

1 hour ago, spl147 said:

Just go to the config file to add them

Thanks @spl147, I did put it in the /boot/config/plugins/dynamix.system.autofan PWM config file, it didn't work and then got overwritten when I restated the service to see if this fixed it... just checked a few hours later and it did work, but then it has litterally just picked up the excluded drive again ... I'll continue to monitor 🤪

5 minutes ago, MrAndyBurns said:

Thanks @spl147, I did put it in the /boot/config/plugins/dynamix.system.autofan PWM config file, it didn't work and then got overwritten when I restated the service to see if this fixed it... just checked a few hours later and it did work, but then it has litterally just picked up the excluded drive again ... I'll continue to monitor 🤪

the plugin is kinda half baked, and doesnt get enough attention to be honest, a board with IPMI is the way to go for full fan control

The Auto Fan Control plugin does not recognize the correct maximum temperature?!

 

 

EDIT: Ok, this is really bad:

1 hour ago, mgutt said:

The Auto Fan Control plugin does not recognize the correct maximum temperature?!

 

 

EDIT: Ok, this is really bad:

post your settings page

3 hours ago, spl147 said:

post your settings page

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

 

I would say the plugin does not recognize hot swapped disks?!

 

4 minutes ago, mgutt said:

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

 

I would say the plugin does not recognize hot swapped disks?!

 

Your refresh interval is way to long, 5 mins between checks could overheat a drive, especially during a parity check. 1 min. max

11 hours ago, spl147 said:

especially during a parity check

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.

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