21 minutes ago, xrichnj said:

same, my script is dead since upgrading to 7.0.0. even with a symlink to libcrypto.so.1.1, it still requires openssl1.1, which unraid doesnt include with 7.0.0. 

been using this plugin as a stop-gap until i found a solution, but it hasnt come and doesnt look like it will with nerdtools being dead, honestly.

any chance for some love for us dual-socket users with this plugin? an algorithm to select which processor to read the temps for fan control would be hugely useful. (average of the 2 cpu temps, highest of the 2 cpu temps).
currently i can just select one cpu or the other to monitor. if the non-monitored cpu gets used heavily, the fans wont ramp up

Can’t you still use boot/extra to install Slackware packages?

16 minutes ago, wgstarks said:

Can’t you still use boot/extra to install Slackware packages?

I think the problem is finding a compatible package to put into extras. Ones I have found don't support the correct libraries in Unraid.

41 minutes ago, xrichnj said:

same, my script is dead since upgrading to 7.0.0. even with a symlink to libcrypto.so.1.1, it still requires openssl1.1, which unraid doesnt include with 7.0.0. 

been using this plugin as a stop-gap until i found a solution, but it hasnt come and doesnt look like it will with nerdtools being dead, honestly.

any chance for some love for us dual-socket users with this plugin? an algorithm to select which processor to read the temps for fan control would be hugely useful. (average of the 2 cpu temps, highest of the 2 cpu temps).
currently i can just select one cpu or the other to monitor. if the non-monitored cpu gets used heavily, the fans wont ramp up

Have you looked at the freeimpi commands to see if you can replace IPMI tool. I could look at options as we have added disk spindown secondary temp. Which motherboard are you using?

5 hours ago, SimonF said:

I think the problem is finding a compatible package to put into extras. Ones I have found don't support the correct libraries in Unraid.

 

5 hours ago, wgstarks said:

Can’t you still use boot/extra to install Slackware packages?

yeah i thought so too when i upgraded, but havent found anything that supports the correct libraries, either. i'm using a dell r730xd

Hi there,

I just upgraded my server (see sig) and have been so happy to find this plugin to control my fans.

My motherboard supports two cooling zones - Fans 1-5 and Fans A-B - for a total of 7 fans.

I have had my server running well with this plugin for a few days, but had my fans connected as follows:

 

FAN_1: CPU (dual fans on a splitter)
FAN_2: top front (inflow)
FAN_3: middle front (inflow)
FAN_4: bottom front (inflow)
FAN_5: rear (outflow)
FAN_A: SAS Card Fan

FAN_B: (none)

 

This is as the motherboard recommended it: FANS 1-5 are for CPU Temp, FANS A-B are for System temp.

 

I had them all set to respond to the CPU temp. Note that the SAS card fan isn't PWM, so just runs at full speed all the time.

 

However, I noticed under heavy IO load that the CPU didn't really rise much, but the HDDs did, so I decided to split the CPU cooler to the FANA & FANB zone (despite what the manual recommends), and the case fans all on the same zone. So now it is set up as:

 

FAN_A: CPU (top)
FAN_B: CPU (bottom)
FAN_1: top front (inflow)
FAN_2: middle front (inflow)
FAN_3: bottom front (inflow)
FAN_4: SAS Card Fan (non PWM)
FAN_5: rear (outflow)

 

I have set the FAN A-B zone to react to CPU temps, and the FANS 1-5 zone to react to HDD temps. You can see my setup in the attached screenshot (please ignore the floating footer - a quirk of the screencap plugin I use).

 

One of my disks is set to never spin down, so I don't need to use the secondary sensor option for HDD temps.

 

However, since moving to the new fan configuration, my case fans now no longer spin down to their lower values (they used to drop to about 140 RPM, sitting mostly at 280 RPM), but now they sit around 500-700 RPM.

Taking a look in the ipmifan log, I see the following entries:

2025-01-24 11:04:12 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C)
2025-01-24 11:05:12 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C)
2025-01-24 11:07:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C)
2025-01-24 11:08:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C)
2025-01-24 11:10:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C)
2025-01-24 11:11:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(44%):CPU Temp(51 °C)
2025-01-24 11:12:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C)
2025-01-24 11:15:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C)
2025-01-24 11:16:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(44%):CPU Temp(51 °C)
2025-01-24 11:17:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C)
2025-01-24 11:20:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(32%):CPU Temp(47 °C)
2025-01-24 11:21:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C)
2025-01-24 11:23:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(32%):CPU Temp(47 °C)

 

