Analyzing Boot Error Messages on a Sun Fire[TM] T1000 and T2000 (Doc ID 1006826.1)

Last updated on NOVEMBER 29, 2022

Applies to:

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