Update causing Fan errors

[avalon60]

I have just updated to TTrueNAS-13.0-U4 and I am getting these errors:
New alerts:
* Fan FAN 4 Deasserted Lower Non-critical going low : Reading 750 < Threshold
600 RPM.

New alerts:
* Fan FAN 4 Asserted Lower Non-critical going low : Reading 600 < Threshold 600
RPM.

Current alerts:
* Fan FAN 4 Deasserted Lower Non-critical going low : Reading 750 < Threshold
600 RPM.


* Fan FAN 4 Asserted Lower Non-critical going low : Reading 600 < Threshold 600
RPM.

Can I ignore them or should I do something about it. I am getting email alerts continually about the fans readings
Thanks

 

[SuperCycle]

I just updated to TrueNAS 13.0-U4 and getting the same errors. They started right after the update

 

[Samuel Tai]

It's likely nothing. Do you have a fan connected to the FAN 4 header?

If so, you could try adjusting the fan speed in the BIOS, under Hardware Health Configuration.

 

[avalon60]

Yes I do for the rear case fan. How do I change the fan speed on a SuperMicro X9SCM-F board

 

[Samuel Tai]

Yes I do for the rear case fan. How do I change the fan speed on a SuperMicro X9SCM-F board

I gave you the extract from the motherboard manual for the specific BIOS screen.

 

[Ramboxman]

Also getting fan alerts super micro board as well.

 

[Nooblet]

Also getting fan errors since updating to TrueNAS-13.0-U4 from TrueNAS-13.0-U3

I am running an old dell R510 that i have modded the fans on so not surprised getting some errors on but I don't need an email every time I get an error.

Code:

New alerts:
* Fan FAN MOD 5A RPM Deasserted Lower Critical going low : Reading 1560 <
Threshold 720 RPM.
* Fan FAN MOD 5A RPM Asserted Lower Critical going low : Reading 0 < Threshold
720 RPM.
* Fan Fan Redundancy Asserted Fully Redundant.
* Fan Fan Redundancy Asserted Redundancy Lost.
* Fan FAN MOD 5A RPM Deasserted Lower Critical going low : Reading 1560 <
Threshold 720 RPM.

I swear there used to be an option for fan error notifications in TrueNAS-12 but don't see it in 13

I also tried logging an error in Jira but as soon as I log into the IXsystems Jira Page i am redirected to the below page and can't submit the bug.

Is anyone else having issues logging a bug over on Jira?

 

[avalon60]

My mothereboard 'manual' is just 1 sheet of paper, and there is no information on how to change the fan speeds.
Strange as it has only just started to give the said errors, as I have had this same setup for about 6 / 7 years now.

 

[Ramboxman]

It's likely nothing. Do you have a fan connected to the FAN 4 header?

View attachment 64276

If so, you could try adjusting the fan speed in the BIOS, under Hardware Health Configuration.

View attachment 64277

I just updated to TrueNAS 13.0-U4 and getting the same errors. They started right after the update

I found noting in setting but did remote logging with ipm

 

[GregW]

Same here, super-micro motherboard, 500 alerts / day on a fan. Fan is running fine (checked in IPMI).

Edit: after a couple of days I see no more alert. Most probably then fan is old, when restarting it's unstable but after a few hours it seems to stabilize and the IPMI alerts stop.

 

[Nooblet]

I disabled the IPMI system alerts and the fan warnings stopped.

Obviously not an ideal solution as it will hide other events. will only use this temporarily.

 

[ummario]

I'm on the same boat as everyone here!

 

[sretalla]

For those claiming there's no manual (I'm sure google will produce one from the supermicro site), there's this from the header of @Stux / @Kevin Horton / @Glorious1 's script:

Code:

# The IPMI fan lower and upper fan speed thresholds must be adjusted to be
# compatible with the fans used.  Do not rely completely on manufacturer specs
# to determine the slowest and fastest possible fan speeds, as some fans have
# been found to run at speeds that differ somewhat from the official specs.
# See:
# https://forums.freenas.org/index.php?resources/how-to-change-ipmi-sensor-thresholds-using-ipmitool.35/

# The following ipmitool commands can be run when connected to the FreeNAS
# server via ssh.  They are useful to set a desired fan duty cycle before
# checking the fan speeds.

