Sun Microsystems Sun Fire V440 Diagnostics And Troubleshooting Manual page 155

The following sample output shows the system booting and loading Solaris software
consolehistory boot -v Command Output (System Booting and Loading Solaris
CODE EXAMPLE 7-13
Software)
Rebooting with command: boot disk
Boot device: /pci@1f,700000/scsi@2/disk@0,0
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.11 97/07/10 16:19:15.
Loading: /platform/SUNW,Sun-Fire-V440/ufsboot
Loading: /platform/sun4u/ufsboot
\
SunOS Release 5.8 Version Generic_114696-04 64-bit
Copyright 1983-2003 Sun Microsystems, Inc.
Hardware watchdog enabled
sc>
4. Check the /var/adm/messages file for indications of an error.
Look for the following information about the system's state:
Any large gaps in the time stamp of Solaris software or application messages
Warning messages about any hardware or software components
Information from last root logins to determine whether any system administrators
might be able to provide any information about the system state at the time of the
hang
5. If possible, check whether the system saved a core dump file.
Core dump files provide invaluable information to your support provider to aid in
diagnosing any system problems. For further information about core dump files, see
"About the Core Dump Process" on page 113 and "Managing System Crash
Information" in the Solaris System Administration Guide.
6. Check the system LEDs.
You can use the ALOM system controller to check the state of the system LEDs. See
the Sun Fire V440 Server Administration Guide for information about system LEDs.
7. Examine the output of the prtdiag -v command. Type:
sc> console
Enter #. to return to ALOM.
# /usr/platform/'uname -i'/sbin/prtdiag -v
The prtdiag -v command provides access to information stored by POST and
OpenBoot Diagnostics tests. Any information from this command about the current
state of the system is lost if the system is reset. When examining the output to
identify problems, verify that all installed CPU modules, PCI cards, and memory
File and args:
All rights reserved.
Chapter 7 Troubleshooting Hardware Problems 137