Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

w83627ehf sensor - driver not working correctly?

Featured Replies

Unraid OS:

6.0.14b using X8SIL-F supermicro mobo

 

Problem

My case has been having intermittent alarms for a while now, and the IPMI interface shows the fans RPMs as absurdly wrong after a few minutes of the server being on (saw 560000RPM at one point, and it flickers to 0 for a second or two Causing the alarm) i finally noticed it is due to the dynamix plugins loading the w83627ehf sensor using modprobe.

 

Once i removed this plugin i started the server off and left it for 8 hours, IPMI sensors still showing correctly, no alarms or errors. Then i used modprobe w83627ehf in console, and within 2 minutes the fans RPMs were displaying wrong, and a port that isn't even plugged in, had been detected briefly as 0 RPMs and alarmed.

 

I'm not sure if this is something that can be fixed by you, or perhaps its something wrong on my end, but it all seems to point to the driver to me, i can of course do without it, but controlling my fans speed would be nice! :D (3000RPM fans at full speed makes the SO quite mad whenever she enters the room with my servers in  ;D)

 

 

How to reproduce:

modprobe w83627ehf on X8SIL-F board

Expected results:

fans continue working normally - able to set RPM correctly

Actual results:

fans IPMI RPMs fail, fans slightly unresponsive

Other information:

Mar 20 14:29:56 jbox autofan: Highest disk temp is 32°C, adjusting fan speed from: FULL (100% @ 2812rpm) to: OFF (0% @ 2766rpm)
Mar 20 14:30:23 jbox autofan: killing autofan process 15348
Mar 20 14:30:23 jbox php: /etc/rc.d/rc.autofan start >/dev/null
Mar 20 14:30:23 jbox autofan: autofan process ID 16851 started, To terminate it, type: autofan -q
Mar 20 14:30:32 jbox autofan: Highest disk temp is 32°C, adjusting fan speed from: FULL (100% @ 2812rpm) to: OFF (0% @ 0rpm)
Mar 20 14:30:51 jbox autofan: killing autofan process 16851
Mar 20 14:30:51 jbox php: /etc/rc.d/rc.autofan start >/dev/null
Mar 20 14:30:51 jbox autofan: autofan process ID 18058 started, To terminate it, type: autofan -q
Mar 20 14:30:51 jbox kernel: w83627ehf w83627ehf.2576: fan2 low limit and alarm disabled
Mar 20 14:30:58 jbox autofan: Highest disk temp is 32°C, adjusting fan speed from: FULL (100% @ 2083rpm) to: OFF (0% @ 2008rpm)

