Troubleshooting StorEdge [TM] 3120/33x0/351x JBOD Failures

Asset ID:	1-75-1002790.1
Update Date:	2011-05-13
Keywords:

Solution Type Troubleshooting Sure

Solution 1002790.1 : Troubleshooting StorEdge [TM] 3120/33x0/351x JBOD Failures

Applies to:

Sun Storage 3120 SCSI Array
Sun Storage 3310 Array
Sun Storage 3320 SCSI Array
Sun Storage 3510 FC Array
Sun Storage 3511 SATA Array
All Platforms

Purpose

The purpose of this document is to assist in troubleshooting StorEdge [TM] 3120/33x0/351x JBOD Failures.

Symptoms:

'show config' shows a failed IOM
'show disks' shows missing or failed disks
Amber LED indicating failure
Chassis sounds an audible alarm
Disks are not visible to the Operating System
Out of range or incorrect Disk ID numbers
SES and/or firmware levels are different in the enclosure (mismatch)
LUN errors

Last Review Date

May 13, 2011

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

NOTE: This is a sub-set of Document 1011431.1: "Troubleshooting Sun StorEdge [TM] 33x0/351x Hardware".

The steps below will help verify and resolve problems isolated to a JBOD.

Before you begin troubleshooting, and if physical access is possible, check the cables that connect the host to the JBOD. Look for bent pins, loose wires, loose cable shields, loose cable casing and any cables with 90 degree or more bends in them. If you find any of these problems, replace the cable.

Verify the cabling configuration is correct. See: "Troubleshooting 351x Cabling", and "Troubleshooting 3120/33x0 Cabling".
Verify component LEDs are Green. If amber LED exists, see the appropriate JBOD Troubleshooting Decision Tree in the Sun StorEdge 3000 Family Installation, Operation, and Service Manual found at the Oracle Documentation Site.
Verify the health of the enclosure(s) and all listed components are OK by:

a) Issuing the show enclosure-status command from the sccli (CLI).

b) For SCSI JBODs directly connected to a host , ensure JBOD support is enabled in Sun Storage [TM] Configuration Services. For more information see: Appendix B (see sections on Monitoring with StorEdge Configuration Services and Enabling JBOD Support), in the Sun StorEdge [TM] 3000 Family Installation, Operation, and Service Manual.
Confirm all enclosures and disks are present. See the appropriate document for examples of enclosures and disk Ids including: Document: 1012313.1: Identifying Disk Drive Ids on a Sun StorEdge [TM] 33x0 Raid SCSI Array with attached JBODs and, Document 1007692.1: Sun Storage 351x Array switch settings and disk IDs.
Confirm there are no failed disks. If the host messages file, event logs, or show enclosure status reports a failed disk, see Document 1001837.1: How to Replace a Disk in a Sun StorEdge[TM] 3510 FC JBOD Array.
Verify the SES revisions on the 3510/3511 JBOD (indicated by a letter D in the Vendor/Product ID field ) are the same by typing show ses from the CLI. See : Sun StorEdge[TM] 351x: JBOD's at Different SES Firmware Revisions is not reported.
Verify that parity errors, or scsi bus resets, or other errors do not appear in /var/adm/messages. If errors appear in logs, see 3120/33x0 JBOD Troubleshooting Decision Trees in step 2 above.
Also, see : Fujitsu (Allegro) drives in Sun StorEdge[TM] 3310 SCSI array connected with Ultra[TM] 320 SCSI HBA can cause scsi bus resets and transport errors.
If JBOD disks are still not visible on the host, see the appropriate document:

For 3120: Sun StorEdge [TM] 3000 Family Installation, Operation, and Service Manual, Document 816-7956

For 3320: Sun StorEdge [TM] 3000 Family Installation, Operation, and Service Manual, Document 819-1274

For 3510: Sun StorEdge [TM] Family Installation, Operation, and Service Manual, Document 816-7300

For 3511: Unlike Sun Storage [TM] 3510 FC products, the Sun Storage [TM] 3511 SATA JBOD cannot be directly attached to a host computer. Sun Storage [TM] 3511 SATA expansion units can be connected to Sun Storage [TM] 3511 SATA arrays.
If no problems were found during the course of this document please refer back to : Troubleshooting Sun StorEdge [TM] 33x0/351x Hardware.

FAB < Solution: 200232 > Sun StorEdge 3510 FC Array and JBOD with RAID fw prior to 4.11, SES fw

prior to 1046, and SSCS sw prior to 2.0 may experience various
downtime, drive offline, and inaccurate component status report.

Synopsis:
Sun StorEdge
3511 FC Array with SATA and JBOD with RAID fw prior to 4.11, SES fw
prior to 0413, and SSCS sw prior to 2.0 may experience various
downtime, drive offline, and inaccurate

Synopsis:
Sun StorEdge
3510 FC Array and JBOD with RAID fw prior to 4.11, SES fw prior to
1046, and SSCS sw prior to 2.0 may experience various downtime,
drive offline, and inaccurate components.

Note: For 3120 JBOD Arrays see: FAB < Solution: 200110 >
Synopsis: Sun StorEdge [TM] 3120 Arrays
with sccli software prior to 2.0 and SAFE-TE firmware prior to 1170
may experience inaccurate status reporting for array
components.

JBOD, 3120, normalized, 3310, 3320, 33x0, 3510, 3511, 351x, disks, failure, Audited
Previously Published As
89047

Change History
Date: 2010-01-12
User Name: [email protected]
Action: Currency & Update
Notes for Normalizaton:
Subset of: 89034
Subset Root path:
89047-->89034-->89031-->89050
References:89053, 80815, 88191, 83673, 72919, 80184, 46440, 80029, 80089, 89064
Project: Minnow Normalization

Testing inter-article linking.
Added 3120 product for Christine.

Attachments

This solution has no attachment