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-72-1549223.1
Update Date:2018-01-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  1549223.1 :   Pillar Axiom: Brick CopyAway Error  


Related Items
  • Pillar Axiom 300 Storage System
  •  
  • Pillar Axiom 600 Storage System
  •  
  • Pillar Axiom 600 Storage System
  •  
  • Pillar Axiom 500 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
  •  


Understanding the "Brick CopyAway Error" Axiom event.

In this Document
Symptoms
Cause
Solution


Created from <SR 3-7130499594>

Applies to:

Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 600 Storage System
Information in this document applies to any platform.

Symptoms

Brick CopyAway Error

Cause

The Axiom array firmware will attempt to identify a marginal drive that may fail in the near future , prior to the drive actually failing. A 'CopyAway' process is started, to copy the still readable data on the suspect disk to the spare.  During this proactive 'CopyAway', it is possible that the suspect disk does indeed fail.  When this occurs a 'Brick CopyAway Error' event is logged.

As the now failed disk cannot be read, the remaining data is placed on the spare by using the RAID protection from the remaining disks in the parity group.

The CopyAway logic is working correctly in this respect.

Sample messages may appear similar to the following:-

 

 [Date&Time] Informational BrickCopyaway /Brick001 RC-1
 [Date&Time] Informational BrickCopyaway /Brick001 RC-0
 [Date&Time] Informational BrickRAIDCopyAwayError /Brick001 RC-0
.....
 [Date&Time] Informational BrickRAIDCopyAwayError /Brick001 RC-0
 [Date&Time] Informational BrickRAIDCopyAwayCompleted /Brick001 RC-0
 [Date&Time] Informational BrickRedundancyRepairStarted /Brick001 RC-0
 [Date&Time] Informational BrickRedundancyRepairStarted /Brick001 RC-0
 [Date&Time] Informational BrickRedundancyRepairCompleted /Brick001 RC-0
 [Date&Time] Warning BrickDiskDriveFault /Brick001 RC-0 Disk-4 ABCDEFGH ST3450856FC
 [Date&Time] Informational BrickCopyaway /Brick001 RC-0


 

Solution

The failed drive should be replaced per the 'BrickDiskDriveFault' error event.
 


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