Whilst the autofan script was running this is the type of thing that would happen every time it was applied. (see 100% RPMs change and 0% rpms change within the same minute) NB: The alarms were happening before the autofan script was installed, i believe it was since the dynamix system temp plugin was installed, which to my knowledge only loads the drivers and doesnt try to 'write' any information to the hw so i dont believe this is the autofan script causing the error (Although i've been wrong plenty of times!  :-X) However i never had a case of this happening prior to V6 of unraid (The alarms) - But i suspect this is due to the fact i never had any sensor detection happening prior to V6

I'm running on 6.0.14b using X8SIL-F supermicro mobo

 

My case has been having intermittent alarms for a while now, and the IPMI interface shows the fans RPMs as absurdly wrong after a few minutes of the server being on (saw 560000RPM at one point, and it flickers to 0 for a second or two Causing the alarm) i finally noticed it is due to the dynamix plugins loading the w83627ehf sensor using modprobe.

 

Once i removed this plugin i started the server off and left it for 8 hours, IPMI sensors still showing correctly, no alarms or errors. Then i used modprobe w83627ehf in console, and within 2 minutes the fans RPMs were displaying wrong, and a port that isn't even plugged in, had been detected briefly as 0 RPMs and alarmed.

 

I'm not sure if this is something that can be fixed by you, or perhaps its something wrong on my end, but it all seems to point to the driver to me, i can of course do without it, but controlling my fans speed would be nice! :D (3000RPM fans at full speed makes the SO quite mad whenever she enters the room with my servers in  ;D)

 

 

How to reproduce:

modprobe w83627ehf on X8SIL-F board

Expected results:

fans continue working normally - able to set RPM correctly

Actual results:

fans IPMI RPMs fail, fans slightly unresponsive

 

This is not a driver malfunction.  When the Auto Fan tries to stop the fan, the IPMI interface will briefly sound an alarm, then will reset the PWM interface to met it's lower threshold.

 

See were how to change the IPMI thresholds : https://forums.freenas.org/index.php?threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/

 

To load the correct ipmi driver, use modprobe ipmi_devintf instead of "kldload ipmi.ko".

 

I recommend  you to use FANA to control the fans, since FAN1-4 are controlled in block using the CPU temperature as parameter.

  • Author

I'm running on 6.0.14b using X8SIL-F supermicro mobo

 

My case has been having intermittent alarms for a while now, and the IPMI interface shows the fans RPMs as absurdly wrong after a few minutes of the server being on (saw 560000RPM at one point, and it flickers to 0 for a second or two Causing the alarm) i finally noticed it is due to the dynamix plugins loading the w83627ehf sensor using modprobe.

 

Once i removed this plugin i started the server off and left it for 8 hours, IPMI sensors still showing correctly, no alarms or errors. Then i used modprobe w83627ehf in console, and within 2 minutes the fans RPMs were displaying wrong, and a port that isn't even plugged in, had been detected briefly as 0 RPMs and alarmed.

 

I'm not sure if this is something that can be fixed by you, or perhaps its something wrong on my end, but it all seems to point to the driver to me, i can of course do without it, but controlling my fans speed would be nice! :D (3000RPM fans at full speed makes the SO quite mad whenever she enters the room with my servers in  ;D)

 

 

How to reproduce:

modprobe w83627ehf on X8SIL-F board

Expected results:

fans continue working normally - able to set RPM correctly

Actual results:

fans IPMI RPMs fail, fans slightly unresponsive

 

This is not a driver malfunction.  When the Auto Fan tries to stop the fan, the IPMI interface will briefly sound an alarm, then will reset the PWM interface to met it's lower threshold.

 

See were how to change the IPMI thresholds : https://forums.freenas.org/index.php?threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/

 

To load the correct ipmi driver, use modprobe ipmi_devintf instead of "kldload ipmi.ko".

 

I recommend  you to use FANA to control the fans, since FAN1-4 are controlled in block using the CPU temperature as parameter.

Hi thanks for the reply! Much appreciated.

 

But the fans have been sounding the alarm from before i used the AutoFan script (Infact i only got the script to work today, as i saw bergware had made an update which let it recognize the fans, as before it would just show 'None' in the PWM controller)

 

Also how do i stop unraid from using "kldload ipmi.ko" (I'm in way over my head when it comes to hardware stuff :(), or do you mean when following the link to use ipmitool, in which case i understand, but how do i stop the IPMI web interface from seeing the wrong RPMs?

 

And finally, what do you mean by 'use FANA to control the fans' As far as im aware there is just ports 1-5 on the board? (or is FanA Fan5? Connected directly to PSU?) Sorry! Gets confusing  :D

I'm running on 6.0.14b using X8SIL-F supermicro mobo

 

My case has been having intermittent alarms for a while now, and the IPMI interface shows the fans RPMs as absurdly wrong after a few minutes of the server being on (saw 560000RPM at one point, and it flickers to 0 for a second or two Causing the alarm) i finally noticed it is due to the dynamix plugins loading the w83627ehf sensor using modprobe.

 

Once i removed this plugin i started the server off and left it for 8 hours, IPMI sensors still showing correctly, no alarms or errors. Then i used modprobe w83627ehf in console, and within 2 minutes the fans RPMs were displaying wrong, and a port that isn't even plugged in, had been detected briefly as 0 RPMs and alarmed.

 

I'm not sure if this is something that can be fixed by you, or perhaps its something wrong on my end, but it all seems to point to the driver to me, i can of course do without it, but controlling my fans speed would be nice! :D (3000RPM fans at full speed makes the SO quite mad whenever she enters the room with my servers in  ;D)

 

 

How to reproduce:

modprobe w83627ehf on X8SIL-F board

Expected results:

fans continue working normally - able to set RPM correctly

Actual results:

fans IPMI RPMs fail, fans slightly unresponsive

 

This is not a driver malfunction.  When the Auto Fan tries to stop the fan, the IPMI interface will briefly sound an alarm, then will reset the PWM interface to met it's lower threshold.

 

See were how to change the IPMI thresholds : https://forums.freenas.org/index.php?threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/

 

To load the correct ipmi driver, use modprobe ipmi_devintf instead of "kldload ipmi.ko".

 

I recommend  you to use FANA to control the fans, since FAN1-4 are controlled in block using the CPU temperature as parameter.

Hi thanks for the reply! Much appreciated.

 

But the fans have been sounding the alarm from before i used the AutoFan script (Infact i only got the script to work today, as i saw bergware had made an update which let it recognize the fans, as before it would just show 'None' in the PWM controller)

 

Also how do i stop unraid from using "kldload ipmi.ko" (I'm in way over my head when it comes to hardware stuff :(), or do you mean when following the link to use ipmitool, in which case i understand, but how do i stop the IPMI web interface from seeing the wrong RPMs?

 

And finally, what do you mean by 'use FANA to control the fans' As far as im aware there is just ports 1-5 on the board? (or is FanA Fan5? Connected directly to PSU?) Sorry! Gets confusing  :D

 

1) If you follow the tutorial from the link, you have to change "kldload ipmi.ko"  to "modprobe ipmi_devintf".

 

2) I think it's marked FAN_A in the motherboard, and, in my case (X9SCM-F), it's fan1 in "sensors". The Auto Fan should auto detect it for you.

  • Author

I'm running on 6.0.14b using X8SIL-F supermicro mobo

 

My case has been having intermittent alarms for a while now, and the IPMI interface shows the fans RPMs as absurdly wrong after a few minutes of the server being on (saw 560000RPM at one point, and it flickers to 0 for a second or two Causing the alarm) i finally noticed it is due to the dynamix plugins loading the w83627ehf sensor using modprobe.

 

Once i removed this plugin i started the server off and left it for 8 hours, IPMI sensors still showing correctly, no alarms or errors. Then i used modprobe w83627ehf in console, and within 2 minutes the fans RPMs were displaying wrong, and a port that isn't even plugged in, had been detected briefly as 0 RPMs and alarmed.

 

I'm not sure if this is something that can be fixed by you, or perhaps its something wrong on my end, but it all seems to point to the driver to me, i can of course do without it, but controlling my fans speed would be nice! :D (3000RPM fans at full speed makes the SO quite mad whenever she enters the room with my servers in  ;D)

 

 

How to reproduce:

modprobe w83627ehf on X8SIL-F board

Expected results:

fans continue working normally - able to set RPM correctly

Actual results:

fans IPMI RPMs fail, fans slightly unresponsive

 

This is not a driver malfunction.  When the Auto Fan tries to stop the fan, the IPMI interface will briefly sound an alarm, then will reset the PWM interface to met it's lower threshold.

 

See were how to change the IPMI thresholds : https://forums.freenas.org/index.php?threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/

 

To load the correct ipmi driver, use modprobe ipmi_devintf instead of "kldload ipmi.ko".

 

I recommend  you to use FANA to control the fans, since FAN1-4 are controlled in block using the CPU temperature as parameter.

Hi thanks for the reply! Much appreciated.

 

But the fans have been sounding the alarm from before i used the AutoFan script (Infact i only got the script to work today, as i saw bergware had made an update which let it recognize the fans, as before it would just show 'None' in the PWM controller)

 

Also how do i stop unraid from using "kldload ipmi.ko" (I'm in way over my head when it comes to hardware stuff :(), or do you mean when following the link to use ipmitool, in which case i understand, but how do i stop the IPMI web interface from seeing the wrong RPMs?

 

And finally, what do you mean by 'use FANA to control the fans' As far as im aware there is just ports 1-5 on the board? (or is FanA Fan5? Connected directly to PSU?) Sorry! Gets confusing  :D

 

1) If you follow the tutorial from the link, you have to change "kldload ipmi.ko"  to "modprobe ipmi_devintf".

 

2) I think it's marked FAN_A in the motherboard, and, in my case (X9SCM-F), it's fan1 in "sensors". The Auto Fan should auto detect it for you.

I can't seem to find any reference in the manual to a FAN_A (or on the motherboard itself) just Fan1 ~ Fan5. Also no reference to Fan1~4 being controlled in block with the CPU - although maybe that's just not in the manual i don't know.

 

Also i feel i should mention, incase it sheds some light on things the 'auto fan script' as-is doesn't currently detect anything for me. I had to manually edit it to bergwares github version updated 12 days ago. Still just a bit confused as to why when the driver is loaded into unraid the IPMI device sees crazy RPM values (Even without the auto fan script installed it was doing this)

 

Sorry for the constant questions! Just happy to have somebody that knows what they're talking about answering! :D

kOViQWU.png

I really don't know your board PWM layout (FAN_A exist on X9SCM-F), but you shouldn't mess with the PWM that controls your CPU fan.

 

If your setup show more than one PWM interface, select it and try Detect and see if it slows down the CPU fan and choose one port that doesn't.

  • 3 months later...

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.