Submit comments about this document at: http://www.sun.com/hwdocs/feedback
Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc.
has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without
limitation, these intellectual property rights might include one or more of the U.S. patents listed at http://www.sun.com/patents and one
or more additional patents or pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and
decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of
Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product might be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in
the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, docs.sun.com, Sun Blade, SunVTS, SunSolve, SunFastEthernet, Sun Quad FastEthernet, SunPCi,
SunHSI/P, OpenBoot, SunSwift, StorEdge, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in
other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other
countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The Energy Star logo is a
registered trademark of the EPA. FireWire and the FireWire logo are trademarks of Apple Computer, Inc., used under license.
The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges
the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun
holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN
LOOK GUIs and otherwise comply with Sun’s written license agreements.
As an Energy Star partner, Sun Microsystems, Inc. has determined that configurations of this
product that bear the Energy Star Logo meet the Energy Star guidelines for energy efficiency.
Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the Sun Microsystems, Inc. license agreements and as
provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct. 1998), FAR 12.212(a) (1995), FAR 52.227-19, or
FAR 52.227-14 (ALT III), as applicable.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés. Sun Microsystems,
Inc. a les droits de propriété intellectuels relatants à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et
sans la limitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à
http://www.sun.com/patents et un ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et
dans les autres pays.
Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la
décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, parquelque moyen que ce soit, sans
l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y ena.
Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des
fournisseurs de Sun.
Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque
déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, docs.sun.com, Sun Blade, SunVTS, SunSolve,SunFastEthernet, Sun Quad FastEthernet, SunPCi, SunHSI/P,
OpenBoot, SunSwift, StorEdge, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et
dans d’autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc.
aux Etats-Unis et dans d’autres pays. Les produits protant les marques SPARC sont basés sur une architecture développée par Sun
Microsystems, Inc. FireWire et le logo de FireWire sont des marques de’pose’es de Applex Computer, Inc., utilise’ sous le permis.
L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun
reconnaît les efforts de pionniers de Xerox pour la recherche et le développment du concept des interfaces d’utilisation visuelle ou graphique
pour l’industrie de l’informatique. Sun détient une license non exclusive do Xerox sur l’interface d’utilisation graphique Xerox, cette licence
couvrant également les licenciées de Sun qui mettent en place l’interface d ’utilisation graphique OPEN LOOK et qui en outre se conforment
aux licences écrites de Sun.
LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES
OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A
L’ABSENCE DE CONTREFAÇON.
Please
Recycle
Contents
Preface xxxi
1.Start Here 1–1
1.1Diagnostic Tools Available 1–1
1.2About Flowcharts 1–3
1.3How to Use This Manual 1–4
2.Product Description 2–1
2.1Product Overview 2–1
2.2External System Description 2–3
2.3Replaceable Components 2–7
2.4Supported Sun Monitors 2–10
3.Basic Troubleshooting 3–1
3.1Power-On Sequence 3–1
3.2Display and Audio Responses 3–2
3.2.1Displayed Screens 3–2
3.2.2Displayed Messages 3–5
3.2.3Audio Responses 3–12
3.3Troubleshooting Commands 3–15
3.3.1iostat Command 3–15
iii
3.3.2prtdiag Command 3–18
3.3.3prtconf Command 3–20
3.3.4netstat Command 3–23
3.3.5ping Command 3–25
3.3.6ps Command 3–27
3.3.7prstat Command 3–29
4.Troubleshooting Flowcharts 4–1
4.1Power-On Flowchart 4–2
4.2Start Up Problems 4–5
4.2.1Power Problem 4–6
4.2.2Hard Drive Problem 4–8
4.2.3System Fan Problem 4–9
4.2.4USB Problem 4–10
4.2.5Audio Output Problem 4–12
4.2.6Monitor Problem 4–14
4.2.7Network Problem 4–17
4.2.8Keyboard Problem 4–19
4.2.9Login Problem 4–20
4.2.10Graphical User Interface Problem 4–22
4.2.11Data Access and Running Applications Problem 4–23
4.3Storage Problems 4–24
4.3.1Optical Drive Problem 4–25
4.3.2PCI Card Problem 4–28
4.3.3IEEE 1394 Problem 4–30
4.3.4Smart Card Reader Problem 4–32
4.4Advanced Problems 4–33
4.4.1Motherboard Problem 4–34
4.4.2Memory Problem 4–37
iv Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
xxx Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Preface
The Sun Blade 1500 Service, Diagnostic, and Troubleshooting Manual is an aid to
troubleshooting problems with and replacing components within the Sun Blade 1500
workstation.
Note – This document is intended for users of Sun Blade 1500 systems with a silver
bezel. If your system has a red bezel, refer to the Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual, 816-7564.
This manual is written for technicians, service personnel, and system administrators
who service and repair computer systems.
The person qualified to use this manual:
■ Can open a system chassis, identify, and replace internal components.
■ Understands the Solaris™ Operating System and the command-line interface.
■ Has superuser privileges for the system being serviced.
If you are not comfortable performing any of the procedures described in this book,
refer to your Sun™ Microsystems™ service representative.
xxxi
About the Multimedia Links in This
Manual
Removal and replacement procedures for selected workstation components are
illustrated with interactive audio and video instructions in the Sun Blade 1500
ShowMe How™ multimedia documentation. This multimedia documentation is
available through links to ShowMe How movie files located throughout this manual.
You can access these multimedia video clips wherever you see the film-clip icon; as
shown in
FIGURE P-1 Link to Multimedia Instructions
Clicking on the above link displays a guided tour of the Sun Blade 1500 workstation.
FIGURE P-1.
How This Book Is Organized
Chapter 1 explains how to use the flowcharts in this manual.
Chapter 2 provides a product description of the Sun Blade 1500 workstation.
Chapter 3 contains basic troubleshooting tasks, commands, and system responses.
Chapter 4 provides the troubleshooting flowcharts for the Sun Blade 1500
workstation.
Chapter 5 introduces advanced troubleshooting using Power-On Self-Test (POST),
OpenBoot™ Diagnostics, and SunVTS™ software.
Chapter 6 provides information about the NVRAM and alternatives to the Stop-A
and Stop-N key commands.
Chapter 7 describes using POST to diagnose problems with the Sun Blade 1500
workstation.
xxxii Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Chapter 8 instructs how to use OpenBoot Diagnostics to troubleshoot the Sun Blade
1500 workstation.
Chapter 9 summarizes using SunVTS software to exercise a Sun Blade 1500
workstation and its components.
Chapter 10 provides preliminary steps necessary to prepare for component
replacement.
Chapter 11 contains replacement procedures for components found on the
motherboard.
Chapter 12 has replacement procedures for data storage components.
Chapter 13 explains replacement procedures for components that are part of the Sun
Blade 1500 chassis.
Chapter 14 describes how to replace system cabling.
Chapter 15 provides steps to finish component replacement.
Chapter 16 describes how to customize your Sun Blade 1500 workstation.
Appendix A lists the specifications of the Sun Blade 1500 workstation.
Appendix B outlines the external signal descriptions.
Appendix C provides a functional description of the Sun Blade 1500 workstation.
Appendix D describes how to manage power-saving modes of the Sun Blade 1500
workstation.
Safety Information
Read this section before beginning any procedure in the Sun Blade 1500 Diagnostics, Service, and Troubleshooting Manual. For your protection, observe the following safety
precautions when removing or installing components, configuring, and
troubleshooting your Sun Blade 1500 workstation.
■ Follow all cautions and instructions marked on the equipment.
■ Make sure that the voltage and frequency of your power source match the voltage
and frequency inscribed on the equipment’s electrical rating label.
■ Never push objects of any kind through openings in the equipment. Dangerous
voltages might be present. Conductive foreign objects could produce a short
circuit that could cause fire, electric shock, or damage to your equipment.
Preface xxxiii
Caution – Hazardous voltages are present. To reduce the risk of electric shock and
danger to personal health, follow the instructions.
Caution – Do not operate Sun products without the access cover in place. Failure to
follow this precaution might result in personal injury or equipment damage.
Caution – There is a risk of personal injury and equipment damage. Follow the
instructions.
The book, Important Safety Information for Sun Hardware Systems, 816-7190, contains a
listing of safety precautions for Sun workstations. The document is located in the
packing carton for the Sun Blade 1500 workstation.
The Sun Blade 1500 workstation complies with regulatory requirements of safety
and EMI as documented in the Sun Blade 1500 Safety and Compliance Guide, 817-5130.
This document is available online at:
■ http://www.sun.com/documentation
■ http://docs.sun.com
Using UNIX Commands
This document might not contain information on basic UNIX® commands and
procedures such as shutting down the system, booting the system, and configuring
devices.
See one or more of the following for this information:
■ Solaris Handbook for Sun Peripherals
■ Online documentation for the Solaris operating system available at:
http://docs.sun.com
■ Sun Blade 1500 Getting Started Guide, 817-5129
■ Sun Blade 1500 Troubleshooting Card, 817-5125
■ Other software documentation that you received with your system
xxxiv Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Typographic Conventions
*
Typeface
MeaningExamples
AaBbCc123The names of commands, files,
and directories; on-screen
computer output
AaBbCc123
AaBbCc123Book titles, new words or terms,
* Your browser settings might differ
What you type, when contrasted
with on-screen computer output
words to be emphasized.
Replace command-line variables
with real names or values.
Edit your.login file.
Use ls-a to list all files.
% You have mail.
% su
Password:
Read Chapter 6 in the User’s Guide.
These are called class options.
You must be superuser to do this.
To delete a file, type rm filename.
Preface xxxv
Shell Prompts
ShellPrompt
C shell machine-name%
C shell superuser machine-name#
Bourne shell and Korn shell $
Bourne shell and Korn shell superuser#
Related Documentation
TABLE P-1 Related Documentation
ApplicationTitlePart Number
Setting up posterSun Blade 1500 Start Here817-5123
Handy reference
information
Preinstalled softwareSun Blade 1500Getting Started Guide817-5129
Last minute informationSun Blade 1500Product Notes817-5131
Safety and complianceSun Blade 1500Safety and Compliance Guide817-5130
ConfigurationSolaris 8 2/04 Sun Hardware Platform Guide817-4347
Important Safety Information for Sun Hardware
Systems
Solaris 9 9/04 Sun Hardware Platform Guide817-6357
Solaris Handbook for Sun Peripherals816-4468
SunVTS Quick Reference Card816-5146
SunVTS 5.1 Test Reference Manual816-5145
SunVTS 5.1 Patch Set 5 Documentation
Supplement
816-7190
817-4350
xxxvi Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
TABLE P-1 Related Documentation (Continued)
ApplicationTitlePart Number
Graphics accelerator
documentation
Co-processor board
documentation
Sun XVR-100 Graphics Accelerator Installation
Guide
Sun XVR-600 Graphics Accelerator Installation
and User’s Guide
Sun XVR-1200 Graphics Accelerator Installation
and User’s Guide
SunPCi™ III 3.2.1 User’s Guide817-3630
SunPCi III Quick Start Installation Guide817-4343
SunPCi III 3.2.1 Product Notes817-3631
816-7560
817-2195
816-7386
Additional Support Resources
This manual contains troubleshooting flowcharts and diagnostic procedures that
assist in identifying and replacing faulty components. It is written to resolve most
common component failures.
TABLE P-2 lists resources for troubleshooting assistance.
TABLE P-2 Additional Support Resources
Sun Blade 1500 Support ResourcesURL or Telephone Number
Find Solaris and other software documents here.
This is also an alternative web site for some Sun
Blade 1500 documents. This web site has full
search capabilities.
Warranty and Contract Support contacts. Links to
other service tools.
Discussion and Troubleshooting Forums.http://supportforum.sun.com/
Support, Diagnostic Tools, Alerts, for all Sun
products.
SunSolvesm: Contains links to software patches.
Lists some system specifications, troubleshooting
and maintenance information, and other tools.
Lists warranties for every Sun product.
Sun Service Support phone number.1-800-872-4786 (1-800-USA-4Sun) Select Option 1
http://docs.sun.com
http://www.sun.com/service/online
http://www.sun.com/bigadmin/
http://www.sunsolve.sun.com/handbook_pub/
http://www.sun.com/service/support/warranty
Preface xxxvii
TABLE P-2 Additional Support Resources (Continued)
Sun Blade 1500 Support ResourcesURL or Telephone Number
This web site lists international telephone
numbers for Sun Service Support.
Note – Access to some Sun proprietary information is restricted to authorized Sun
personnel.
Some low-level hardware and software failures require troubleshooting techniques
that are beyond the scope of this document, and are best resolved by those persons
with experience and skill in fault analysis. Your Sun Microsystems service
representative can provide these types of services.
You can view, print, or purchase a broad selection of Sun documentation, including
localized versions, at:
http://www.sun.com/documentation
Contacting Sun Technical Support
If you have technical questions about this product that are not answered in this
document, go to:
http://www.sun.com/service/contacting
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and
suggestions. You can submit your comments by going to:
http://www.sun.com/hwdocs/feedback
xxxviii Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Please include the title and part number of your document with your feedback:
Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual, part number 817-5127-
11.
Preface xxxix
xl Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
CHAPTER
1
Start Here
This chapter provides an overview of how to use this manual. The diagnostics and
troubleshooting flowcharts within this manual can help you determine the root
cause of problems that you might encounter with the Sun Blade 1500 workstation.
This chapter contains the following topics:
■ “Diagnostic Tools Available” on page 1-1
■ “About Flowcharts” on page 1-3
■ “How to Use This Manual” on page 1-4
1.1Diagnostic Tools Available
The Sun Blade 1500 Service, Diagnostic, and Troubleshooting Manual uses displayed
messages, system sounds, flowcharts, and firmware and software diagnostic tools to
help you locate and identify workstation malfunctions.
The diagnostic tools used in the Sun Blade 1500 workstation include but are not
limited to:
■ System displayed messages (such as flashing LEDs or error messages)
■ Workstation sounds (such as beeps)
■ Nonvolatile random access memory (NVRAM)
■ Power-on self-test (POST) diagnostics
■ OpenBoot PROM diagnostics
■ SunVTS validation test suite software
■ Solaris diagnostic commands
1-1
TABLE 1-1 provides a summary of these diagnostics tools.
TABLE 1-1 Summary of Diagnostic Tools
Diagnostic ToolType of ToolWhat the Tool DoesHow Tool is Used
System LEDsHardwareShows status of system or of
a specific component.
Power button LED indicates system
state. TPE and optical drive LEDs
indicate activity. Motherboard LED
indicates standby power.
System soundsHardwareIndicates system condition.Beeps heard from workstation internal
speaker indicate POST completion,
Solaris boot, or system failure. See
“Audio Responses” on page 3-12.
NVRAM FirmwareContains properties and flags
to configure system and
diagnostic tests.
The setenv command typed at the ok
prompt or the eeprom command in a
terminal window can configure the
OpenBoot PROM for diagnostics and
automatic execution of scripts. See
“NVRAM” on page 6-1.
POST diagnosticsFirmwareTests workstation core
components such as CPU and
memory.
Checks low-level interaction between
CPU, caches, memory, JBus, and PCI
bridge. Output displayed through serial
port. See
“Power-On Self-Test” on
page 7-1.
OpenBoot
Diagnostics
FirmwareTests system motherboard
and component interfaces.
Component tests are selected from
menu. If component is PCI card with
IEEE 1275 compliant Fcode, internal selftest is executed. See
“OpenBoot
Diagnostics” on page 8-5.
SunVTSSoftwareExercises and stresses
workstation components.
Invoked from the Solaris operating
system. Command-line or GUI user
interface. SunVTS must be installed on
the system under test. See
“SunVTS” on
page 9-1.
Solaris Operating
System
SoftwareCommands display system
information.
Commands iostat, prtdiag,
prtconf, netstat, ping, ps, and
prstat are run with superuser
privileges. See
“Troubleshooting
Commands” on page 3-15.
1-2 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
1.2About Flowcharts
The Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual contains
flowcharts that you can use to:
■ Determine how to use this book.
■ Identify workstation malfunctions.
■ Verify workstation operation after completing the service procedure.
Each flowchart begins with a problem statement and a description of normal
operation.
Flowcharts use structural elements, as described in TABLE 1-2:
TABLE 1-2 Flowchart Elements
ElementDescriptionPurpose
There is a power problem.
Rectangles at the top left and
throughout flow of the flowchart.
Bold text states a problem. Plain text states an
action.
Descriptive text about
normal operation.
Replace the power supply. See “Replacing the
Power Supply” on
page 13-2
Do any system
fans spin?
Y
Go to
A
Rectangle at the top right of the
flowchart.
Rectangle drawn with bold lines.Text gives a cross-reference to another
Diamond shape.Text asks questions to be answered Yes or No.
N
CircleThe letter in the circle directs you to a
Text describes normal operation or provides
details about normal conditions.
flowchart, table, or procedure. The crossreferences are clickable links.
If you answer Yes, move down the chart to
the next element. If you answer No, move
right to the next element.
continuation of the flowchart. Some
flowcharts have more than one continuation
path.
Chapter 1 Start Here 1-3
Note – Some flowcharts also point to additional diagnostic information in other Sun
documents.
1.3How to Use This Manual
When you service the Sun Blade 1500 workstation, begin with the Start Here
flowchart,
■ Troubleshooting
■ Component removal, installation, and verification
■ Workstation customization
■ Product information
START HERE
Is something wrong
with the system?
Y
See “Basic Troubleshoot-
ing” on page 3-1.
FIGURE 1-1. The Start Here flowchart links you to information about:
The start here flowchart helps you identify what section of
this book to read first. Boxes like this one appear at the
start of each flowchart and describe the normal operation
of the Sun Blade 1500 workstation. This box might also
have information to help clarify the flowchart or resolve
the problem.
N
Do you want to replace
a component?
Y
See “Preparing to
Replace Components” on
page 10-1.
N
Do you want
to add a component or
optional component?
Y
See “Customizing Your
System” on page 16-1.
N
See “Product Specifica-
tions” on page A-1.
FIGURE 1-1 Start Here Flowchart
1-4 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
See “Signal Descrip-
tions” on page B-1.
See “Functional Descrip-
tion” on page C-1.
See “Power Manage-
ment” on page D-1.
CHAPTER
2
Product Description
Topics covered in this chapter are:
■ “Product Overview” on page 2-1
■ “External System Description” on page 2-3
■ “Replaceable Components” on page 2-7
■ “Supported Sun Monitors” on page 2-10
2.1Product Overview
The Sun Blade 1500 workstation has the power and expandability to handle a wide
range of tasks. Examples of these tasks range from entry-level 2D graphics EDA
applications to mid-range 3D graphics MCAD applications. Combined with the
power of the Solaris operating system, Sun Blade 1500 workstation offers reliability
and scalability to match the power of its UltraSPARC IIIi.
The Sun Blade 1500 workstation provides the following features in the base
configuration:
■ UltraSPARC IIIi 1.5 GHz 64-bit processor
■ 1 GB of DDR1 memory
■ Sun XVR-100 graphics accelerator
■ 120 GB ATA 100 hard drive
■ High-speed optical drive
2-1
The Sun Blade 1500 workstation is configured with the features described in
TABLE 2-1.
TABLE 2-1 Sun Blade 1500 Configured Features
FeatureDescription
Processor1.5 GHz UltraSPARC IIIi CPU with 1 MB integrated
Level2 cache, heat sink, and fan
Operating systemPreinstalled Solaris 8 2/04 and Solaris 9 9/04
operating system supporting 32 and 64-bit
applications
EnclosureDeskside system enclosure with front-panel access
to optical media drive and smart card reader
Memory optionsFrom a minimum of 1 GB to a maximum of 8 GB of
ECC error-correcting DDR-1 SDRAM memory,
using matched pairs of 512 MB, 1 GB, or 2 GB
DIMMs
Maximum of 2 DIMM pairs per system (4 DIMMS
total)
Power supply420 W autoranging
Internal storageOne or two 120 GB ATA 100 3.5-inch hard drives
(7,200 rpm)
Note: Internal drive mirroring is not supported.
Sun XVR-100 PCI graphics card
Sun XVR-1200 PCI graphics card
Contact your Sun Microsystems service representative if you need a component.
Note – The components listed in TABLE 2-4 are subject to change without notice.
Consult your authorized Sun sales representative or service provider to confirm a
part number prior to ordering a replacement component, or search:
http://www.sun.com/ibb/spares
Chapter 2 Product Description 2-9
2.4Supported Sun Monitors
The Sun Blade 1500 workstation supports the monitors listed in TABLE 2-5. The Sun
XVR-100 and Sun XVR-1200 graphics accelerators can be configured to support
multiple displays.
TABLE 2-5 Monitors supported by the Sun Blade 1500 Workstation
19-inch LCD color1280 x 1024 @ 60/76 HzUp to 21Up to 2
22-inch CRT color1600 x 1200 @ 75 HzUp to 21Up to 2
24.1-inch LCD flat screen color1920 x 1200 @ 60 HzUp to 21Up to 2
Dual monitor support requires special cabling and software configuration. For more
information about the Sun XVR-100, Sun XVR-600, and Sun XVR-1200 graphics
accelerators, refer to the Sun XVR-100 Graphics Accelerator Installation Guide, 8167560, the
the Sun XVR-1200 Graphics Accelerator Installation and User’s Guide, 816-7386.
Sun XVR-600 Graphics Accelerator Installation and User’s Guide, 817-2195, or
2-10 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
CHAPTER
3
Basic Troubleshooting
This chapter provides basic troubleshooting assistance. Topics include:
■ “Power-On Sequence” on page 3-1
■ “Display and Audio Responses” on page 3-2
■ “Troubleshooting Commands” on page 3-15
3.1Power-On Sequence
When you power on the Sun Blade 1500 workstation, a series of tasks and processes
brings the workstation to a user-ready state.
The following lists the sequence of power-on events that occur before a user can
interact with the Sun Blade 1500 workstation.
1. Power button is pressed.
2. OpenBoot PROM initiates system power-on reset (SPOR).
5. OpenBoot PROM loads workstation configuration from NVRAM.
6. OpenBoot PROM initializes bus and PCI card self-test diagnostics.
7. OpenBoot PROM loads and executes boot block.
8. Boot block loads and executes bootstrap program.
9. Bootstrap loads Solaris kernel.
10. Bus connections and hardware components are probed.
3-1
11. init program is loaded and executed.
12. init program reads /etc/inittab.
13. init program launches rc scripts, which read, check, and mount file systems.
14. /etc/vfstab file system is checked and mounted.
15. Additional rc script files are executed.
If the power-on behavior seems erratic, see “Power-On Flowchart” on page 4-3
3.2Display and Audio Responses
Component failures can often be diagnosed by looking at the monitor or listening to
the system. Topics in this section include:
■ “Displayed Screens” on page 3-2
■ “Displayed Messages” on page 3-5
■ “Audio Responses” on page 3-12
3.2.1Displayed Screens
TABLE 3-1 describes what you might see on the monitor, what the images mean, and
where to find assistance in this manual to resolve the problem.
TABLE 3-1 Screen Images and What They Mean
Screen ImagesDescriptionMeaningComment
White screen with
banner and text.
Error message
displayed.
3-2 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Error from
OpenBoot PROM.
Error from Solaris
operating system.
See “OpenBoot PROM
Messages” on page 3-6.
See “Solaris Error Messages” on
page 3-8.
TABLE 3-1 Screen Images and What They Mean (Continued)
Screen ImagesDescriptionMeaningComment
White screen with
banner and text.
Information
displayed in banner
is incorrect.
Display has
flickering horizontal
lines.
GUI is too small,
too large, or not
centered.
Corruption of
OpenBoot PROM.
Corruption of
NVRAM.
Monitor sync
problem.
Monitor settings
or sync problem.
See “OpenBoot PROM
Messages” on page 3-6.
See “NVRAM Problem” on
page 4-39.
Verify monitor can sync to set
frequency. See
“Graphics
Accelerators” on page C-21. Also
see monitor documentation.
See “Monitor Problem” on
page 4-14.
See “PCI Card Problem” on
page 4-28.
Adjust monitor according to
monitor manual.
Verify monitor can sync to set
frequency. See
“Graphics
Accelerators” on page C-21.
See “Monitor Problem” on
page 4-14.
White bar with
black text across
GUI.
Error message in
terminal window.
Error occurred in
Solaris kernel.
Error occurred in
process started
from that terminal.
See “Other Messages” on
page 3-11.
See “Solaris Error Messages” on
page 3-8.
See “Other Messages” on
page 3-11.
See “Graphical User Interface
Problem” on page 4-22.
Chapter 3 Basic Troubleshooting 3-3
TABLE 3-1 Screen Images and What They Mean (Continued)
Screen ImagesDescriptionMeaningComment
Ψ∆
ΣΦΞ
GUI colors flash or
are wrong.
GUI has artifacts.Graphics
GUI is in wrong
language.
Color registers
exhausted.
Monitor problem.See “Monitor Problem” on
accelerator
problem.
Locale problem.1. Log out.
Allocate more colors to GUI. See
“Avoiding Colormap Flash” on
page 11-3 7.
page 4-14.
See “PCI Card Problem” on
page 4-28.
2. At the login GUI Options
pulldown, select Language.
3. Select your language.
4. Log in as usual.
Window in GUI is
completely white.
Display is all one
color.
3-4 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Window process is
hung.
Monitor problem.See “Monitor Problem” on
Graphics
accelerator
problem.
NVRAM problem.See “NVRAM Problem” on
See “Graphical User Interface
Problem” on page 4-22.
page 4-14.
See “PCI Card Problem” on
page 4-28.
page 4-39.
TABLE 3-1 Screen Images and What They Mean (Continued)
Screen ImagesDescriptionMeaningComment
Display is black
with hourglass.
Display is black
with mouse pointer.
3.2.2Displayed Messages
When a failure occurs, a message might be displayed on the system’s monitor. Use
the following flowchart to determine which message table addresses the error
message you see.
Network problem.See “Network Problem” on
page 4-17.
Dtlogin problem.See “Login Problem” on
page 4-20.
Network problem.See “Network Problem” on
page 4-17.
Dtlogin problem.See “Login Problem” on
page 4-20.
Chapter 3 Basic Troubleshooting 3-5
An error message is displayed on the system’s
monitor.
Use this flowchart to determine which message table to
look up the error message you see. If the message is not
provided in any table, consult with a system administrator.
Was the Solaris operating
system running?
Y
Was the message
displayed in a white band
with black text across the
GUI?
Y
See “Other Messages” on
page 3-11.
FIGURE 3-1 Displayed Messages Flowchart
N
Is the screen all white
with black text?
See “OpenBoot PROM
Messages” on page 3-6.
N
See “Solaris Error Mes-
sages” on page 3-8.
3.2.2.1OpenBoot PROM Messages
N
Y
See “Displayed Screens”
on page 3-2.
TABLE 3-2 lists some common fault messages or portions of fault messages displayed
by the OpenBoot PROM, their meanings, and what to do next.
TABLE 3-2 OpenBoot PROM Messages and Their Meaning
MessageMeaningWhat to Do
The date is displayed as:
01/01/2000 00:00:00 GMT
3-6 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
The battery has drained.Replace the battery. See
“Replacing the Battery” on
page 11-2 2.
TABLE 3-2 OpenBoot PROM Messages and Their Meaning (Continued)
MessageMeaningWhat to Do
Can’t open boot device
Can’t run OBDIAG from the
device tree node or with the
active instance
NOTICE - CPUx Banky DIMMs are
from different vendors.
NOTICE - CPUx Banky DIMMs have
different architectures and
will not be used.
Searching for self-test methods
. . . Rejecting alloc-mem!
Starting xv-500 self-test
The process “cs00.sh” has been
exited with retcode#256
Timeout waiting for ARP/RARP
packet
/usr/bin/ps/getexecname () has
failed
The device specified for
boot is unavailable.
Attempt to run OpenBoot
Diagnostics from a selected
device node.
A pair of DIMMs are each
from different
manufacturers.
A pair of DIMMs are each
of different architectures.
The DIMMs are not used.
OpenBoot Diagnostics
failed to start. Some devices
might be tied to other
processes.
Sun XVR-1200 PROM error.Type:
The battery has drained.Replace the battery. See
Network connection
problem.
The battery has drained.Replace the battery. See
• For hard drive, check
internal connections. Drive
might be corrupted. See
“Hard Drive Problem” on
page 4-8.
• For optical drive, check that
disc is bootable. Check
internal connections. See
“Optical Drive Problem” on
page 4-25.
• For network, check network
connections. Check boot
server. See “Network
Problem” on page 4-17.
Type:
ok unselect-dev
Install DIMMs in identical
pairs. See
DIMMs” on page 11-2.
Install DIMMs in identical
pairs. See
DIMMs” on page 11-2.
Type:
“Replacing the
“Replacing the
ok unselect-dev
ok show-devs
search for the text: xvr-1200
“Replacing the Battery” on
page 11-2 2.
Check network connection.
“Network Problem” on
See
page 4-17.
“Replacing the Battery” on
page 11-2 2.
Chapter 3 Basic Troubleshooting 3-7
TABLE 3-2 OpenBoot PROM Messages and Their Meaning (Continued)
MessageMeaningWhat to Do
WARNING: Timed out waiting for
NIS to come up
The name service cannot be
found.
Check network connection.
“Network Problem” on
See
page 4-17. Check system name
service configuration
information.
3.2.2.2Solaris Error Messages
TABLE 3-3 lists some common error messages or portions of error messages displayed
while the Solaris operating system is functioning, their meanings, and what to do
next. These messages are high-level and might be related to software, rather than
hardware failure.
TABLE 3-3 Solaris Error Messages and Their Meanings
MessageMeaningWhat to do
Arguments too long
automountd[int]:
server
hostname
responding
Bad address
Bad file number
BAD TRAP
Broken pipe
Bus error
Command not found
Connection closed
(by foreign host)
Too many arguments follow a C shell
command.
An NFS server cannot be mounted.Check the NFS server’s status
The value of an address is invalid.Determine and use the correct
A program error where the application does
not have permission to interact with the file.
Faulty hardware or mismatch of hardware and
its configuration. Can sometimes indicate a
bad or earlier version CPU. Usually precedes a
panic.
Occurs when a pipe (|) directs without data.Check the structure of the
I/O was attempted on a nonexistent device.
Might be caused by invalid file descriptors,
bad memory allocation, or corrupt boot blocks.
The C shell could not find the command you
typed.
Timeout has occurred or network connection
failed from remote host using either
3-12 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
TABLE 3-5 System Sounds at Locations and What They Mean (Continued)
LocationSoundMeaningComment
MonitorTickingMonitor is searching for
video mode or trying to sync.
Very high-pitched whineMonitor cannot sync.Change graphics
Monitor or power
Low-pitched buzzPower supply degraded.Replace the power
supply
Monitor power supply
degraded.
Verify monitor can sync
to set frequency. See
“Graphics
Accelerators” on
page C-21. Also see
monitor
documentation.
See “Monitor Problem”
on page 4-14.
See “PCI Card
Problem” on page 4-28.
accelerator resolution.
See graphics
accelerator
documentation.
See “Monitor Problem”
on page 4-14.
See “PCI Card
Problem” on page 4-28.
supply. See
“Replacing
the Power Supply” on
page 13-2.
Replace the monitor.
Chapter 3 Basic Troubleshooting 3-13
TABLE 3-5 System Sounds at Locations and What They Mean (Continued)
LocationSoundMeaningComment
Front of system
chassis
Front or rear of
system chassis
Upon power on, three
beeps and the system
powers off
Invalid configuration.
Memory or CPU does not
match requirements.
See “Memory Problem”
on page 4-37 or
“Motherboard
Problem” on page 4-34.
Upon power on, four
beeps and the system
powers off
FRU ID checksum error.Replace motherboard.
“Replacing the
See
Motherboard” on
page 11-4 3.
Upon power on, five beeps
and the system powers off
Continuous beepingKeyboard key is stuck or
Internal reset failed.See “Motherboard
Problem” on page 4-34.
See “Keyboard
connection is bad.
Problem” on page 4-19.
Quiet scratchinghard drive heads are moving.Hard drive is normal.
High-pitched humminghard drive bearings are
failing.
Replace the hard drive.
“Replacing a Hard
See
Drive” on page 12-2.
Low shrill soundFront fan bearing is failing.Replace front fan. See
“Replacing the Front
Fan” on page 13-8.
Rear fan bearing is failing.Replace rear fan. See
“Replacing the Rear
Fan” on page 13-15.
Power supply fan bearing is
failing.
Replace the power
supply. See
“Replacing
the Power Supply” on
page 13-2.
Quiet grumbling soundTemperature is such that fans
Fans are normal.
are barely turning.
Silence from fansFront fan is not spinning.
Rear fan is not spinning.
Power supply fan is not
spinning.
See “System Fan
Problem” on page 4-9.
See “Power Problem”
on page 4-6.
3-14 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
TABLE 3-5 System Sounds at Locations and What They Mean (Continued)
LocationSoundMeaningComment
Optical driveRepetitive quiet clunkingDisc is unbalanced.Reposition disc.
Rapid shifting Laser pickup head is moving.Optical drive normal.
Rushing air that is
constant or intermittently
changes
Rushing air that is
rhythmically changing
Very high-pitched
squeaking
Disc is spinning properly.Optical drive normal.
Laser pickup head cannot
locate tracks on disc.
Laser pickup head is out of
alignment.
Try a different disc. If
the problem continues,
“Optical Drive
see
Problem” on page 4-25.
Try a different disc. If
the problem continues,
replace optical drive.
“Replacing the
See
Optical Drive” on
page 12-9.
3.3Troubleshooting Commands
The section discusses superuser commands that assist in troubleshooting problems
with the Sun Blade 1500 workstation. Commands discussed are:
■ “iostat Command” on page 3-15
■ “prtdiag Command” on page 3-18
■ “prtconf Command” on page 3-20
■ “netstat Command” on page 3-23
■ “ping Command” on page 3-25
■ “ps Command” on page 3-27
■ “prstat Command” on page 3-29
Most of these commands are located in the /usr/bin or /usr/sbin directories.
3.3.1iostat Command
The iostat command iteratively reports terminal, drive, and tape I/O activity, as
well as CPU utilization.
Chapter 3 Basic Troubleshooting 3-15
3.3.1.1Options
TABLE 3-6 describes options for the iostat command and how those options can
help troubleshoot the Sun Blade 1500 workstation.
TABLE 3-6 Options for iostat
OptionDescriptionHow It Can Help
No optionReports status of local I/O devices.A quick three-line output of device
status.
-c
-e
-E
-n
-x
Reports the percentage of time the system has
spent in user mode, in system mode, waiting for
I/O, and idling.
Displays device error summary statistics. The
total errors, hard errors, soft errors, and transport
errors are displayed.
Displays all device error statistics.Provides information about devices:
Displays names in descriptive format.Descriptive format helps identify
For each drive, reports extended drive statistics.
The output is in tabular form.
Quick report of CPU status.
Provides a short table with accumulated
errors. Identifies suspect I/O devices.
manufacturer, model number, serial
number, size, and errors.
devices.
Similar to the -e option, but provides
rate information. This helps identify
poor performance of internal devices
and other I/O devices across the
network.
3.3.1.2Examples
The following examples show output for the iostat command and its options.
# iostat
tty dad0 sd0 nfs1 nfs2 cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us sy wt id
0 5 128 15 6 0 0 0 0 0 0 50 3 9 2 8 4 86
# iostat -c
cpu
us sy wt id
2 7 4 87
3-16 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
# iostat -En
c0t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3120026A Revision: 8.01 Serial No: 3JT4H4C2
Size: 120.03GB <120031641600 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: LITE-ON Product: COMBO SOHC-4832K Revision: O3K1
Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
Chapter 3 Basic Troubleshooting 3-17
3.3.2prtdiag Command
The prtdiag command displays configuration and diagnostic information for a
system. The diagnostic information identifies any failed component in the system.
The prtdiag command is located in the /usr/platform/platform-name/sbin/
directory.
Note – The prtdiag command might indicate a slot number different than that
identified elsewhere in this manual. This is normal.
3.3.2.1Options
TABLE 3-7 describes options for the prtdiag command and how those options can
help troubleshoot the Sun Blade 1500 workstation.
TABLE 3-7 Options for prtdiag
OptionDescriptionHow It Can Help
No optionLists system components.Identifies CPU timing and PCI cards installed.
-v
Verbose mode. Displays the
time of the most recent AC
power failure, the most recent
hardware fatal error
information, and (if applicable)
environmental status.
Provides the same information as no option. Additionally
lists fan status, temperatures, ASIC, and PROM revisions.
3.3.2.2Examples
The following examples show output for the prtdiag command and its options.
3-18 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
# /usr/platform/sun4u/sbin/prtdiag
System Configuration: Sun Microsystems sun4u Sun Blade 1500 workstation
System clock frequency: 160 MHZ
Memory size: 1GB
==================================== CPUs ====================================
E$ CPU CPU Temperature
CPU Freq Size Implementation Mask Die Amb. Status Location
--- -------- ---------- ------------------- ----- ---- ---- ------ ------- 0 1500 MHz 1MB SUNW,UltraSPARC-IIIi 3.3 68C 30C online MB/0
================================= IO Devices =================================
Bus Freq Slot + Name +
Type MHz Status Path Model
-------------------------------------------------ControllerID GroupID Labels Status
-------------------------------------------------0 0 MB/DIMM0
0 0 MB/DIMM1
=============================== usb Devices ===============================
Name Port#
------------ ----mouse 1
keyboard 2
Chapter 3 Basic Troubleshooting 3-19
# /usr/platform/sun4u/sbin/prtdiag -v
System Configuration: Sun Microsystems sun4u Sun Blade 1500 workstation
System clock frequency: 160 MHZ
Memory size: 1GB
. . .
============================ Environmental Status ============================
Fan Speeds:
--------------------------------------------Location Sensor Status Speed
--------------------------------------------F2 CPU okay 3183rpm
F1 Intake okay 2280rpm
F0 Outtake okay 2280rpm
Temperature sensors:
----------------------------------------------------------------------------Location Sensor Temperature Lo LoWarn HiWarn Hi Status
Similar to the show-devs command run at the ok prompt, the prtconf command
displays the devices that are configured for the Sun Blade 1500 workstation.
The prtconf command identifies hardware that is recognized by the Solaris
operating system. If hardware is not suspected bad, yet software applications are
having trouble with the hardware, the
software recognizes the hardware, and if a driver for the hardware is loaded.
3-20 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
prtconf command can indicate if the Solaris
3.3.3.1Options
TABLE 3-8 describes options for the prtconf command and how those options can
help troubleshoot the Sun Blade 1500 workstation.
TABLE 3-8 Options for prtconf
OptionDescriptionHow It Can Help
No optionDisplays the device tree of
devices recognized by the
operating system.
-D
-p
-V
Similar to the output of no
option, however the device
driver is listed.
Similar to the output of no
option, yet is abbreviated.
Displays the version and date
of the OpenBoot PROM
firmware.
If a hardware device is recognized, then it is probably
functioning properly. If the message “
attached)
device, then the driver for the device is corrupt or missing.
Informs you of the driver needed or used by the operating
system to enable the device.
Does not report a “(driver not attached)”
message, only a quick view of the devices.
Provides a quick check of firmware version.
” is displayed for the device or for a sub-
(driver not
Chapter 3 Basic Troubleshooting 3-21
3.3.3.2Examples
The following examples show output for the prtconf command and its options.
# prtconf
System Configuration: Sun Microsystems sun4u
Memory size: 1024 Megabytes
System Peripherals (Software Nodes):
SUNW,Sun-Blade-1500
packages (driver not attached)
SUNW,builtin-drivers (driver not attached)
deblocker (driver not attached)
disk-label (driver not attached)
terminal-emulator (driver not attached)
dropins (driver not attached)
kbd-translator (driver not attached)
obp-tftp (driver not attached)
SUNW,i2c-ram-device (driver not attached)
SUNW,fru-device (driver not attached)
SUNW,asr (driver not attached)
ufs-file-system (driver not attached)
chosen (driver not attached)
openprom (driver not attached)
client-services (driver not attached)
options, instance #0
aliases (driver not attached)
. . .
3-22 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
224.0.0.0 matlock U 1 0 bge0
default fermpk28a-46 UG 1 22
localhost localhost UH 25 3018 lo0
3.3.5ping Command
The ping command sends ICMP ECHO_REQUEST packets to network hosts.
Depending upon how the
identify troublesome network links or nodes. The destination host is specified in the
variable hostname.
ping command is configured, the output displayed can
Chapter 3 Basic Troubleshooting 3-25
3.3.5.1Options
TABLE 3-10 describes options for the ping command and how those options can help
troubleshoot the Sun Blade 1500 workstation.
TABLE 3-10 Options for ping
OptionDescriptionHow It Can Help
hostnameThe probe packet is sent to
hostname and returned.
-g hostnameForces the probe packet to
route through a specified
gateway.
-i interfaceDesignates which interface to
send and receive the probe
packet through.
-n
-s
-svR
Replaces host names with IP
addresses.
Ping continuously in one
second intervals. Ctrl-C aborts.
Upon abort, statistic are
displayed.
Displays the route the probe
packet followed in one second
intervals.
3.3.5.2Examples
The following examples show output for the ping command and its options.
# ping -s teddybear
PING teddybear: 56 data bytes
64 bytes from teddybear (192.146.77.140): icmp_seq=0. time=1.
ms
64 bytes from teddybear (192.146.77.140): icmp_seq=1. time=0.
ms
64 bytes from teddybear (192.146.77.140): icmp_seq=2. time=0.
ms
^C
The ps command lists the status of system processes. Using options and rearranging
the command output can assist in determining the Sun Blade 1500 workstation
resource allocation.
3.3.6.1Options
TABLE 3-11 describes options for the ps command and how those options can help
troubleshoot the Sun Blade 1500 workstation.
TABLE 3-11 Options for ps
OptionDescriptionHow It Can Help
-e
-f
Displays information for every
process.
Generates a full listing.Provides the following process information: user ID, parent
-o optionAllows configurable output.
pid, pcpu, pmem, and
The
comm options display process
ID, percent CPU consumption,
percent memory consumption,
and the responsible executable,
respectively.
Identifies the process ID and the executable.
process ID, system time when executed, and the path to
the executable.
Provides only most important information. Knowing the
percentage of resource consumption helps identify
processes that are affecting system performance and might
be hung.
Chapter 3 Basic Troubleshooting 3-27
3.3.6.2Examples
The following examples show output for the ps command and its options.
Note – When using sort with the -r option, the column headings are printed at the point
where the value in the first column is equal to zero.
3-28 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
3.3.7prstat Command
The prstat utility iteratively examines all active processes on the system and
reports statistics based on the selected output mode and sort order. The
command provides output similar to the
3.3.7.1Options
TABLE 3-12 describes options for the prstat command and how those options can
help troubleshoot the Sun Blade 1500 workstation.
TABLE 3-12 Options for prstat
OptionDescriptionHow It Can Help
No optionDisplays a sorted list of the top
processes which are consuming
the most CPU resources. List is
limited to the height of the
terminal window and the total
number of processes. Output is
automatically updated every
five seconds. Ctrl-C aborts.
-nnumberLimits output to number of
lines.
-skeyPermits sorting list by key
parameter.
-v
Verbose mode.Displays additional parameters.
Output identifies process ID, user ID, memory used, state,
CPU consumption, and command name. By default, list is
sorted by CPU consumption.
Limits amount of data displayed and identifies primary
resource consumers.
Useful keys are cpu (default), time, and size.
prstat
ps command.
Chapter 3 Basic Troubleshooting 3-29
3.3.7.2Examples
The following examples show output for the prstat command and its options.
3-30 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
CHAPTER
4
Troubleshooting Flowcharts
This chapter contains flowcharts to help you troubleshoot problems with your Sun
Blade 1500 workstation. The flowcharts are ordered parallel to the power-on
sequence. Flowchart topics covered are:
■ “Power-On Flowchart” on page 4-2
■ “Start Up Problems” on page 4-5
■ “Power Problem” on page 4-6
■ “Hard Drive Problem” on page 4-8
■ “System Fan Problem” on page 4-9
■ “USB Problem” on page 4-10
■ “Audio Output Problem” on page 4-12
■ “Monitor Problem” on page 4-14
■ “Network Problem” on page 4-17
■ “Keyboard Problem” on page 4-19
■ “Login Problem” on page 4-20
■ “Graphical User Interface Problem” on page 4-22
■ “Data Access and Running Applications Problems” on page 4-23
■ “Storage Problems” on page 4-24
■ “Optical Drive Problem” on page 4-25
■ “PCI Card Problem” on page 4-28
■ “IEEE 1394 Problem” on page 4-30
■ “Smart Card Reader Problem” on page 4-32
■ “Advanced Problems” on page 4-33
■ “Motherboard Problem” on page 4-34
■ “Memory Problem” on page 4-37
■ “NVRAM Problem” on page 4-39
■ “Battery Problem” on page 4-40
4-1
4.1Power-On Flowchart
The “Power-On Flowchart” on page 4-3 indicates points where proper startup can be
recognized. This flowchart helps identify what aspect of the Sun Blade 1500
workstation is at fault.
If you suspect a system failure, power on the system and follow the flowchart.
If you answer “No” to a question, direct your attention to the section provided or to
other flowchart cross-references.
If you complete the flowchart without answering “No” to any questions yet you still
suspect a failure with the Sun Blade 1500 workstation, see
Advanced Troubleshooting” on page 5-1 for more in-depth procedures.
“Introduction to
4-2 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Press and release the
Power button.
Does the power supply
fan spin up?
Y
Does the hard
drive spin up?
Y
Does at least one of the
system fans spin up?
Y
N
N
N
Problem with fan. See
“System Fan Problem” on
page 4-9.
In normal operation, the system power-on sequence follows the path of Y for every question. Power on your system and follow this flowchart. Should your system resolve
to a N answer to a question, go to the cross-reference. If
several cross-references are listed, the first is the most
likely solution. Try the other cross-references if the first
does not resolve the problem.
Problem with power. See
“Power Problem” on
page 4-6.
Problem with hard drive.
See “Hard Drive Problem”
on page 4-8.
Does the speaker
beep only once?
Y
Is anything displayed
on the monitor?
Y
Can you log in
as your user?
Y
Go to
Next Page
FIGURE 4-1 Power-On Flowchart
N
N
N
Problem with monitor.
See “Monitor Problem”
on page 4-14.
Problem with log in. See
“Login Problem” on
page 4-20.
Problem with network.
See “Network Problem”
on page 4-17.
OR
OR
Problem with monitor.
See “Monitor Problem”
on page 4-14.
OR
Problem with graphics
accelerator. See “PCI Card
Problem” on page 4-28.
Problem with speaker.
See “Audio Output Prob-
lem” on page 4-12.
OR
Problem with memory or
motherboard. See “Audio
Responses” on page 3-12.
Chapter 4 Troubleshooting Flowcharts 4-3
Next Page
Can you interact
with the GUI?
Y
Can you access data
and run applications?
Y
Can you use: the optical
drive, smart card reader,
PCI cards, USB, audio
ports?
Y
N
N
N
Problem with optical
drive. See “Optical Drive
Problem” on page 4-25.
Problem with smart card
reader. See “Smart Card
Reader Problem” on
page 4-32.
Problem with PCI card.
See “PCI Card Problem”
on page 4-28.
Problem with USB. See
“USB Problem” on
page 4-10.
OR
OR
OR
Problem with remote network or servers. See
“Data Access and Running Applications Problems” on page 4-23.
Problem with resources.
See “Graphical User Inter-
face Problem” on
page 4-22.
OR
Problem with network.
See “Network Problem”
on page 4-17.
OR
Problem with audio. See
“Audio Output Problem”
on page 4-12.
OR
Problem with memory.
See “Memory Problem”
on page 4-37.
OR
System is normal. If you
suspect a problem, run
SunVTS. See “SunVTS” on
page 9-1.
FIGURE 4-2 Power-On Flowchart (Continued)
Problem with CPU or
motherboard. See “Moth-
erboard Problem” on
page 4-34.
4-4 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
4.2Start Up Problems
The following flowcharts help troubleshoot problems that occur during system
startup.
■ “Power Problem” on page 4-6
■ “Hard Drive Problem” on page 4-8
■ “System Fan Problem” on page 4-9
■ “USB Problem” on page 4-10
■ “Audio Output Problem” on page 4-12
■ “Monitor Problem” on page 4-14
■ “Network Problem” on page 4-17
■ “Keyboard Problem” on page 4-19
■ “Login Problem” on page 4-20
■ “Graphical User Interface Problem” on page 4-22
■ “Data Access and Running Applications Problems” on page 4-23
Chapter 4 Troubleshooting Flowcharts 4-5
4.2.1Power Problem
There is a power problem.
Is the motherboard
LED0 on?
Y
N
Attach known good electric device or tester to
wall receptacle.
In normal operation, the motherboard LED0 glows as
standby power is supplied to the workstation. You can
view the glow from LED0 by looking into the system chassis through the rear system fan, or the mounting holes for
the fan. If room lighting is bright, the glow might not be
seen.
Upon powering on the workstation, the system fans immediately spin to full speed. In a moment, they slow down to
the required speed.
Further into the boot process, the light in the Power button flashes, then stays lit.
If there is a serious problem with the system memory, the
workstation beeps three times and power off.
Checking a component means checking the electrical connections and fit.
Power on system.
Is the specified power
supplied?
Y
Replace power cables.
Is the motherboard
LED0 on?
Y
N
N
Replace power supply.
See “Replacing the Power
Supply” on page 13-2.
Is the motherboard
Check power requirements. See “Electrical
Specifications” on
page A-2.
Resolve facility power
supply issues.
N
LED0 on?
Y
Check motherboard and
replace if necessary. See
“Motherboard Problem”
on page 4-34.
Go to
A
FIGURE 4-3 Power Problem
4-6 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
A
Does the power supply
fan spin?
Y
Do any system
fans spin?
Y
Wait a moment.
Does
the system beep and
immediately power off?
Y
Check motherboard and
replace if necessary. See
“Motherboard Problem”
on page 4-34.
N
Did you replace the
power switch?
Did you replace the
power supply?
Check motherboard and
replace if necessary. See
“Motherboard Problem”
on page 4-34.
N
N
the light in the power
button flash or stay lit?
Return to “Power-On
Flowchart” on page 4-3.
Y
Y
Does
Y
N
N
Replace power supply.
See “Replacing the Power
Supply” on page 13-2.
Does the hard
drive spin up?
System fan problem. See
“System Fan Problem” on
page 4-9.
N
Check power switch and
replace if necessary. See
“Replacing the Power
Switch Assembly” on
page 14-17.
Check power switch and
replace if necessary. See
“Replacing the Power
Switch Assembly” on
page 14-17.
N
Y
Check motherboard and
replace if necessary. See
“Motherboard Problem”
on page 4-34.
FIGURE 4-4 Power Problem (Continued)
Chapter 4 Troubleshooting Flowcharts 4-7
4.2.2Hard Drive Problem
There is a problem with
the hard drive.
Is a message about the
hard drive displayed?
Y
Refer to the message
tables. See “Displayed
Messages” on page 3-5.
Is the
operating system
running?
Y
N
Does the hard
drive sound like that of a
known good system?
N
In normal operation, the hard drive spins up shortly after
powering on the workstation. The drive might stop spinning later as part of the power management configuration. Clicking the mouse can bring the hard drive out of
sleep state.
Checking a component means checking the electrical connections and fit.
N
Y
Refer to audio responses
table. See “Audio
Responses” on page 3-12.
1. Save data.
2. Close all applications.
As superuser, run fsck:
# /usr/bin/fsck
Answer the questions.
Is the problem
still there?
Y
Check the hard drive with
SunVTS. See “SunVTS” on
page 9-1.
Did the hard drive
pass the test?
Y
Data on the hard drive is
corrupt. Contact the system administrator.
Is the ok prompt
displayed?
N
Return to “Power-On
Flowchart” on page 4-3.
N
Replace the hard drive.
See “Replacing a Hard
Drive” on page 12-2.
N
Y
Press the Stop-A keys.
Type:
probe-ide
Is the manufacturer
and model of the suspect
N
hard drive displayed?
Y
Type boot to start the
operating system.
Check the hard drive with
OpenBoot Diagnostics.
See “OpenBoot Diagnos-
tics” on page 8-5.
Check the hard drive with
SunVTS. See “SunVTS” on
page 9-1.
FIGURE 4-5 Hard Drive Problem
4-8 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
4.2.3System Fan Problem
There is a problem with
the system fans.
In normal operation, the system fan’s speed is set according to the temperature inside of the workstation. If it is
cold, the fans might not turn on at all and instead make a
quiet grumbling sound.
When fan bearings fail, they have a distinct noisy sound
and the fan should be replaced. Do not mistake this for the
full fan speed sound at power on.
If might be difficult to hear the CPU fan spinning.
Checking a component means checking the electrical connections and fit.
Is the room
temperature greater than
15 °C (60 °F)?
Y
Is the rear fan
spinning?
Y
Is the
rear fan exceptionally
noisy?
Y
Replace the rear fan. See
“Replacing the Rear Fan”
on page 13-15.
N
N
N
Is the front fan
spinning?
Y
front fan exceptionally
noisy?
Y
Replace the front fan. See
“Replacing the Front Fan”
on page 13-8.
Is the
Check the rear fan and
replace if necessary. See
“Replacing the Rear Fan”
on page 13-15.
N
N
Is the CPU fan
spinning?
Y
CPU fan exceptionally
noisy?
Y
Replace the CPU fan and
heat sink. See “Replac-
ing the CPU Fan and Heat
Sink Assembly” on
page 11-13.
Is the
The system fans are thermally controlled and only
turn on when cooling is
needed.
Check the front fan and
replace if necessary. See
“Replacing the Front Fan”
on page 13-8.
N
Check CPU fan and
replace if necessary. See
“Replacing the CPU Fan
and Heat Sink Assembly”
on page 11-13.
N
Return to “Power-On
Flowchart” on page 4-3.
FIGURE 4-6 System Fan Problem
Chapter 4 Troubleshooting Flowcharts 4-9
4.2.4USB Problem
There is a problem with
a USB device (not keyboard or mouse), interacting with the system.
Is the
suspect device a Sun
supported device?
Y
Disconnect all USB
devices and attach the
suspect device directly to
the system.
N
This flowchart can only
be used for Sun supported devices.
In normal operation, the USB ports allow for hot-plugging
of peripherals. If the peripheral is not recognized, try plugging it in to another connector. Do not force the connection.
If the peripheral is USB 2.0-compliant, and it is not
attached to the USB 2.0 ports on the combination card, or
to a USB 2.0 hub attached to the USB 2.0 ports, then it will
have poor performance.
The keyboard and mouse do not function in the USB 2.0
ports on the combination card.
Checking a component means checking the electrical connections and fit.
Is the problem
still there?
Y
Is the suspect
device connected to the
combination card?
Y
Reconnect the suspect
device to another combination card port.
Is the problem
still there?
Y
Go to
B
FIGURE 4-7 USB Problem
N
N
Problem is with cabling,
hubs, or other USB
device.
Is the
suspect device a USB
N
1.0 or USB 1.1 device?
Y
The combination card
provides best perfor-
Go to
B
N
mance for USB 2.0
devices. Plug the USB 2.0
device into the combination card.
Is the problem
N
still there?
Y
Return to “Power-On
Flowchart” on page 4-3.
Go to
Return to “Power-On
Flowchart” on page 4-3.
B
4-10 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
B
Obtain the ok prompt.
See “Obtaining the ok
Prompt for Testing” on
page 5-2.
Type:
ok show-devs
Do you see this text?
usb@b
usb@a
Y
Do you see this text?
usb@8,2
usb@8,1
usb@8
Y
Start the operating system. Type:
ok boot -r
Determine if the USB
ports are recognized.
Type:
% prtconf
Do you see this output
five times?
usb, instance
Y
Do you see this output?
usb, instance
unit,(driver not
Y
Problem with device
driver. Contact system
administrator.
FIGURE 4-8 USB Problem (Continued)
N
N
N
N
Do you see this output?
usb, instance
device, instance
Problem with device
application or device
itself.
Problem with I/O subsystem chip. Replace
motherboard. See
“Replacing the Motherboard” on page 11-43.
Did you move
the combination card to
N
another PCI slot?
Y
Replace the combination
card. See “Replacing the
PCI Cards” on page 11-28.
Move the combination
card to another PCI slot.
See “Replacing the PCI
Cards” on page 11-28.
Go to
B
Problem with Solaris
driver. Contact system
administrator.
N
Y
Problem with device connection to system. If problem is at
front panel USB ports, check
with keyboard. See “Keyboard
Problem” on page 4-19.
Chapter 4 Troubleshooting Flowcharts 4-11
4.2.5Audio Output Problem
There is a problem with
the audio output.
Obtain the ok prompt.
See “Obtaining the ok
Prompt for Testing” on
page 5-2.
Check the audio with
OpenBoot Diagnostics.
See “OpenBoot Diagnos-
tics” on page 8-5.
In normal operation, system sounds are played through
the chassis speaker and headphone jack.
Some audio drivers might prevent an audio application
from making sound. Consult the system administrator in
this situation.
Loopback connectors can provide more thorough testing
with OpenBoot Diagnostics or SunVTS.
Checking a component means checking the electrical connections and fit.
Was an error
displayed?
Y
Check motherboard and
replace if necessary. See
“Motherboard Problem”
on page 4-34.
N
Change the test-args
parameter to loop-back. See “Configuring
OpenBoot Diagnostics”
on page 8-7.
Check the audio output
with OpenBoot Diagnostics again.
Do you hear a beep from
the system speaker?
Attach headphones to
the headphone jack on
the front panel and run
the audio test again.
Do you hear a beep in
the headphones?
Y
Attach the headphones
to the audio out jack on
the rear panel and run
the audio test again.
N
Y
Check the speaker and
replace if necessary. See
“Replacing the Speaker”
on page 13-39.
N
Check the audio/USB
board and replace if necessary. See “Replacing
the Audio USB Board” on
page 13-30.
Go to
C
FIGURE 4-9 Audio Output Problem
4-12 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
C
Do you hear a beep in
N
the headphones?
Y
Start the operating system. Type:
ok boot -r
Check motherboard and
replace if necessary. See
“Motherboard Problem”
on page 4-34.
Check the audio with
SunVTS. See “SunVTS” on
page 9-1.
Did the audio
N
test pass?
Y
Problem with audio software application. Contact
system administrator.
FIGURE 4-10 Audio Output Problem (Continued)
Problem with Solaris
audio drivers. Contact
system administrator.
Chapter 4 Troubleshooting Flowcharts 4-13
4.2.6Monitor Problem
There is a problem with
the monitor.
In normal operation, an LED on the monitor is green.
In sleep mode the LED is either flashing or amber colored.
The monitor wakes from sleep mode by tapping the spacebar or moving the mouse.
Checking a component means checking the electrical connections and fit.
Is this a Sun
monitor?
Y
Is the monitor screen
black?
Y
Is a KVM in use?
Y
Attach monitor, keyboard, and mouse
directly to workstation.
Set the brightness and
contrast controls to their
center positions.
Tap spacebar and move
mouse.
N
N
N
Check monitor, keyboard, and mouse connections.
Refer to monitor’s documentation.
Refer to displayed screens
table. See “Displayed
Screens” on page 3-2.
Is the problem
N
still there?
Y
Go to
Return to “Power-On
Flowchart” on page 4-3.
D
FIGURE 4-11 Monitor Problem
4-14 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
D
Does an LED indicate
power to the monitor?
Y
N
Is the monitor
turned on?
Is the monitor
connected to same power
source as computer?
Replace monitor power
cable.
N
Y
N
Y
Attach known good electric device or tester to
Turn monitor on.
Return to “Power-On
Flowchart” on page 4-3.
wall receptacle.
Is the specified power
N
supplied?
Y
Check power requirements. See “Electrical
Specifications” on
page A-2.
Resolve facility power
supply issues.
Go to
E
Does an LED indicate
N
power to the monitor?
Y
Flowchart” on page 4-3.
FIGURE 4-12 Monitor Problem (Continued)
Replace monitor.Return to “Power-On
Chapter 4 Troubleshooting Flowcharts 4-15
E
connector on the monitor
Is the
signal cable good?
Y
Is the connector
on the graphics
accelerator good?
Y
Does the monitor have
a multi-input switch?
Y
Set the switch to different positions.
Did this solve
the problem?
Y
Return to “Power-On
Flowchart” on page 4-3.
FIGURE 4-13 Monitor Problem (Continued)
N
N
N
N
Check the graphics accelerator. See “PCI Card
Problem” on page 4-28.
Replace monitor signal
cable.
Replace the graphics
accelerator. See “Replac-
ing the PCI Cards” on
page 11-28.
4-16 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.