|Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
Solution Type Troubleshooting Sure
Solution 1010039.1 : Analyzing Internal RAID/non-RAID Disk Failures for x64 Sun Blade [TM] 6000/8000 server platforms
This document addresses failures of internal disks in Solaris[TM] x64, Red Hat , SuSE/Novell and Windows platforms. Failures under hardware RAID and JBOD (non-RAID) are discussed in this document.
- Disk service LED illuminated
- Disk errors in system messages files
- Disk errors on console
- Disk SMART errors during the boot process
Steps to Follow
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 Sun systems handbook to confirm the disk in question is a supported disk for your platform:
<Document: 1010055.1> Identifying Sun 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.
Step 2. Verify disk is or is not a member of a RAID array
The following links reference support documents that assist in identifying if your Solaris, Linux or Windows operating environments are installed as part of a RAID array or not. The Windows instructions are in line:
Solaris: <Document: 1017961.1> How to Identify if a Solaris[TM] Operating Environment is Installed on a Hardware RAID
Linux: <Document: 1013003.1> How to Identify if a Linux Operating Environment is Installed on a Hardware RAID Controller
Right Click on My Computer and select Properties. Select the Hardware tab from the window that appears. Click on Device Manager. Click on Disk Drives. Installed disk(s) are listed.
If the disk drive(s) listed display the name Adaptec, LSI,
NVIDIA or StorageTek then your platforms disks are
under the control of a RAID device.
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 has has not been going offline and no physical disk hardware problem
The following links reference support documents that assists in identifying the online/offline status of directly attached platform disks. This document also discusses the location of your operating system error logs and the format in which disk errors should appear:
Solaris: <Document: 1005530.1> How to Check for Solaris[TM] x64 Disk Errors and Online/Offline Status
Linux: <Document: 1002936.1> How to Check for Linux Platform Disk Errors and Online/Offline Status
Windows: <Document: 1011590.1> How to check for Windows platform 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.
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. Run information gathering programs and raise a Sun service request
The following links reference support documents that assist in the gathering of information from your Solaris, Red Hat, Novell/SuSE and Windows platforms using their own information gathering tools.
Solaris: <Document: 1018748.1> How to Run Sun[TM] Explorer and Forward the Data to a Sun Engineer
Novell/SuSE Enterprise Linux: <Document: 1010057.1> How to gather information on SuSE Linux Enterprise Systems
Red Hat Enterprise Linux: <Document: 1010058.1> How to Gather Information on Red Hat Enterprise Linux Systems
Click on Start and select Run. Type "msinfo32" in the text box that appears. Select the File menu and then select Export. Provide a file name and send this file to Sun.
This is necessary if the resolution steps above did not resolve your issue and Sun needs to be engaged to continue diagnosis for you. Information gathering programs gather operating system parameters and configuration information from your platform.
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.
Sun Blade x8400 Server Module
Sun Blade X8450 Server Module
Sun Blade X8440 Server Module (Quad Core)
Sun Blade X8440 Server Module
Sun Blade X8420 Server Module
Sun Blade X6450 Server Module
Sun Blade X6420 Server Module
Sun Blade X6250 Server Module
Sun Blade X6220 Server Module
Sun Blade 8000 P Modular System
Sun Blade 8000 Modular System
Sun Blade 6000 Modular System
At this point, if the customer has validated that each troubleshooting step above is true for their environment, and the issue still exists, escalate to your Sun escalation path.
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:
Normalization team alias:
x64, normalized, RAID, JBOD, error, disk, MSM, Windows, Solaris, Linux, Red, Hat, SuSE, Novell
Previously Published As
User Name: 31620
Comment: Published using interim normalization rules supplied by the Normalization Program Team: (circa mid-December 2007)
o Content visibility is appropriate
o External links are in the proper format - all tested ok
o No internal-only links
o Normalized keyword present
o No in-line images
o Consistent use of language and grammar
o Solution type consistent with WTS at:
o Product metadata seems appropriate
o Summary and Symptoms sections present
o Resolution Path, Steps to follow seem logical and numbered
o Added Brian Jackson as the Domain Lead and feedback path
o Links only tested to one level down and are in the correct
o Added correct trademarking
User Name: 79977
Comment: Checks out okay
I added "Step x..." to each troubleshooting step as per the normalization content standard rules
Please pass to publish
This solution has no attachment