@Edival76here is the ipmitool commands to play with fan control to find the perfect cpu idle setting:

 

stop fan control in the plugin

 

Set fans to manual control:

ipmitool raw 0x30 0x30 0x01 0x00

 

set fan speed:

ipmitool raw 0x30 0x30 0x02 0xff 0xXX (replace XX with a value from the chart below:

00-64 (00=0% and 64=100%)

 

00 -> 0%

01 -> 2%

02 -> 3%

03 -> 5%

04 -> 6%

05 -> 8%

06 -> 9%

07 -> 11%

08 -> 12%

09 -> 14%

10 -> 16%

11 -> 17%

12 -> 19%

13 -> 20%

14 -> 22%

15 -> 23%

16 -> 25%

17 -> 27%

18 -> 28%

19 -> 30%

20 -> 31%

21 -> 33%

22 -> 34%

23 -> 36%

24 -> 38%

25 -> 39%

26 -> 41%

27 -> 42%

28 -> 44%

29 -> 45%

30 -> 47%

31 -> 48%

32 -> 50%

33 -> 52%

34 -> 53%

35 -> 55%

36 -> 56%

37 -> 58%

38 -> 59%

39 -> 61%

40 -> 62%

41 -> 64%

42 -> 66%

43 -> 67%

44 -> 69%

45 -> 70%

46 -> 72%

47 -> 73%

48 -> 75%

49 -> 77%

50 -> 78%

51 -> 80%

52 -> 81%

53 -> 83%

54 -> 84%

55 -> 86%

56 -> 88%

57 -> 89%

58 -> 91%

59 -> 92%

60 -> 94%

61 -> 95%

62 -> 97%

63 -> 98%

64 -> 100%

Edited January 29, 20251 yr by spl147

3 hours ago, Edival76 said:

I'm making it complex because it's still very loud despite the reasonable CPU temp of 58 °C. As you can see, the top temp is 80 °C, which should give it plenty of movement to ramp speeds at that point.

 

It's running at 9600 rpm, which is a bit too loud at that temp, IMO. So, I'm just hoping to be able to make tweaks to it. If not, no worries, it's still WAY better than without.

 

 

when below your minimum temp setting, the fans run at the fan speed minimum. 

 

once it hits above your minimum temperature, it starts applying the curve between your fan speed minimum and fan speed maximum depending on your temps 

 

for the settings you posted, your fan logic would be:

 

-run the fans at 1.5% until the CPU hits 20 degrees.

-between 20 degrees and 80 degrees, apply and set the fan speed/curve between 1.5% and 75% depending on where the temperature sits between 20 and 80.

-any temp past 80, run the fans at 75% (the "fan speed maximum")

 

these are bad settings because your CPU will never run below 20 degrees. 

 

my CPU idles in the mid-40 degree range, so I have my low temperature threshold set to 50, so the fans don't bounce around with minor temp changes at idle. it doesn't start applying the curve until it hits 50 degrees (my low temperature threshold), which means the CPU is actually doing something, so it starts ramping the fans up (at 50 degrees)

 

 

11 hours ago, xrichnj said:

 

when below your minimum temp setting, the fans run at the fan speed minimum. 

 

once it hits above your minimum temperature, it starts applying the curve between your fan speed minimum and fan speed maximum depending on your temps 

 

for the settings you posted, your fan logic would be:

 

-run the fans at 1.5% until the CPU hits 20 degrees.

-between 20 degrees and 80 degrees, apply and set the fan speed/curve between 1.5% and 75% depending on where the temperature sits between 20 and 80.

-any temp past 80, run the fans at 75% (the "fan speed maximum")

 

these are bad settings because your CPU will never run below 20 degrees. 

 

my CPU idles in the mid-40 degree range, so I have my low temperature threshold set to 50, so the fans don't bounce around with minor temp changes at idle. it doesn't start applying the curve until it hits 50 degrees (my low temperature threshold), which means the CPU is actually doing something, so it starts ramping the fans up (at 50 degrees)

 

 

very nicely put.

13 hours ago, xrichnj said:

 

when below your minimum temp setting, the fans run at the fan speed minimum. 

 

once it hits above your minimum temperature, it starts applying the curve between your fan speed minimum and fan speed maximum depending on your temps 

 

for the settings you posted, your fan logic would be:

 

-run the fans at 1.5% until the CPU hits 20 degrees.

-between 20 degrees and 80 degrees, apply and set the fan speed/curve between 1.5% and 75% depending on where the temperature sits between 20 and 80.

-any temp past 80, run the fans at 75% (the "fan speed maximum")

 

these are bad settings because your CPU will never run below 20 degrees. 

 

my CPU idles in the mid-40 degree range, so I have my low temperature threshold set to 50, so the fans don't bounce around with minor temp changes at idle. it doesn't start applying the curve until it hits 50 degrees (my low temperature threshold), which means the CPU is actually doing something, so it starts ramping the fans up (at 50 degrees)

 

 

This is amazing and makes so much sense!! Thank you!

Hi guys, I recently updated to the newer version 2025.01.26c  was on 2025.01.21

 

and after the update, the fan control doesnt work anymore.... all my fans are stuck at full speed... I am trying to find the issue since this morning and I think its a bug in the plugin and not in my setting...

 

I did reboot, BMC cold Reset, reset the thresholds of all my fans (mix of Noctua and SuperMicro loud fans) and even if my  CPU or HDD Temp are under my setting (25 degree after a reboot) with the Fan control Enable, all fans are at their max RPM

 

There no Fans on Critical State, all are Normal State

 

The only way I can slow them down is by putting the Fan Control at OFF and going in the IPMI to change the Fan Mode to Optimal

 

Need some help uhuh so tell me what logs you guys need and I will post it

 

** in the ipmifan.log **

 

Quote

2025-01-30 16:49:17 Fan:Temp, FAN1234( 5%):CPU2 Temp(30C), FANA( 6%):M2NVMeSSD Temp2(28C)

 

we can see it try to slow them down to 5% but unsuccessful and the next polling (set at every 1 minute) seem never happen also

 

UnRaid version = 6.12.15

IPMI plugin version = 2025.01.26c

 

Last working IPMI Version = 2025.01.21

 

Thank a lot

nevermind... I think I found my issue...

 

I Cleared the Event Logs in the plugin -> Readings -> Event Logs -> Clear ALL

 

seem I need to clear there too, not only in the IPMI

 

at the moment it seem to work, they all slowed down

Question: I applied the new unRAID Patch plugin yesterday and had to reboot due to the mover issue - uninstalling the mover tuning plugin still didn't let the mover fix get applied. After the reboot things are operating normally, but today I opened a terminal session and saw something that I haven't seen previously.

 

The 1st screenshot below shows two folders that I've never seen before when at the root of the unRAID filesystem. The installpkg one contains a file named conffiles which appears to be a leftover from installation of the IPMI plugin. That file is viewable as raw text and contains the data in the 2nd screenshot which led me to believe it's related to the IPMI plugin.  Is this normal or just a one-off? Is it safe to delete? It doesn't appear to be affecting anything operationally and I didn't find anything in syslog that references it.

 

The 2nd folder is the empty one called hugetlbfs, which may be unrelated to the IPMI plugin but is new to me. I'm not seeing any operational changes or lockups, but my OCD always has me investigate things even if they aren't or don't appear to be affecting normal operation. This one may be related to using the command 'touch /boot/config/fastusr', used to make unRAID load all modules into RAM rather than having fallback to some on the USB key. Thoughts?

 

 

55 minutes ago, AgentXXL said:

Question: I applied the new unRAID Patch plugin yesterday and had to reboot due to the mover issue - uninstalling the mover tuning plugin still didn't let the mover fix get applied. After the reboot things are operating normally, but today I opened a terminal session and saw something that I haven't seen previously.

 

The 1st screenshot below shows two folders that I've never seen before when at the root of the unRAID filesystem. The installpkg one contains a file named conffiles which appears to be a leftover from installation of the IPMI plugin. That file is viewable as raw text and contains the data in the 2nd screenshot which led me to believe it's related to the IPMI plugin.  Is this normal or just a one-off? Is it safe to delete? It doesn't appear to be affecting anything operationally and I didn't find anything in syslog that references it.

 

The 2nd folder is the empty one called hugetlbfs, which may be unrelated to the IPMI plugin but is new to me. I'm not seeing any operational changes or lockups, but my OCD always has me investigate things even if they aren't or don't appear to be affecting normal operation. This one may be related to using the command 'touch /boot/config/fastusr', used to make unRAID load all modules into RAM rather than having fallback to some on the USB key. Thoughts?

 

 

Thanks, Will look into my Slack build script I compiled a new freeimpi package looks like that path should be excluded from the package.

Hello, little update from my issue with IPMI plugin

 

I find out the polling Temp stop when there a Critical issue in the Event Logs and after I cleared the warning, it doesnt restart...

 

and for unknown reason, there 1 sometime 2 fans been detected at 0 RPM. and After after that. it show weird warning like when the RPM are around 1 200 RPM even if the Lower CT is set at 200 or 300 rpm, it appear in the Event Log.

 

I disabled the  HDD Spundown option to test if is that option who put my fan to 0 RPM while switching to another sensor.

 

I got one question -> How do I restart the polling temp? it seem stuck at the last configuration showed in the ipmifan.log and no update appear in this log since the Critical Warning.

 

Thanks

1 minute ago, FTW said:

Hello, little update from my issue with IPMI plugin

 

I find out the polling Temp stop when there a Critical issue in the Event Logs and after I cleared the warning, it doesnt restart...

 

and for unknown reason, there 1 sometime 2 fans been detected at 0 RPM. and After after that. it show weird warning like when the RPM are around 1 200 RPM even if the Lower CT is set at 200 or 300 rpm, it appear in the Event Log.

 

I disabled the  HDD Spundown option to test if is that option who put my fan to 0 RPM while switching to another sensor.

 

I got one question -> How do I restart the polling temp? it seem stuck at the last configuration showed in the ipmifan.log and no update appear in this log since the Critical Warning.

 

Thanks

post your fan settings page screenshot

2 hours ago, spl147 said:

post your fan settings page screenshot

 

There the Screenshot

 

I got 3 fans stuck between 6 800rpm  and 7 2000rpm

Edited February 2, 20251 yr by FTW

after few test. I unplug my FAN5 and FAN6 and did a "ipmitool bmc reset cold". They are the one who hitting a lower critical NR and I fall on another issue... this time its FAN ABC who are stuck at 7200rpm while FAN 1234 are at normal RPM....

 

20 hours ago, FTW said:

 

There the Screenshot

 

I got 3 fans stuck between 6 800rpm  and 7 2000rpm

on supermicro boards, fanA is for the CPU and FAN1234 is chassis fans.

 

looking at your manual, your board has FANABC and FAN123456. so it looks like the plugin is not taking all your headers into account.

 

you could put both CPU's on FANA via a splitter and use splitters to keep your chassis fans on FAN1234 only.

 

or see if @SimonFcan add support for the additional fan headers

Edited February 3, 20251 yr by spl147

A

On 2/1/2025 at 4:51 AM, AgentXXL said:

Question: I applied the new unRAID Patch plugin yesterday and had to reboot due to the mover issue - uninstalling the mover tuning plugin still didn't let the mover fix get applied. After the reboot things are operating normally, but today I opened a terminal session and saw something that I haven't seen previously.

 

The 1st screenshot below shows two folders that I've never seen before when at the root of the unRAID filesystem. The installpkg one contains a file named conffiles which appears to be a leftover from installation of the IPMI plugin. That file is viewable as raw text and contains the data in the 2nd screenshot which led me to believe it's related to the IPMI plugin.  Is this normal or just a one-off? Is it safe to delete? It doesn't appear to be affecting anything operationally and I didn't find anything in syslog that references it.

 

The 2nd folder is the empty one called hugetlbfs, which may be unrelated to the IPMI plugin but is new to me. I'm not seeing any operational changes or lockups, but my OCD always has me investigate things even if they aren't or don't appear to be affecting normal operation. This one may be related to using the command 'touch /boot/config/fastusr', used to make unRAID load all modules into RAM rather than having fallback to some on the USB key. Thoughts?

 

 

 

@SimonF I have the exact same issue. Using an Supermicro X11SPi-TF , Version 1.02 motherboard. Here's my fan settings page (let me know if I can post any other diagnostics to help locate the issue):

36 minutes ago, jch said:

A

 

@SimonF I have the exact same issue. Using an Supermicro X11SPi-TF , Version 1.02 motherboard. Here's my fan settings page (let me know if I can post any other diagnostics to help locate the issue):

Thats the sensor page not the fan setting page

30 minutes ago, spl147 said:

Thats the sensor page not the fan setting page

 

Is this it?

13 minutes ago, jch said:

 

Is this it?

No, click the fan control tab

21 minutes ago, spl147 said:

No, click the fan control tab

 

3rd time's the charm.

21 hours ago, jch said:

A

 

@SimonF I have the exact same issue. Using an Supermicro X11SPi-TF , Version 1.02 motherboard. Here's my fan settings page (let me know if I can post any other diagnostics to help locate the issue):

Are you referring to the package folders or something else?

2 minutes ago, SimonF said:

Are you referring to the package folders or something else?

The package folders.

On 2/1/2025 at 12:51 PM, AgentXXL said:

Question: I applied the new unRAID Patch plugin yesterday and had to reboot due to the mover issue - uninstalling the mover tuning plugin still didn't let the mover fix get applied. After the reboot things are operating normally, but today I opened a terminal session and saw something that I haven't seen previously.

 

The 1st screenshot below shows two folders that I've never seen before when at the root of the unRAID filesystem. The installpkg one contains a file named conffiles which appears to be a leftover from installation of the IPMI plugin. That file is viewable as raw text and contains the data in the 2nd screenshot which led me to believe it's related to the IPMI plugin.  Is this normal or just a one-off? Is it safe to delete? It doesn't appear to be affecting anything operationally and I didn't find anything in syslog that references it.

 

The 2nd folder is the empty one called hugetlbfs, which may be unrelated to the IPMI plugin but is new to me. I'm not seeing any operational changes or lockups, but my OCD always has me investigate things even if they aren't or don't appear to be affecting normal operation. This one may be related to using the command 'touch /boot/config/fastusr', used to make unRAID load all modules into RAM rather than having fallback to some on the USB key. Thoughts?

 

 

I will release an update with a new package over the weekend as no longer get the directory but just want to tidy up a message that apears on the console. Hugetlbfs is for hugepages used by VMs etc.

Hello,

Thank you for your hard work with this plugin.

I have a small request : in this screenshot I selected hhd temp. Is there a way to change that icon before the temp reading to show a small hdd or something else to make it more obvious that is a hdd temp and not a cpu temp. 

 

Edited February 9, 20251 yr by htudor

4 hours ago, htudor said:

Hello,

Thank you for your hard work with this plugin.

I have a small request : in this screenshot I selected hhd temp. Is there a way to change that icon before the temp reading to show a small hdd or something else to make it more obvious that is a hdd temp and not a cpu temp. 

 

change to HDD icon in latest release.

 

On 2/1/2025 at 12:51 PM, AgentXXL said:

Question: I applied the new unRAID Patch plugin yesterday and had to reboot due to the mover issue - uninstalling the mover tuning plugin still didn't let the mover fix get applied. After the reboot things are operating normally, but today I opened a terminal session and saw something that I haven't seen previously.

 

The 1st screenshot below shows two folders that I've never seen before when at the root of the unRAID filesystem. The installpkg one contains a file named conffiles which appears to be a leftover from installation of the IPMI plugin. That file is viewable as raw text and contains the data in the 2nd screenshot which led me to believe it's related to the IPMI plugin.  Is this normal or just a one-off? Is it safe to delete? It doesn't appear to be affecting anything operationally and I didn't find anything in syslog that references it.

 

The 2nd folder is the empty one called hugetlbfs, which may be unrelated to the IPMI plugin but is new to me. I'm not seeing any operational changes or lockups, but my OCD always has me investigate things even if they aren't or don't appear to be affecting normal operation. This one may be related to using the command 'touch /boot/config/fastusr', used to make unRAID load all modules into RAM rather than having fallback to some on the USB key. Thoughts?

 

 

Package has been updated. But may need a reboot to replace.

 

20 hours ago, SimonF said:

Package has been updated. But may need a reboot to replace.

 

i like the HDD icon, any chance to expand this? cpu icon for cpu temp, a fan instead of the rpm gauge for fan speed?

 

the ability to label the sensors would also be great