I am sure from Supermicro perspective changing the fan thresholds is considered a hack and an unsupported change, hence their comments.You can definitely lower the fan thresholds.
I am sure from Supermicro perspective changing the fan thresholds is considered a hack and an unsupported change, hence their comments.You can definitely lower the fan thresholds.
ipmitool -H HOSTNAME -I lanplus -U ADMIN sensor
FAN1 | 300.000 | RPM | cr | 200.000 | 300.000 | 500.000 | 25300.000 | 25400.000 | 25500.000
FAN2 | 700.000 | RPM | ok | 200.000 | 300.000 | 500.000 | 25300.000 | 25400.000 | 25500.000
FAN3 | 1100.000 | RPM | ok | 200.000 | 300.000 | 500.000 | 25300.000 | 25400.000 | 25500.000
FAN4 | 1800.000 | RPM | ok | 200.000 | 300.000 | 500.000 | 25300.000 | 25400.000 | 25500.000
FAN5 | 1100.000 | RPM | ok | 200.000 | 300.000 | 500.000 | 25300.000 | 25400.000 | 25500.000
ipmitool -H HOSTNAME -I lanplus -U ADMIN sensor thres FAN1 lower 100 150 250
Just be warned that I've had two SM motherboards with Noctua fans where the rpm actually dropped to 0, so the revving would happen regardless of whatever thresholds I set. Annoying, but seems to be a quirk of the SM IPMI combined with some of the Noctua fans.Changing the fan thresholds fixed the problem for me
ipmitool -H HOSTNAME -I lanplus -U ADMIN sensor thres FAN1 lower 100 150 250
Do you know what fan(s) you used?Just be warned that I've had two SM motherboards with Noctua fans where the rpm actually dropped to 0
this computer is not with me now, but i think it's a NF-F12 PMW.Do you know what fan(s) you used?
Pretty sure it was the NF-S12A's that gave me that particular problem; I think I've used the NF-F12's successfully although I just tend to avoid using Noctua fans with SuperMicro boards as a whole now. FWIW I've never had the same problem with any of my ASRR IPMI implementations, touch wood.Do you know what fan(s) you used?