Looking at the other attached screenshot, you can see that the HDD temp reported by the plugin actually 33C. Though I do have an NVME in my server that is 46. I have unchecked that NVME (and my other NVME and SSDs) from the "Available HDDs" list, so they shouldn't be monitored. Indeed, as the IPMI dashboard shows, they are not.

Yet is seems that the Fan Control is still including the excluded NVME drive(s).

Can you please confirm if this is the case, or if I have some other setting that needs changing?

 

FWIW, all the case fans are the same Noctua model, while the CPU fans are a different Noctua model. As Noctua fans can go to very low RPMs, I therefore had to set "Lower_Critical_Threshold"  (using the config editor) to 0 for all of the fans - otherwise I was getting the pulsing problem where the mobo thinks fans have failed (anoher reason why this plugin has been so valuable for me - thank you).

 

Also FWIW, I've never gotten the network connection to work, but it seems to work fine without it, so I never bothered troubleshooting it to get it to work.

 

FINALLY AND ALSO:

Since either the recent plugin update or the swap to FAN A-B, I now have the options to set:

    High temperature threshold Overide(°C):

    Low temperature threshold Overide(°C):

    Fan speed maximum Overide(%):

    Fan speed minimum Overide(%):

 

Can you explain what these are used for? Is it so that if something goes extremely wrong (ie temps out of control), it will ignore the previously set max fan speed settings to ensure things get cool again? Similarly, if the temp gets unusually cool, it can slow the fans down even further?

 

Thanks for your help, insight, and this great plugin - a real life saver.

Edited January 24, 20251 yr by jademonkee

9 hours ago, xrichnj said:

 

yeah i thought so too when i upgraded, but havent found anything that supports the correct libraries, either. i'm using a dell r730xd

your server is supported, install and setup, i run a T430 with dual cpu and it works perfectly

Edited January 24, 20251 yr by spl147

48 minutes ago, spl147 said:

your server is supported, install and setup, i run a T430 with dual cpu and it works perfectly

with this plugin? or you have a script that works with 7.0.0 for fan control?

1 minute ago, xrichnj said:

with this plugin? or you have a script that works with 7.0.0 for fan control?

Plugin

15 minutes ago, spl147 said:

Plugin

yes it 'works' for me too, but as far as i can tell, lacks an algorithm to select how to monitor dual cpus for fan control (you can monitor one cpu or the other, not the highest temp of the 2 cpus or the average between the 2 cpus). if im using the non-monitored cpu for something heavily, the monitored temp doesn't really change, the fans dont ramp up, and the thermals run away.

also, there is very little granularity for customizing the fan curve itself. if your cpu is at idle and goes back and forth between 45 and 46 degrees, i havent found settings that will get it to stop changing the fan speeds with these tiny fluctuations in temp.

22 minutes ago, xrichnj said:

yes it 'works' for me too, but as far as i can tell, lacks an algorithm to select how to monitor dual cpus for fan control (you can monitor one cpu or the other, not the highest temp of the 2 cpus or the average between the 2 cpus). if im using the non-monitored cpu for something heavily, the monitored temp doesn't really change, the fans dont ramp up, and the thermals run away.

also, there is very little granularity for customizing the fan curve itself. if your cpu is at idle and goes back and forth between 45 and 46 degrees, i havent found settings that will get it to stop changing the fan speeds with these tiny fluctuations in temp.

agreed the dual cpu monitoring could use refinement, given the fact that functionality was just added recently. (i am the one that requested it) it has room to grow. the author is quite easy to work with.

 

the fan curve is based on percent of high and low temp threshold vs fan rpm min and max. if you fan speed is set to narrow or your cpu high and low are set to narrow, then yes 1 degree will hake the fan change alot.

 

here is mine:

i  monitor the cpu2,

13 minutes ago, spl147 said:

agreed the dual cpu monitoring could use refinement, given the fact that functionality was just added recently. (i am the one that requested it) it has room to grow. the author is quite easy to work with.

 

