Sun Storage 3000 Arrays: Troubleshooting JBOD Failures

Asset ID:	1-75-1002790.1
Update Date:	2016-04-04
Keywords:

Solution Type Troubleshooting Sure

Solution 1002790.1 : Sun Storage 3000 Arrays: Troubleshooting JBOD Failures

Applies to:

Sun Storage 3320 SCSI Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3120 SCSI Array - Version Not Applicable and later
All Platforms

Purpose

The purpose of this document is to assist in troubleshooting Sun Storage 3000 Array JBOD failures.

Symptoms:

'format' shows "drive not available"
'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

Troubleshooting Steps

This is a sub-set of <Document 1011431.1> Troubleshooting Sun Storage 3000 Array Series 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 <Document 1008193.1> Sun Storage 3510 and 3511 Arrays: Troubleshooting the Cabling, and <Document 1006857.1> Verifying and Troubleshooting Sun Storage 3120, 3310 and 3320 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> Sun Storage 3310 and 3320 Arrays: How to Identify Disk IDs and Correct Backend Cabling, and <Document 1007692.1> Sun Storage 3510 and 3511 Arrays: How to Identify Switch IDs, Disk IDs and Correct Backend Cabling.
Check and confirm if there are any failed disks.

a) See if disk any utilities show a drive is missing/failing: Examples "format" reports "<drive not available>"; "fdisk" reports "I/O error" or "unable to read"

b) See if the host messages file, event logs, "dmesg", or "show enclosure status" reports a failed disk.

If a drive is suspected/identified and confirmed to have failed refer to <Document 1001837.1> How to Replace a Disk in a Sun StorEdge 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 <Document 1002758.1> Sun StorEdge[TM] 351x: JBODs at Different SES Firmware Revisions is not reported.
Verify that parity errors, 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 <Document 1006888.1> Sun Storage 3310 Array Connected with Ultra320 SCSI HBA: Fujitsu (Allegro) Drives Can Cause SCSI Bus Resets and Transport Errors.
If JBOD disks are still not visible on the host, see the appropriate document at the Oracle Documentation Site:

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 <Document 1011431.1> Troubleshooting Sun Storage 3000 Array Series Hardware.

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

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.

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

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: sue.copeland@sun.com
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

References

<NOTE:1002758.1> - Sun StorEdge[TM] 351x: JBOD's at Different SES Firmware Revisions is not reported
<NOTE:1001837.1> - How To Replace A Disk In a Sun Storage 3510 FC JBOD.
<NOTE:1006857.1> - Verifying and Troubleshooting Sun Storage 3120, 3310 and 3320 Cabling
<NOTE:1006888.1> - Sun Storage 3310 Array Connected with Ultra320 SCSI HBA: Fujitsu (Allegro) Drives Can Cause SCSI Bus Resets and Transport Errors
<NOTE:1007692.1> - Sun Storage 3510 and 3511 Arrays: How to Identify Switch IDs, Disk IDs and Correct Backend Cabling
<NOTE:1012313.1> - Sun Storage 3310 and 3320 Arrays: How to Identify Disk IDs and Correct Backend Cabling
<NOTE:1011431.1> - Troubleshooting Sun Storage 3000 Array Series Hardware
<NOTE:1008193.1> - Sun Storage 3510 and 3511 Arrays: Troubleshooting the Cabling

Attachments

This solution has no attachment