# Set duty cycle in Zone 0 to 100%: ipmitool raw 0x30 0x70 0x66 0x01 0x00 100
# Set duty cycle in Zone 0 to  50%: ipmitool raw 0x30 0x70 0x66 0x01 0x00 50
# Set duty cycle in Zone 0 to  20%: ipmitool raw 0x30 0x70 0x66 0x01 0x00 20

# Set duty cycle in Zone 1 to 100%: ipmitool raw 0x30 0x70 0x66 0x01 0x01 100
# Set duty cycle in Zone 1 to  50%: ipmitool raw 0x30 0x70 0x66 0x01 0x01 50
# Set duty cycle in Zone 1 to  20%: ipmitool raw 0x30 0x70 0x66 0x01 0x01 20

# Check duty cycle in Zone 0:
#   ipmitool raw 0x30 0x70 0x66 0x00 0x00
# result is hex, with 64 being 100% duty cycle. 32 is 50% duty cycle.
# 14 is 20% duty cycle.

# Check duty cycle in Zone 1:
#    ipmitool raw 0x30 0x70 0x66 0x00 0x01
# result is hex, with 64 being 100% duty cycle.  32 is 50% duty cycle.
# 14 is 20% duty cycle.

# Check fan speeds using: ipmitool sdr

The really old URL above converts to this one:

How To: Change IPMI Sensor Thresholds using ipmitool

Many server motherboards, including the Supermicro X10 series, have their fans monitored by the BMC, which automatically attempts to recover stalling (of the motor, not in the aerodynamic sense) fans by spinning them up to maximum (PWM set to...

www.truenas.com

 

[Kaptain9981]

Also started seeing this with 13.0-U4, but probably was also going on the whole time. I use a SuperMicro x9 board and while looking at the current status my FAN1 and FAN2 were around 800-900 rpm with the optimal fan profile when looking at fan sensor speeds. However looking at health history they had dipped to 500rpm which is what was screaming under alerts with the latest update.

Changing to the Heavy I/O or even standard fan profile those and all other fans appear to stay above their warning thresholds. You can change that under Configuration > Fan Mode in the IMPI web interface.

You can also try to adjust the thresholds with ipmitool, but I figured the fans were probably spinning too low anyway on Optimal if they were down to 500rpm.

 

[avalon60]

Thanks for that, but how do I change to Heavy I/O or change the fan threshholds in the ipmitool

 

[termehansen]

I have the same issue on a standard "TRUENAS-MINI-3.0-XL+" instance. In ipmitool I see a lot of times:

FAN1 | 1100 RPM | ok
FAN2 | 800 RPM | ok
FAN3 | 7100 RPM | ok
FANA | 300 RPM | nr

for FANA (I guess it means No Reading?), but also ok readings once in a while.

This issue really came with this last update.
How do I say not to monitor FANA then for instance, instead of dropping IPMI alerts all together :D

 

[termehansen]

update from comment above. Lowered lower thresh in ipmitool for FANA, and seems to help me for now

ipmitool sensor thresh "FANA" lower 0 100 200

as I saw here in the same issue: https://www.truenas.com/community/threads/hundreds-of-fan-fana-deasserted-errors.108408/

 

[avalon60]

How do you change the fan speeds in the ipmi tool as I can't see how,to do it.
Thanks

 

[sretalla]

How do you change the fan speeds in the ipmi tool as I can't see how,to do it.

It's in my post above...

Update causing Fan errors

I have just updated to TTrueNAS-13.0-U4 and I am getting these errors: New alerts: * Fan FAN 4 Deasserted Lower Non-critical going low : Reading 750 < Threshold 600 RPM. New alerts: * Fan FAN 4 Asserted Lower Non-critical going low : Reading 600 < Threshold 600 RPM. Current alerts: * Fan FAN 4...

www.truenas.com

I guess I didn't include the bit about zones in that post, so maybe that's what you're missing:

Code:

## FAN ZONES
## Your CPU/case fans should probably be connected to the main fan sockets,
## which are in fan zone zero
## Your HD fans should be connected to FANA which is in Zone 1
## You could switch the CPU/HD fans around, as long as you change the zones
## and fan header configurations.
##
## 0 = FAN1..5
## 1 = FANA..FANC

 

[David Henrickson]

Yep...same thing. This isn't a motherboard issue nor fan4 header issue. This is now directly a TrueNAS issue and a bug that needs to be updated. Supermicro BIOS and IPMI show perfect health, TrueNAS is showing the faulty connection.