the fan curve is based on percent of high and low temp threshold vs fan rpm min and max. if you fan speed is set to narrow or your cpu high and low are set to narrow, then yes 1 degree will hake the fan change alot.

 

here is mine:

i  monitor the cpu2,

 

yeah they seem helpful in this thread, and receptive to ideas for improvement.
i hope with some development, this tool can be great for fan control.

also, can you explain the 'standard' vs 'override' fields?

4 minutes ago, xrichnj said:

also, can you explain the 'standard' vs 'override' fields?

override fields are used when the hdd's are spundown (if you selected a sensor in the hdd spundown field) i think override should be spundown. it's confusing

43 minutes ago, spl147 said:

here is mine:

i  monitor the cpu2,

 

under temperature sensor, your photo lists 'hdd temperature'. doesnt this mean that your fans are reading your hdd temp for control and not your cpu?

Edited January 24, 20251 yr by xrichnj

13 minutes ago, xrichnj said:

 

under temperature sensor, your photo lists 'hdd temperature'. doesnt this mean that your fans are reading your hdd temp for control and not your cpu?

right, then under that it lists HDD spundown temp sensor, i use temp (CPU2) so when my hdds spindown it will monitor cpu. my chassis has 1 single 92mm fan with a shroud that pulls air in through the front hotswap hdd bays over both cpus and out the back.

 

thats why there are 2 sensors to choose and 2 sets of high and low thresholds. 1 when hdds are spining and 1 when they are not

 

Edited January 24, 20251 yr by spl147

1 minute ago, spl147 said:

right, then under that it lists HDD spundown temp sensor, i use temp (CPU2) so when my hdds spindown it will monitor cpu. my chassis has 1 single 92mm fan with a shroud that pulls air in through the front hotswap hdd bays over both cpus and out the back

 

 

ah, ok i see. my drives are right upfront as well (its a rackmount server), so drive temps are never an issue with 6 fans pulling fresh ambient air across them always, i just need the cpus to respond to the cpu. 

 

i set the "low temperature threshold" value to above my idle cpu temperatures and tuned the "fan speed minimum" to the value i wanted the fans to run at idle and it has stopped the up and down ramping.

 

ex:
the monitored cpu idles between 44-47c. so i set the "low temp threshold" to 50c and set the fan speed minimum to 18.7%, and now it can bounce around between 44 and 47c without changing. it only starts applying the curve once the monitored cpu hits 50c. 

 

that i can live with, but the lack of dual-cpu monitoring options still concerns me. i have 28cores/56threads and dont like to have everything just blast away at whatever cores it can get its hands on, so i have containers and vms segmented/compartmentalized to specific cores or even just give it a whole cpu (but not both). the fact i cant tell the plugin to "use the higher of the 2 temps of the 2 cpus to control the fans" means i have to be careful what is running on which cpu to avoid the fans not increasing and thermals going out of control. 

 

i suppose i could monitor the exhaust temp and run the fans off that, as the exhaust temp correlates to either cpu being loaded, but that is certainly not elegant/ideal either. 

12 hours ago, xrichnj said:

 

yeah i thought so too when i upgraded, but havent found anything that supports the correct libraries, either. i'm using a dell r730xd

So, this is me too. What I ended up doing is grabbing 3 files and putting them in a shared /ipmi/ folder on my array:

• ipmitool
• libcrypto.so.1.1
• libssl.so.1.1

Then, using the User Scripts plugin, I created a simple script to run "At First Array Start Only"  with the following content:

#!/bin/bash

cp /mnt/user/Public/ipmi/ipmitool /usr/bin/
cp /mnt/user/Public/ipmi/libcrypto.so.1.1 /usr/lib64/
cp /mnt/user/Public/ipmi/libssl.so.1.1 /usr/lib64/

modprobe ipmi_devintf

 

Apparently, the IPMI plugin didn't copy these necessary files over for me.

 

To test that ipmitool works after running the script, run the following command in the Unraid console and expect this result:

root@Tower:~# ipmitool power status
Chassis Power is on
root@Tower:~#

 

Note, I turned off the script and rebooted and IPMI Tools wouldn't work so I had to re-enable the script. Not sure why those files aren't installed with the plugin, or if they are, something screwed up for me.

Edited January 24, 20251 yr by Edival76

