Analyzing Boot Error Messages on a Sun Fire[TM] T1000 and T2000

Asset ID:	1-75-1006826.1
Update Date:	2017-06-07
Keywords:

Solution Type Troubleshooting Sure

Solution 1006826.1 : Analyzing Boot Error Messages on a Sun Fire[TM] T1000 and T2000

Applies to:

Sun Fire T2000 Server
Sun Fire T1000 Server
All Platforms

Purpose

Description
Errors are generated and reported to the console or the /var/adm/messages file during the boot sequence.

These errors may be caused by missing patches, down-level firmware or missing etc/system file settings. If applicable:

The Sun Fire[TM] T1000 may report SUNW-MSG-ID errors related to: SUNOS-8000-1L

The Sun Fire[TM] T2000 may report SUNW-MSG-ID errors related to: SUN4-8000-ER, SUN4-8000-0Y, SUN4-8000-75, SUN4-8000-D4, or the PCI-Express subsystem

Symptoms:

Example of what may be seen on the console or in /var/adm/messages:

SUNW-MSG-ID: SUN4-8000-0Y, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: Fri Jan 27 22:17:36 GMT 2006
PLATFORM: SUNW,Sun-Fire-T200, CSN: -, HOSTNAME: x
SOURCE: eft, REV: 1.13
EVENT-ID: d79b51d1-aca0-c786-aa50-c8f35ea0fba3
DESC: A problem was detected in the PCI-Express subsystem.
Refer to http://sun.com/msg/SUN4-8000-0Y for more information.

To check the FMA logs for these messages use the command:

#  fmdump -v

TIME                 UUID                                 SUNW-MSG-ID
Apr 16 13:54:13    d79b51d1-aca0-c786-aa50-c8f35ea0fba3   SUN4-8000-0Y

If the system shows that the fltlog is empty, the following will be displayed.

# fmdump -v
TIME                 UUID                                 SUNW-MSG-ID
fmdump: /var/fm/fmd/fltlog is empty

Note:

The system may have the required patches, firmware and /etc/system entries installed and applied but still will need to have the previous faults (if any) cleared.

Troubleshooting Steps

Steps to Follow
Please validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

To Analyze Boot Error Messages on a Sun Fire[TM] T1000 and T2000:

1. Verify that the required patch are installed and that they are at the required level for the version of Solaris^[TM] that is being used. For further information reference:

- For the Sun Fire T2000: <Document: 1009719.1> : Confirming that the Sun Fire T2000 has the minimum required Solaris patches and /etc/system entries applied

- For the Sun Fire T1000: <Document: 1008343.1> : Confirming that the Sun Fire [TM] T1000 has the minimum required Solaris patches applied.

2. Verify that the firmware is at or beyond the needed levels.

For further information reference <Document: 1012949.1> :How to determine the system firmware version on Sun Fire[TM] T1000/T2000

3. Verify that the faults have been cleared from both the System Controller (SC) and Solaris FMA.

For further information reference <Document: 1004229.1> : Clearing the FMA faults from Solaris[TM] and SC (System Controller) on Sun Fire[TM] T1000/T2000

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. Gather the needed data by running explorer -w default,Tx000. Reference document: Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT Doc ID 1153444.1 . For additional support contact My Oracle Support (MOS)

Normalized, T2000, T1000, boot, error, FMA, SUNOS-8000-1L, SUN4-8000-ER, SUN4-8000-0Y, SUN4-8000-75, SUN4-8000-D4, PCI-Express subsystem, patch, firmware, etc/system
Previously Published As 88051

Attachments

This solution has no attachment