Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1001199.1
Update Date:2013-03-04
Keywords:

Solution Type  Sun Alert Sure

Solution  1001199.1 :   DRAM Parity Errors or SDRAM ECC Errors on Sun StorEdge 3310, Sun StorEdge 3510 or 3511 FC Arrays May Cause File System Integrity Issue  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3511 SATA Array
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun Alert
  •  
  • _Old GCS Categories>Sun Microsystems>Sun Alert>Criteria Category>Data Loss
  •  
  • _Old GCS Categories>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
201594


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

Date of Workaround Release: 03-AUG-2004

Date of Resolved Release: 30-AUG-2005

***Checked for relevance on 04-Mar-2013***

Impact

In some rare cases, multi-bit DRAM parity errors or multi-bit SDRAM ECC errors on Sun StorEdge 3310, Sun StorEdge 3510 or 3511 FC arrays may cause loss of file system integrity.

Note: There is a very low probability for the occurrence of this issue.


Contributing Factors

This issue can occur on the following platforms:

  • Sun StorEdge 3310 array without patch 113722-11
  • Sun StorEdge 3510 array without patch 113723-10
  • Sun StorEdge 3511 FC array without patch 113724-04

This issue can occur when the controller firmware fails to distinguish between single-bit ECC errors and multi-bit ECC errors. The controller seems to continue to work normally even for multi-bit errors, which leads to loss in file system integrity. A single-bit ECC error is recoverable, while a multi-bit ECC error is not.

Note: This issue may only occur when SE3310, SE3510 or SE3511 arrays encounter multi-bit DRAM parity errors or multi-bit SDRAM ECC errors. Single-bit parity or ECC errors would not encounter this issue.


Symptoms

Should the described issue occur, DRAM parity error messages similar to following are logged in SCCLI event log:

    [0104] #4287: StorEdge Array SN#xxxxxxx Controller ALERT: DRAM parity error detected

SDRAM error messages similar to following are logged in "/var/adm/messages" file:

    Mar 19 18:30:23  SUNWscsdMonitor[628]: [ID 298706 daemon.error]
[SUNWscsd 0x10B1D0D: Critical] <rctrl6003> Controller Event,  SDRAM  Error.
Likely controller error. If error persists, replace defective controller.
(Primary, Fri Mar 19 18:23:36 2004) {SN#00369b}
.
.
Mar 20 04:21:20  SUNWscsdMonitor[628]: [ID 739865 daemon.error]
[SUNWscsd 0x10B1D0D: Critical] <rctrl6003> Controller Event,  SDRAM  Error.
Likely controller error. If error persists, replace defective controller.
(Primary, Sat Mar 20 04:14:25 2004) {SN#00369b}

Workaround

There is no workaround for this issue. Please see the Resolution section below.


Resolution

This issue is addressed on the following platforms:

  • Sun StorEdge 3310 with patch 113722-11 or later
  • Sun StorEdge 3510 with patch 113723-10 or later
  • Sun StorEdge 3511 (FC) with patch 113724-04 or later


Modification History
14-JAN-2004: Add point patch for SSE 3510 to Relief/Workaround section
30-AUG-2005: Update Contributing Factors and Resolution sections
04-Mar-2012: Checked for currency/relevance, product attribution; no change in content

References





Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback