Sun Java Workstation W2100z
 
Sun Fire V20z Server
 
Sun Fire V40z Server
 
Sun Java Workstation W1100z
 

PLA-Support>Sun Systems>x64>Server>SN-x64: MISC-SERVER
 

Applies to:

Purpose

Summary:

This document identifies failures of internal disks in Oracle Solaris x64 platforms that are not configured as part of a RAID array. Failures under hardware RAID and volume management are not discussed in this document however disks under Veritas or SVM control are referenced.

Troubleshooting Steps

Symptoms:

• Disk service LED illuminated
• Disk errors in system messages files
• Disk errors on console
• Disk SMART errors during the boot process

Steps to Follow

Step 1. Verify a supported platform disk and part number:

The following link references a support document that assists in the identification of a disk part number. In addition, the document provides the public web location of the Oracle systems handbook to confirm the disk in question is a supported disk for your platform:

<Document:1010055.1> Identifying Oracle Supported Platform Disks

Disks that are not listed on a platforms documentation and deemed unsupported. This is because they have not been tested and therefore have unknown properties and as such may produce unknown errors.
Even if an unsupported disk appears to work correctly, it is recommended to always use supported disks for contracted platforms.

Step 2. Verify disk is not a member of a RAID array:

The following link references a support document that assists in identifying if your Solaris operating environment is installed as part of a RAID array or not:

<Document:1017961.1> How to Identify if a Solaris[TM] Operating Environment is Installed on a Hardware RAID Controller

Troubleshooting steps differ for platforms that are installed under the control or a RAID management device. This is because disks under RAID control are hidden from the operating environment and are referenced as a pseudo or meta-device.

Step 3. Verify disk is online/offline status and errors:

The following link references a support document that assists in identifying the online/offline status of directly attached platform disks. This document also discusses the location of Solaris error logs and the format in which disk errors should appear:

<Document:1005530.1> How to Check for Solaris[TM] x64 Disk Errors and Online/Offline Status

Disks that are not directly attached to the platform for example installed in an external storage array, are not discussed in this document.
Storage array disks may have different properties when connected to and behind an external controller and as such change the error syntax and tools used for collection and configuration.

Step 4. Verify disk firmware revision and known applicable issues:

The following link references a support document that assists in identifying the disk model number and firmware revision to check for known issues and if applicable patch updates:

<Document:1008396.1> How to Identify Optical and Hard Disk Firmware Revisions for Checking of Known Issues

Patches and firmware updates are often available for disks under multiple operating systems.
Checking for known issues and updates results in decreased downtime.

Step 5. Solaris or Veritas Volume Manager disk identification and replacement:

The following link references a support document that assists in identifying and replacing failed disks under control of the Solaris or Veritas Volume Manager applications:

<Document:1010946.1> General Procedures for Replacing a SCSI or FC-AL Disk

Disk replacement under Solaris or Veritas Volume Manager requires additional steps to remove the disk from volume manager control before physical replacement. Steps to introduce the replacement disk are also necessary when under the control of a volume manager.

Step 6. Run a Solaris explorer and raise a Oracle service request:

The following link references a support document that assists in the gathering of information from your platform using the Oracle Explorer package.

The Explorer script gathers operating system parameters and configuration information. This package is designed to collect data on how Solaris is configured and not data from the corporate environment, Solaris is operating within.

A full description of the Oracle Explorer package and release notes are available on the following URL:

<Document:1312847.1> Oracle Explorer Data Collector

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 Oracle Support.

References

This solution has no attachment