1 minute ago, Edival76 said:

So, this is me too. What I ended up doing is grabbing 3 files and putting them in a shared /ipmi/ folder on my array:

• ipmitool
• libcrypto.so.1.1
• libssl.so.1.1

Then, using the User Scripts plugin, I created a simple script to run "At First Array Start Only"  with the following content:

#!/bin/bash

cp /mnt/user/Public/ipmi/ipmitool /usr/bin/
cp /mnt/user/Public/ipmi/libcrypto.so.1.1 /usr/lib64/
cp /mnt/user/Public/ipmi/libssl.so.1.1 /usr/lib64/

modprobe ipmi_devintf

 

Apparently, the IPMI plugin didn't copy these necessary files over for me.

 

To test that ipmitool works after running the script, run the following command in the Unraid console and expect this result:

root@Tower:~# ipmitool power status
Chassis Power is on
root@Tower:~#

 

The plugin does not use ipmitool it uses freeimpi the commands are different https://www.gnu.org/software/freeipmi/manpages/man7/freeipmi.7.html

12 minutes ago, SimonF said:

The plugin does not use ipmitool it uses freeimpi the commands are different https://www.gnu.org/software/freeipmi/manpages/man7/freeipmi.7.html

That is very odd then because without my script the IPMI Tool doesn't kick in for me. The fans continue to run at full speed despite the tool being turned on. 🤷🏻‍♂️

41 minutes ago, Edival76 said:

That is very odd then because without my script the IPMI Tool doesn't kick in for me. The fans continue to run at full speed despite the tool being turned on. 🤷🏻‍♂️

What motherboard do you the plugin does not have support for all platforms.

2 hours ago, spl147 said:

override fields are used when the hdd's are spundown (if you selected a sensor in the hdd spundown field) i think override should be spundown. it's confusing

Happy to change what do you want it to say.

4 minutes ago, SimonF said:

Happy to change what do you want it to say.

override should be spundown

 

 

6 minutes ago, SimonF said:

Happy to change what do you want it to say.

also perhaps move the spundown sensor down to the spun down settings

1 hour ago, Edival76 said:

So, this is me too. What I ended up doing is grabbing 3 files and putting them in a shared /ipmi/ folder on my array:

• ipmitool
• libcrypto.so.1.1
• libssl.so.1.1

Then, using the User Scripts plugin, I created a simple script to run "At First Array Start Only"  with the following content:

#!/bin/bash

cp /mnt/user/Public/ipmi/ipmitool /usr/bin/
cp /mnt/user/Public/ipmi/libcrypto.so.1.1 /usr/lib64/
cp /mnt/user/Public/ipmi/libssl.so.1.1 /usr/lib64/

modprobe ipmi_devintf

 

Apparently, the IPMI plugin didn't copy these necessary files over for me.

 

To test that ipmitool works after running the script, run the following command in the Unraid console and expect this result:

root@Tower:~# ipmitool power status
Chassis Power is on
root@Tower:~#

 

Note, I turned off the script and rebooted and IPMI Tools wouldn't work so I had to re-enable the script. Not sure why those files aren't installed with the plugin, or if they are, something screwed up for me.

 

this would absolutely work, but i'm not willing to do it because i'm suspicious that libssl1 has something to do with the recent vulnerabilities patched by LimeTech. 

 

they said if youre on 6.12.4 and before (which only has libssl1), then youre vulnerable.

 

if you are on 7.0.0 (which ONLY has libssl3), then youre safe from the vulnerabilities.

 

maybe someone can check what ssl libraries 6.12.15 has (which is also safe) to shed some light on this. 

 

look, i'm not a security researcher, but the above worries me about installing old and "unofficial" libraries. libssl1 is pretty antiquated at this point, maybe the discovery of these vulnerabilities is what led to it being dropped from 7.0.0. i'm sure Lime had a good reason for removing/replacing it, i dont think they would remove old libraries that would break things "because they felt like it", there needed to be good reason. 

 

having better fan control isnt worth leaving my server potentially vulnerable to xss and csrf

22 minutes ago, SimonF said:

Happy to change what do you want it to say.

like this: 

 

Also only show the spundown threshold vales if the spundown sensor is not none.

 

Edited January 24, 20251 yr by spl147