T2000 Won't Power On; Missing/Inconsistent FRU Data

Asset ID:	1-72-2115361.1
Update Date:	2017-06-19
Keywords:

Solution Type Problem Resolution Sure

Solution 2115361.1 : T2000 Won't Power On; Missing/Inconsistent FRU Data

Applies to:

Sun Fire T2000 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Sometimes missing components may produce inconsistent or incorrect fault list in service processor.

Internal status monitoring buses, like i²c, may depend of availability of some components, otherwise multiple components may be found faulty when they actually are not.

For instance, given a T2000 with IOBD (IO-Board) presenting erratic FRU information:

sc> showfru

...[snip]...

FRU_PROM at IOBD/SEEPROM
ERROR: RO crc test failed
ERROR: RW crc test failed
Failed to print information
FRU_PROM at MB/SEEPROM

...[snip]...

May lead to additional components sensors failing, or not being detected (UNKNOWN). Some of those error messages may lead to misdiagnose.

sc> showlogs

...[snip]...

MAR 09 10:04:36: 0004006c: "VOLTAGE_SENSOR at IOBD/V_+3V3STBY has exceeded high soft shutdown threshold."
MAR 09 10:04:39: 00040069: "VOLTAGE_SENSOR at IOBD/V_+1V has exceeded low soft shutdown threshold."
MAR 09 10:04:42: 00040069: "VOLTAGE_SENSOR at IOBD/V_+1V2 has exceeded low soft shutdown threshold."
MAR 09 10:04:44: 0004006c: "VOLTAGE_SENSOR at IOBD/V_+5V has exceeded high soft shutdown threshold."
MAR 09 10:04:48: 00040069: "VOLTAGE_SENSOR at IOBD/V_-12V has exceeded low soft shutdown threshold."
MAR 09 10:04:51: 0004006c: "VOLTAGE_SENSOR at IOBD/V_+12V has exceeded high soft shutdown threshold."
...[snip]...
MAR 09 10:05:00: 0004006c: "VOLTAGE_SENSOR at IOBD/V_+3V3MAIN has exceeded high soft shutdown threshold."
MAR 09 10:05:00: 0004006e: "VOLTAGE_SENSOR at IOBD/V_+3V3STBY is within normal range."
MAR 09 10:05:07: 0004006e: "VOLTAGE_SENSOR at IOBD/V_-12V is within normal range."
MAR 09 10:05:20: 00040069: "VOLTAGE_SENSOR at IOBD/V_+3V3STBY has exceeded low soft shutdown threshold."
...[snip]...
MAR 09 10:09:21: 0004004f: "Indicator FT2/SERVICE is now UNKNOWN"
MAR 09 10:09:23: 0004004f: "Indicator FT2/SERVICE is now OFF"
MAR 09 10:09:27: 0004004f: "Indicator FT2/SERVICE is now UNKNOWN"

During POST, you may also notice i²c subsystem tests failing:

sc> showlogs

Log entries since MAR 09 07:51:40
----------------------------------
MAR 09 07:51:40: 00040072: "PSU at PS1 has been inserted."
MAR 09 07:51:42: 0004004f: "Indicator SYS/ACT is now STANDBY BLINK"
MAR 09 07:51:45: 00040029: "Host system has shut down."
MAR 09 08:01:52: 00080000: "Starting Diagnostic Tests..."
MAR 09 08:01:59: 00080002: "ERROR: MB/IOEXP58.MONITOR (0x5C) Read FAILED"
MAR 09 08:01:59: 00080002: "ERROR: I2C Subsystem Test (i2ctest) FAILED"

Cause

The cause of this error may not be trivial, and requires engaging Oracle Support Services.

Solution

If your T2000 system has a similar behavior, with multiple components failing, with i²c errors during POST, please collect diagnosis data from Service Processor and create a Service Request in MOS (My Oracle Support):

sc> showhost
sc> showenvironment
sc> showplatform
sc> showfru
sc> showlogs
sc> showsc
sc> consolehistory -v

Chances are some of the error messages or faulty components are side-effects of a single component failure.

Internal note:

When troubleshooting i²c problems with T2000, notice IOBD is major component in terms of i²c bus dependency. Other components may also impact i²c, as PDB and internal cable PDB/IOBD.

Recommendation is checking reported suspect components and analyze wiring diagram in order to track the probable failing component.

https://mosemp.us.oracle.com/handbook_internal/Systems/SunFireT2000/wiring_1.html

Attachments

This solution has no attachment