Multiple environment sensor reading issues reported, node not booting

• Newly deployed controller powers on with multiple errors referred to sensor readings against FANs

callhome.c.fan.fru.fault: Call home for CHASSIS FAN FRU FAILED: Fan2_1

monitor.globalStatus.critical: Multiple fans has failed: SysFan4 F2, SysFan3 F1, SysFan2 F2, SysFan2 F1, SysFan1 F2, SysFan1 F1.

• Motherboard power cycling and reseat does not solve the issue.
• After motherboard replacement additional environment sensor errors are experienced:
  • NVBattery errors are observed

WARNING: The battery is experiencing a critical failure:


- Internal error. Failed to communicate with the Environment Manager
Without a working battery, the system cannot retain data
during a power outage, which can result in data loss.
Power down the system and verify that the battery is
properly installed.

• • Sensors and i2c bus stuck errors are observed during boot sequence:

[Node01:netif.sfpEventErrorCode:error]: Unsupported or faulty transceiver or cable in port e0h. Error :Bus stuck(I2C or data shorted).
[Node01:netif.sfpEventErrorCode:error]: Unsupported or faulty transceiver or cable in port e0h. Error :Bus stuck(I2C or data shorted).
[Node01:monitor.power.unreadable:error]: A power sensor PVCCIN CPU0 in the controller module is not readable.
[Node01:monitor.power.unreadable:error]: A power sensor PVCCIN CPU1 in the controller module is not readable.
[Node01:monitor.power.unreadable:error]: A power sensor PVDDQ ABC in the controller module is not readable.
[Node01:monitor.power.unreadable:error]: A power sensor PVDDQ DEF in the controller module is not readable.
[Node01:monitor.power.unreadable:error]: A power sensor PVDDQ GHI in the controller module is not readable.
[Node01:monitor.power.unreadable:error]: A power sensor PVDDQ KLM in the controller module is not readable.

• After BMC upgrade to latest version (13.10P1 by the time of this KB creation) node is able to boot up, but fails again shortly.