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?

1 hour ago, Squid said:

Which plugin?

Oh sorry, the autofan plugin.

S3 Sleep

Since update to 7.1.2 I am getting many errors just before server goes to sleep should I be concerned? Server is working ok just wondering about the errors.

May 24 00:08:31 Media-Server kernel: Call Trace:
May 24 00:16:21 Media-Server kernel: Call Trace:
May 24 00:35:53 Media-Server kernel: Call Trace:
May 24 00:44:09 Media-Server kernel: Call Trace:
May 24 01:01:57 Media-Server kernel: Call Trace:
May 24 01:12:13 Media-Server kernel: Call Trace:
May 24 01:20:55 Media-Server kernel: Call Trace:
May 24 01:34:26 Media-Server kernel: Call Trace:
May 24 01:45:19 Media-Server kernel: Call Trace:

May 21 22:06:05 Media-Server kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
May 22 22:05:46 Media-Server kernel: Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:08:31 Media-Server kernel: Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:16:21 Media-Server kernel: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:35:53 Media-Server kernel: Freezing user space processes failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:44:09 Media-Server kernel: Freezing user space processes failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:01:57 Media-Server kernel: Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:12:13 Media-Server kernel: Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:20:55 Media-Server kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:34:26 Media-Server kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:45:19 Media-Server kernel: Freezing user space processes failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):

Server gui unresponsive, unable to SSH (connection refused), and console commands dont return anything. Local consoles shows the following lines repeating:

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

xxxxxxxlogin: root

Unraid Server OS version: 7.1.2

IPv4 address: 192.xxxxxxxx

IPv6 address: not set

wireless network: not set

it let me attempt to login but would just return the unraid version lines and not ask for a password then just continue repeating the exit codes. shutdown/restart commands returned nothing and then it eventually stopped letting me even try to login.

On 5/25/2025 at 4:59 PM, HiImAWalrus said:

Server gui unresponsive, unable to SSH (connection refused), and console commands dont return anything. Local consoles shows the following lines repeating:

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

xxxxxxxlogin: root

Unraid Server OS version: 7.1.2

IPv4 address: 192.xxxxxxxx

IPv6 address: not set

wireless network: not set

it let me attempt to login but would just return the unraid version lines and not ask for a password then just continue repeating the exit codes. shutdown/restart commands returned nothing and then it eventually stopped letting me even try to login.

Assuming you've already rebooted to fix, if it happens again from the console can you grab the diagnostics (they'll be saved on the flash drive) and also the output of this command:

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

Small bit of feedback: I would personally have the icon in the header follow the colour scheme of the other icons. The red is too "error"/"attention required", especially with the Unraid notification bell icon applying colour codes on top of the bell to indicate status. It doesn't follow the current design language, IMO.

Regarding the Autofan plugin -> For me it works again after update to Unraid 7.1.3 🙂