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-73-1019666.1
Update Date:2010-09-21
Keywords:

Solution Type  FAB (standard) Sure

Solution  1019666.1 :   Some SATA Drives have incorrectly shipped with a Rev 4 DACstore installed.  


Related Items
  • Sun Storage 6140 Array
  •  
Related Categories
  • GCS>Sun Microsystems>Sun FAB>Standard>Reactive
  •  

PreviouslyPublishedAs
243306


Bug Id
<SUNBUG: 6746964>

Product
Sun StorageTek CSM200 Expansion Tray
Sun StorageTek 6140 Array
Sun StorageTek 5320 NAS Appliance

Date of Resolved Release
10-Oct-2008

SATA drives incorrectly shipped with Rev 4 DACstore installed (see details below).

Affected X-Options:

XTC-ST1CF-1TB7KZ      1TB 7200 RPM SATA Drive
XTC-ST1CF-750G7KZ    750GB 7200 RPM SATA Drive
XTC-ST1CF-500G7KZ    500GB 7200 RPM SATA Drive

Affected Parts:

540-7590-01    1TB 7200 RPM SATA Drive
540-7245-01    750GB 7200 RPM SATA Drive
540-6635-02 (or below)    500GB 7200 RPM SATA Drive

Impact

Putting a Rev 4 DACstore drive into an array running 6.x controller firmware will cause the drive to be unusable by the array, but otherwise be unharmful.

These same drives will work fine in arrays running 7.x controller firmware.

Contributing Factors

This issue has been observed during both the replacement of failed drives and the addition of new drives (x-options) to an existing array.  The problem will only be seen in arrays running 6.x controller firmware because it's Rev 3 DACstore version is incompatible with Rev 4.

Thus far the problem has been seen only in 750GB and 1TB SATA drives, but it is possible that a smaller number of 500GB SATA drives may also exhibit the same problem.

Symptoms

If the drive is introduced to the array by way of a replacement of a failed drive, CAM will generate an alarm or SANtricity will generate a recovery guru notification of;

    Severity:     Critical
    Date:     <date>
    State:     Open
    Acknowledged By:
    Auto Clear     Yes
    Description:     An uncertified drive has been detected: Tray.XX.Drive.XX
    Info:
    Device:     <array-name>
    Component:     Tray.XX.Drive.XX
    Event Code:     57.66.1027
    Aggregated Count:     <count>

If the drive is unassigned/new the drive will not be seen by the Management Host and as such will be unable to generate any notification to the Management Host.  But the problem will show the following in the serial shell;

    08/25/08-17:50:05 (GMT) (utlTimer): NOTE:  fcnChannelReport ==> +0 +1  2 =3
    08/25/08-17:50:36 (GMT) (utlTimer): NOTE:  fcnChannelReport ==> +0 +1  2 =3
    08/25/08-17:50:45 (GMT) (ssmDriveSpinTask): NOTE:  cfgCommonReplaceCode: dev = 0x1
    08/25/08-17:50:45 (GMT) (ssmDriveSpinTask): WARN:  Unsupported dacstore: dev = 0x1
    08/25/08-17:50:45 (GMT) (ssmDriveSpinTask): WARN:  Unsupported dacstore: dev = 0x1
    08/25/08-17:50:46 (GMT) (ssmDriveSpinTask): NOTE:  cfgCommonReplaceCode: complete dev = 0x1

Root Cause

A number of SATA drives escaped from the factory with DACstore on them.  These drives, either as spares or x-options coming from the factory should not have a DACstore on them.

This has been resolved in Manufacturing in mid-August 2008 (37th week) via StopShip/Purge P001-20559, and in Services via GSAP# 4509 published on September 29, 2008.  Going forward anti-static bags will also be tagged with a sticker saying "cleardac" to certify the drive is safe to use in any supported array.

Going forward Service personnel should consider the seal on the anti-static bag containing the drive FRU to certify that the drive is safe to use in any supported array.  Bags with seals that are already broken should not be used unless it known with certainty that the drive does not have a DACstore on it.

Corrective Action

Workaround:

No workaround available - see Resolution section below.

Resolution:

If this issue is observed in the field, an escalation to PTS Storage is required to fix the problem.  On-site personnel will also need to have a working serial port cable.

Identification of Affected Parts (how to):

There is no effective way to identify the affected parts other than the failures detailed above.

References:

  BugID: 6746964
  Escalation ID: 71905715
  Other References: PITT# 2238
  GSAP: 4509
  WW Stop Ship: P001-20559
  Radiance ID: 66060106, 66054505


For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:

For Sun Authorized Service Providers go to:

In addition to the above you may email:


Modification History
Changes made since initial publication.

17-Apr-2009
  • Multiple changes made Impact, Root Cause, and How To sections.

Internal Contributor/submitter
Bob.Deguc@Sun.COM

Internal Eng Responsible Engineer
Bob.Deguc@Sun.COM Responsible Manager: Kyle.Mayle@Sun.COM

Internal Services Knowledge Engineer
Joe.Davis@Sun.COM

Internal Eng Business Unit Group
NWS (Storage)

Internal Sun Alert & FAB Admin Info
07-Oct-2008: Finalized draft - sent to Extended Review.
10-Oct-2008: Addressed Ext Rvw feedback - sending to Publish.
01-Dec-2009: Corrected Product Name to swoRDFish inconsistency.


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