Analyzing "Can't boot/boot fails" on Sun Fire[TM] T6300, T6320 Blade Servers

Asset ID:	1-75-1019653.1
Update Date:	2010-08-27
Keywords:

Solution Type Troubleshooting Sure

Solution 1019653.1 : Analyzing "Can't boot/boot fails" on Sun Fire[TM] T6300, T6320 Blade Servers

Applies to:

Sun Blade 6048 System
Sun Blade T6300 Server Module
Sun Blade T6320 Server Module
All Platforms

Purpose

This document describes which troubleshooting steps to take when trying to resolve problems related to booting Sun Blade T6300 and T6320 servers, from power on the system until the operating system starts to boot.

Last Review Date

August 27, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Description
Document description

Symptoms:

system will not boot
boot fails
can't power up

Purpose/Scope:

This document describes which troubleshooting steps to take when trying to resolve problems related to booting Sun Blade T6300 and T6320 servers, from power on the system until the operating system starts to boot.

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.

Step 1. Verify the power is good

This can be done either locally to the chassis, or remotely via ILOM commands.

See Document 1019382.1 : How to verify power on a Sun Blade[tm] 6000 and Sun Blade[tm] 6048 Modular System

To do so remotely, you will need to connect to the CMM which is covered in document 1019314.1 : How to connect to the CMM ILOM using a Serial Connection on a Sun Blade 6000/6048

Step 2. Verify there are no fault or warning LEDs

Again, this can be done either locally to the chassis, or remotely.

Refer to Document 1019321.1 : How to check Fault/warning LEDs on Blade 6000/6048 Systems

Step 3. Verify That POST diagnostics pass.

This is simple enough, simply check the console for error messages. If there were none, the banner should be displayed.

Step 4. Verify that the boot device can be seen.

Refer to Document 1019747.1 : How to verify boot devices can be seen for Sun Fire[TM] T6300/T6320 Blade Servers

Step 5. Verify that there are no boot media problems.

Check to be sure that the user is booting from supported Solaris Media.

Details of the minimum supported Solaris versions and patch levels may be found in the Sun System Handbook at:

Sun Blade T6300

Sun Blade T6320

If booting over the network be sure that the add_install_client was done for a sun4v system.

Refer to Document 1018938.1 : Jumpstart of UltraSPARC T1 based system panics with "BAD TRAP: type=10"

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 console logs, any errors that are seen, and showlogs -v from the system controller. For additional support contact My Oracle Support.

Product
Sun Blade 6000 Modular System
Sun Blade 6048 Modular System
Sun Blade T6300 Server Module
Sun Blade T6320 Server Module

Internal Comments
This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap
contained in this document, and/or prior to updating this document, please
contact the domain engineers that are managing this document via the “Document
Feedback” alias(es) listed below:

Domain Lead: [email protected]
Feedback Alias: [email protected]

normalized, blade, 6000, 6048, T6300, T6320, can't boot, boot fails

Attachments

This solution has no attachment