Sun Blade 6048 System
 
Sun Blade X6220 Server Module
 
Sun Blade X6250 Server Module
 
Sun Blade X6450 Server Module
 

PLA-Support>Sun Systems>x64>Blades>SN-x64: BLADE
 
.Old GCS Categories>Sun Microsystems>Servers>x64 Servers
 

Applies to:

Purpose

Description
This document addresses issues you may run in to during the boot process on Sun Fire Blade X6220, X6250, X6450 servers
Symptoms::

• system will not boot
• boot fails
• can't power up

Purpose/Scope:

This document addresses issues you may run in to during the boot process on Sun Fire Blade X6220, X6250, X6450 servers, from power on the system until the operating system starts to boot.

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.

Step 1. Verify system has power

This can be done either locally to the chassis, or remotely via ILOM commands. To do so remotely, you will need to connect to the CMM

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 via serial or network.

If you have problems connecting to the CMM, you can follow the instructions in the troubleshooting document:

Document: 1019381.1 Analyzing "can't log in" problems on a Sun Blade 6000 or Sun Blade 6048

Step 2. Verify there are no fault or warning LEDs

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

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

Step 3. Verify boot media exists and is bootable

Refer to Document: 1019727.1 How to verify your boot media exists and is bootable on Sun Fire[TM] X6220/X6250 and X6450 systems

Step 4. Confirm that the OS starts to boot

For Solaris refer to:

System Administration Guide: basic Administration (817-1985)

Chapter 15 x86: GRUB Based Booting (Reference)
Chapter 16 x86: Booting a System That Does Not Implement GRUB

If you are able to see the boot loader of your system, e.g. GRand Unified Bootloaded (GRUB) for Sun Solaris or Linux, LiLO for Linux or the MS Windows boot loader, than you have confirmed that the OS is starting to boot.

When starting the GRUB on a system running Linux or Solaris[TM], and you do not see the GRUB menu for selecting the image to boot, you may have an issue with a corrupted boot archive. In this case, please refer to:

Document: 1018947.1 Boot problem because of corrupted boot_archive file

You may also find the following useful:

Document: 1005352.1 Configuring and understanding GRUB

Step 5. Raise a Service Request

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further in-depth troubleshooting is required. Please provide supporting data and open a Service Request.

See Document: 1019322.1 How to gather Information from Sun Blade[TM] 6000/6048 systems.

References

Sun Blade 6000 Documentation
Sun Blade X6250 Server Module documentation
Sun Blade X6220 Server Module documentation
Sun Blade X6450 Server Module documentation
Sun Blade 6000 Disk Module documentation

For possible issues in booting or BIOS refer to the Sun Blade 6000 Modular System Product Notes


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, can't, boot, blade, 6000, 6048, X6220, X6250, X6450

References

This solution has no attachment