Sun Storage 3000 Arrays: How to Resolve the Degraded Status of a Redundant (RAID-5 or RAID-1) Logical Drive
Last updated on SEPTEMBER 19, 2017
Applies to:Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
Sun Storage 3310 SCSI Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Information in this document applies to any platform.
This document provides the procedure to return a DEGRADED logical drive, on a Sun Storage 3310, 3320, 3510 or 3511 Array, to a GOOD status. The information in this document is primarily for arrays running 3.x firmware, but may be used on a 4.x array assuming the initial set of conditions are identical. Normally, for arrays running 4.x firmware, you should follow the procedures in "Rebuilding a Logical Drive" from the Sun StorEdgeTM 3000 Family RAID Firmware 4.2x User’s Guide.
The problem will reveal itself with the data collected from the sccli interface. In this example, you can see two Degraded RAID-5 Logical Drives. show logical-drives lets us know there is a failed disk in each LD. show disks lets us know what the two good disks are. However, there is nothing reported that lets us know which disks have failed.
There have been no changes per se. The problem manifests itself via a series of events on the array. The event logs may show some disk failures, drive channel failures, loop initialization's (LIP's), usually followed by a controller reset. The timing and combination of these Events is unknown. However, when the array comes back online, the result is a Degraded Logical Drive with no associated failed disks.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms