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-1018667.1
Update Date:2011-02-11
Keywords:

Solution Type  Problem Resolution Sure

Solution  1018667.1 :   Sun Storage[TM] 3510/3511 FC Array: Ghost Drive Presentive Configuration  


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

PreviouslyPublishedAs
230369


Applies to:

Sun Storage 3510 FC Array
Sun Storage 3511 SATA Array
All Platforms

Symptoms



Symptoms

Output of  sccli>show logical-drives:
* logical-drives
LD LD-ID Size Assigned Type Disks Spare Failed Status
------------------------------------------------------------------------
ld0 40A5C5A1 340.58GB Primary RAID1 10 3 0 Good


There are only 12 drives on this array, and 10 are used by the logical drive.
Two of the drives are hot-spares but the above output shows an extra hotspare.
Sun Storage[TM] 3510/3511 (SE3510) firmware is at revision 4.13C in this example.
This problem happened on the SE3510 but it can also happen with SE3511.

+

Changes

{CHANGE}


Cause

{CAUSE}

Additional Information

This problem was thought to be in NVRAM but the problem remained even after NVRAM was reset. Telnet to the SE3510 array showed the presence of an additional drive which confirmed that this is a firmware bug.

Even after removing all the hotspares, one hotspare is seen configured for the logical drive.

Solution



Resolution
There is no permanent resolution to this problem as there was no reliable method to reproduce this issue.

Relief/Workaround

If the customer does not want to Backup->Delete LD-> Create LD -> Restore, there is one
more option which may work. This is to recreate the logical drive without initializing
the data. To get this procedure, please escalate to Level 2 Support and they may be able
to provide a procedure where we just Delete LD -> "Use the LD Recovery Procedure*"
and the data should be intact.

In the event that the LD recovery procedure does not result in the data being intact then a restore from backup is required.

*The LD Recovery Procedure may not be applicable. PTS can determine
if this situation meets the criteria for the procedure.



Please see CR 6374218



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