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-77-1000797.1
Update Date:2011-02-25
Keywords:

Solution Type  Sun Alert Sure

Solution  1000797.1 :   "Support Data Collection" Procedure on Certain Sun StorEdge and Sun StorageTek Arrays May Cause SATA Drive Failures  


Related Items
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6130 Array
  •  
  • Sun Storage 6140 Array
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
201075


Product
Sun StorageTek 6130 Array
Sun StorageTek 6140 Array
Sun StorageTek 6540 Array

Bug Id
<SUNBUG: 6491409>

Date of Workaround Release
15-DEC-2006

Date of Resolved Release
22-FEB-2007

Impact

If the "Support Data Collection" procedure is run while the drives are in use on Sun StorEdge 6130 or Sun StorageTek 6140/6540 arrays, SATA drive failure may occur, causing volumes and underlying VDisks to also become degraded or to fail. These failures will result in a loss of access to data in the volumes.


Contributing Factors

This issue can occur on the following platforms:

  • Sun StorEdge 6130 array with firmware 06.12.27.10 and earlier and without firmware  06.19.23.10
  • Sun StorageTek 6140 array with firmware 06.16.81.10 and without firmware  06.19.23.10
  • Sun StorageTek 6540 array with firmware 06.16.81.10 and without firmware  06.19.23.10

Note: The above arrays must have SATA drives present to be affected by this issue.


Symptoms

When using "Common Array Manager"(CAM), drive failures and possibly volume failures may occur when executing a "Support Data Collection" procedure via the Service Advisor or when running the following command:

    $ /opt/SUNWsefms/bin/supportData

Using "Configuration Services" for the StorEdge 6130 and StorageTek 6140 arrays will also cause drive/volume failures when collecting support information by running the following command:

    $ /opt/SUNWstade/bin/SupportData

Note: This includes Sun Explorer versions 5.0 and above when run on a StorADE management host.

SANtricity will produce the same results as above when collecting support information using the following menu tree selection:

Advanced->Troubleshooting->Collect All Support Data


Workaround

To work around the described issue (if SATA drives are in the array), avoid using operations that collect support data (as outlined above) while the array is actively accepting I/O from hosts.


Resolution

This issue is addressed in the following releases:

  • Sun StorEdge 6130 array with firmware 06.19.23.10 or later
  • Sun StorageTek 6140 array with firmware 06.19.23.10 or later
  • Sun StorageTek 6540 array with firmware 06.19.23.10 or later

Firmware version 06.19.23.10 was released with Sun StorageTek Common Array Manager (CAM) 5.1.

Sun StorageTek Common Array Manager (CAM) 5.1. is available for download at www.sun.com/download under Systems Administration and by selecting Storage Management. Look for "Sun StorageTek Common Array Manager (CAM) 5.1" in the list of downloads provided.



Modification History
Date: 22-FEB-2007
  • State: Resolved
  • Updated Contributing Factors and Resolution sections


Previously Published As
102753
Internal Comments


Within the MEL log drive errors are seen with the Event specific code 05/2c/00 signature just prior to the drive being failed:




    Date/Time: Thu Oct 26 14:06:30 CEST 2006
    Sequence number: 530762
    Event type: 100A
    Event category: Error
    Priority: Informational
    Description: Drive returned CHECK CONDITION
    Event specific codes: 5/2c/0
    Component type: Drive
    Component location: Tray.1.Drive.7
    Logged by: Controller in slot B


Raw data:




    4d 45 4c 48 02 00 00 00 4a 19 08 00 00 00 00 00
    0a 10 11 20 c6 a4 40 45 01 00 60 00 0a 01 00 00
    01 00 00 00 3c 00 00 00 01 00 00 00 01 00 00 00
    01 00 00 00 01 00 00 00 01 00 00 00 07 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 01 00 00 00 02 1c 00 00
    12 00 0d 01 70 00 05 00 00 00 00 0a 00 00 00 00
    2c 00 00 00 00 00 02 00 0d 81 cc 01


The fix is included with the delivery of array firmware 06.19.18.10. The final build of the 06.19.xx.10 firmware is still pending.



For cases where this bug has been identified, PTS/Backline can provide a pre-release of this firmware to customers. An escalation will be required for delivery.


Internal Contributor/submitter
[email protected], [email protected]

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
[email protected]

Internal Services Knowledge Engineer
[email protected]

Internal Escalation ID
43484691, 1-20436107

Internal Sun Alert Kasp Legacy ID
102753

Internal Sun Alert & FAB Admin Info
Critical Category: Availability ==> HA-Failure
Significant Change Date: 2006-12-15, 2007-02-22
Avoidance: Upgrade, Workaround
Responsible Manager: [email protected]
Original Admin Info: [WF 22-Feb-2006, Jeff Folla: Updated with firmware version that addresses this issue. This is now resolved. Sent for re-release.]
[WF 15-Dec-2006, dave m: send for release]
[WF 14-Dec-2006, dave m: draft created, send for review]

Product_uuid
8252cb91-d771-11d8-ab52-080020a9ed93|Sun StorageTek 6130 Array
8ac7dca5-a8bd-11da-85b4-080020a9ed93|Sun StorageTek 6140 Array
e35cfcfc-a31a-11da-85b4-080020a9ed93|Sun StorageTek 6540 Array

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