Community
cancel
Showing results for 
Search instead for 
Did you mean: 
YKorc
Beginner
1,624 Views

S2600CP - Power Source Fan runs too fast and loud after BIOS Update to R02.06.E0006-rev2.

Before I had the same problem with motherboard which reported Platform ID as S2600SDP

Intel has replaced motherboard to me by standard warranty as wrong motherboard

New board has correct identification. And Power Supply FAN was working quietly.

Support person recommended me to upgrade BIOS on new received board and the story has repeated.

 

Power Supply fan rotates at max speed.

It is not PS Fan fault. It is some other fault.

As I know already, the loud PS Fan is made for signalling of critical system faults.Customer support by phone replies too slow.

So I decided to ask here.

Please, help me identify the fault source. ( taking into account that fault raised right after BIOS UPGRADE )

I attach sysinfo logfiles here

Thank you.

0 Kudos
10 Replies
YKorc
Beginner
277 Views

77 09/25/2018-21:37:39 Fan, System Fan 1 (# 0x30) Informational event: System Fan 1 reports the sensor is no longer in a low non-critical state. Sensor reading: 0.000000 RPM. Threshold value: 462.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 78 09/25/2018-21:37:39 Fan, System Fan 1 (# 0x30) Informational event: System Fan 1 reports the sensor is no longer in a critically low state. Sensor reading: 0.000000 RPM. Threshold value: 392.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 79 09/25/2018-21:37:39 Fan, System Fan 2 (# 0x31) Informational event: System Fan 2 reports the sensor is no longer in a low non-critical state. Sensor reading: 0.000000 RPM. Threshold value: 460.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 80 09/25/2018-21:37:40 Fan, System Fan 2 (# 0x31) Informational event: System Fan 2 reports the sensor is no longer in a critically low state. Sensor reading: 0.000000 RPM. Threshold value: 400.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 81 09/25/2018-21:37:40 Physical Security (Chassis Intrusion), Physical Scrty (# 0x4) Informational event: Physical Scrty reports there has been a chassis intrusion. Integrated BMC - LUN# 0 (Channel# 0) 82 09/25/2018-21:37:46 System Event, BIOS Evt Sensor (# 0x83) Informational event: BIOS Evt Sensor reports Timestamp Clock Sync. Event is first of two expected events from BIOS on every power on. BIOS POST - LUN# 0 (Channel# 0) 83 09/25/2018-21:37:46 System Event, BIOS Evt Sensor (# 0x83) Informational event: BIOS Evt Sensor reports Timestamp Clock Sync. Event is second of two expected events from BIOS on every power on. BIOS POST - LUN# 0 (Channel# 0) 84 09/25/2018-21:37:56 Fan, System Fan 1 (# 0x30) Warning event: System Fan 1 reports the sensor is in a low, but non-critical, and going lower state. Sensor reading: 0.000000 RPM. Threshold value: 462.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 85 09/25/2018-21:37:56 Fan, System Fan 1 (# 0x30) CRITICAL event: System Fan 1 reports the sensor is in a low, critical, and going lower state. Sensor reading: 0.000000 RPM. Threshold value: 392.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 86 09/25/2018-21:37:56 Fan, System Fan 2 (# 0x31) Warning event: System Fan 2 reports the sensor is in a low, but non-critical, and going lower state. Sensor reading: 0.000000 RPM. Threshold value: 460.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0) 87 09/25/2018-21:37:56 Fan, System Fan 2 (# 0x31) CRITICAL event: System Fan 2 reports the sensor is in a low, critical, and going lower state. Sensor reading: 0.000000 RPM. Threshold value: 400.000000 RPM. Integrated BMC - LUN# 0 (Channel# 0)

These messages appeared in SEL after BIOS update

 

Does it mean that system MUST have system fans 1,2 ?

 

Is it possible to reset RPM threshold to zero?
idata
Community Manager
277 Views

Hello Yaroslav-Korchevsky,

 

 

Is common if the Fans run high at the beginning but it should drop down after a few minutes.

 

I will recommend to first to do a BIOS Default.

 

If the problem persists either to re-flash the BIOS and make sure to select all options.

 

 

The threshold can not be set to Zero.

 

 

If there is anything else we can help please feel free to ask.

 

 

Best regards,

 

 

Henry A.
YKorc
Beginner
277 Views

I did already set BIOS defaults and BIOS reflashing several times.

It didn't help

Moreover, I installed system fans 1 and 2

FAN_1 and FAN_2 warning and error messages stopped to appear in SEL after it.

However Power Supply fan still runs at maximum and do not reduce rotation speed further.

Runs high always after short RPM drop at power on.

I found another message, which looks suspicious

Management Subsystem Health, BMC FW Health (# 0x10) Warning event: BMC FW Health reports the sensor has failed and may not be providing a valid reading.

I set BIOS defaults in BIOS menu by F9 key

Is there any difference of resetting BIOS settings with "CLEAR CMOS" jumper?

Issue still persists .

idata
Community Manager
277 Views

Hello Yaroslav-Korchevsky,

 

 

First, BIOS Defaults with F9 Defaults Clear CMOS jumper are pretty much the same. The jumper is used for more deep problems when you don't have access to the CMOS at all.

 

 

Also, if installed the Fans 1 and 2 then you will need to do a Full BIOS Flashed so it will detect the Fans on the configuration.

 

 

Another option after the BIOS is reflashed with the 2 additional Fans will be, if possible, to test another power supply to ensure if the problem is the power supply or system board.

 

 

If there is anything else we can help please feel free to ask.

 

 

Best regards,

 

 

Henry A.
YKorc
Beginner
277 Views

I have been struggling with this issue already few weeks.

 

I made tests with PS swapping in various combinations.

I definitely does not depend of Power Source.

 

It comes with BIOS reflashing.

 

I have the same result on two S2600cp boards.

 

Before flashing - Power Source Fan works at low speed

After flashing - works with max speed.

This RPM raise happens right after FRUSDR phase of BIOS update.

By my opinion the R02.06.E006_rev2 has some issue in SDR

 

However, I can not identify what exactly is wrong.

 

Is it SDR configuration or BMC error.

 

I don't think it is the issue of IPMI upgrade.

The SDR record 12 indicates

Management Subsystem Health, BMC FW Health (# 0x10) Warning event: BMC FW Health reports the sensor has failed and may not be providing a valid reading.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

Displaying SDR Record id: 12

0c 00 51 02 28 20 00 10 07 01 67 40 28 6f 10 00 ..Q.(.....g@(o..

00 00 10 00 c0 00 00 01 00 00 00 00 00 00 00 cd ................

42 4d 43 20 46 57 20 48 65 61 6c 74 68 BMC.FW.Health

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Before BIOS flashing the log didn't have these event entries

I believe, the BIOS detects BMC FW Heath issue and commands the PS to unlimit rotation speed.

I found the document IPMI specification, which allows me to parse SDR

But I don't understand the meaning of SDR fields

YKorc
Beginner
277 Views

I flashed original version of BIOS to the board and error gone.

Fan works at normal speed

BMC version 01.21.6580

BIOS version 02.03.0003

ME version 02.01.07.328. didn't change

I can upgrade back to R02.06.E006 rev 2. but without SDR change

I believe, that SDR makes problem.

idata
Community Manager
277 Views

Hello Yaroslav-Korchevsky,

 

 

I am glad the fans are spinning at the correct speed now.

 

Yes you can flash to rev. 2 without the SDR.

 

 

If there is anything else we can help please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
277 Views

Hello Yaroslav-Korchevsky,

 

 

I just wanted to follow and see if there is something else I can help you with.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
277 Views

Hello Yaroslav-Korchevsky,

 

 

I just wanted to follow on a case that is still open with the issue "state issue here summary", we know that this is important for you to get it resolved and it is also equally important for us to get you the right solution. Since we have not seen an update for 9 days, the case will automatically close after 2 business days.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
277 Views

Hello Yaroslav-Korchevsky,

 

 

I just wanted to follow on a case that is still open with the issue "state issue here summary", we know that this is important for you to get it resolved and it is also equally important for us to get you the right solution. Since we have not seen an update for 9 days, the case will automatically close after 2 business days.

 

 

Best regards,

 

 

Henry A.
Reply