Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1009137.1
Update Date:2011-04-06
Keywords:

Solution Type  Problem Resolution Sure

Solution  1009137.1 :   Sun StorageTek[TM] 351x/33x0: Resolving Drive NONE USED status for Raid 5 logical drives  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3320 SCSI Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
212646


Symptoms
Following an engineer visit it was decided that a disk [ID3] had not failed
and was placed back into the unit. At this point the disk is given the
following status:
Ch Id Size Speed LD Status IDs

----------------------------------------------------------------------
[snip]
0 2 68.37GB 160MB ld0 ONLINE SEAGATE ST373307LSUN72G 0207
0 3 68.37GB 160MB NONE USED SEAGATE ST373307LSUN72G 0207
0 4 68.37GB 160MB ld0 ONLINE SEAGATE ST373307LSUN72G 0207
[snip]
0 13 68.37GB 160MB NONE USED SEAGATE ST373307LSUN72G 0207

IMPORTANT NOTE
This procedure is to be used ONLY when the LD(s) are in either "DEGRADED" or "OPTIMAL" state. It should NOT be used when the LD is in a "DEAD" state. Using this procedure for dead LDs may result in lost data with little or no chance of recovery.



Resolution
Final Outcome to be:
o ID3 being ONLINE within the Raid5 LD0

o ID13 to be a Global Standby.

Drives in NONE/USED are already detected by the controller, therefore a
"Scan Drive" operation can no longer be performed on those IDs.

Here's what to do instead :

- go "view and edit SCSI Drives"
- select ID3 (NONE/USED #1)
- select "add Global spare"
- designate ID3 global spare
- go to "view and edit configuration parameters"
--> select Disk Array parameters
--> select rebuild priority and set it to "Normal" or "improved",

(when selecting "improved" discuss with the customer ... their I/O may be
impacted)

- go back to root of firmware menu
- go to "view and edit logical drive"
- select the logical drive that needs to be rebuilt (should be "DEGRADED")
- choose "rebuild a logical drive"
- watch the "manual rebuild" kick off
- once the rebuild is running go back to root menu
- go "view and edit SCSI Drives"
- select ID13 (NONE/USED #2)
- select "add Global spare"
- designate ID13 global spare

This way if we truly have a faulty disk in ID3 and the rebuild
back to it fails then ID13 will be used instead as it is a Global spare.



Additional Information
See also:

Sun StorEdge 3000 Family RAID Firmware 4.2x User's Guide


for Sun StorEdge[TM] 3510 FC/3511 SATA and 33x0 SCSI.

See Chapter 6 for Manual Rebuild information, and Drive Status description USED DRV
The drive was previously configured as part of a logical drive from which
it has been removed; it still contains data from this logical drive.



Product
Sun StorageTek 3510 FC Array
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3511 SATA Array
Sun StorageTek 3320 SCSI Array


Change History
Date: 2010-04-23
User Name: 79977
Action: Currency Check
Comment: Title changed as per CL feedback,
Susan.Copeland@oracle.COM

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback