Sun Fire V20z Compute Grid Rack System
 
Sun Fire V20z Server
 
Sun Fire V40z Server
 

GCS>Sun Microsystems>Servers>x64 Servers
 

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

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

Power can be verified either visually (if you have access to the platform) or remotely using using Service Processor (SP) commands.

Refer to <Document: 1008399.1> : How to verify power on a Sun Fire[TM] v20z/40z System

The above technical instruction makes reference to the v20z/v40z Troubleshooting guide, which will assist in troubleshooting in the event that the server powered down unexpectedly. For example, in the event of a Thermal Trip Event, advice is given on correcting airflow blockages.

If you still have a problem, raise a service request as outlined in Step 6

Step 2. Check for any errors on the system

• Check for platform events

Identify any reported system faults on the Service Processor with command:

sp get events -v

Or one of the other methods described in the Troubleshooting: System Events section of the Sun Fire V20z and Sun Fire V40z Servers Troubleshooting Techniques and Diagnostics Guide, Part No 817-7184

Available at http://download.oracle.com/docs/cd/E19121-01/index.html

• Visually check of system LEDs

System LEDs and the LCD panel can indicate certain fault conditions.

Refer to "Lights, LCD, LED" section of the Sun Fire V20z and Sun Fire V40z Servers Troubleshooting Techniques and Diagnostics Guide, Part No 817-7184

Any abnormal conditions, raise a a service request as outlined in Step 6.

• Checking POST codes

In the event of hardware or configuration errors, the BIOS displays any error messages on the display. In some cases the error may be so severe that there is no video output, in which case you can retrieve any errors from the SP. Run the command:

$ sp get port80

Refer to <Document: 1006320.1> : Cheatsheet for V20z and V40z Post Codes

and also to the "BIOS POST Codes" section of the Sun Fire V20z and Sun Fire V40z Servers Troubleshooting Techniques and Diagnostics Guide, Part No 817-7184

Step 3. Verify boot media exists and is bootable

Refer to <Document: 1010038.1> : How to verify your boot media exists and is bootable on a Sun Fire[TM] V20z/40z Server

Step 4. Confirm that the OS starts to boot

If you are able to see the boot loader of your system, e.g. 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 GRand Unified Bootloaded (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 <Document: 1005352.1> Configuring and understanding GRUB

  useful

Step 5. Raise a Sun 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 troubleshooting is required. For additional support contact Sun Support.

NOTE: Since you can't boot your server, the amount of data you can gather is limited. For example, if you are running solaris, you will not be able to complete an explorer data capture.

However, please capture the following from the SP:

$ inventory get hardware -v
$ inventory get software
$ sp get events -v

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. For additional support contact Sun Support.

This solution has no attachment