Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

Increased fan vibration can lead to Disk Drive failures

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FCOs are internal - this KM doc details instructions for implementing FCO 333.

Applies to:

Goal

 Provide TSC Engineers with implementation instructions for FCO 333.

Solution

1. Parts Order and Set Up Steps:
   
   
   1. In the Open Service Request, set the Root Cause to Hardware and the Reason Code to  Field Change Order.
   2. If the system has encountered multiple failed drives causing LUNs to go offline - engage Engineering immediately to determine the next course of action to avoid customer data loss.
   3. If the customer asks for all eligible drives to be replaced, replace any drive with the part numbers covered by this FCO in all Bricks in slots 3-8 and Hot Spare.
   4. Since this is a conditional FCO, email a verification request to: AXIOM_CONDITIONAL_FCO_WW_GRP@oracle.com with "FCO 333 Request" in the subject and include the following template:
      
      Service Request #:
      Customer Name:
      Country/Geo:
      System Type: Ax600
      System Serial #:
      Requested Replacement: Y x 1450-00310-30 + Z x 1450-00311-30
      
      
      Note: the values of Y & Z will normally be 6 & 1 respectively but may be less if some of the affected drives have already been replaced by 2TB drives
        
      Note: once the issue has been validated, an L2 Engineer will then forward the request to FCO333_2TB_WW_GRP@oracle.com and cc the SR owner to release the parts.
        
      
      
   5. Once you have the approval - order the needed parts to implement the FCO.  Be sure to add "Dispatch Drives from Regional T1 location" in the Special Instruction box of the Dispatch Instructions of Field Service Task.
   6. If the Axiom is running R5.3 or higher, use SMART_DATA_R5.exe or for earlier versions, the event log, to identify any potential bad drives that may cause reconstruction problems.
   7. Create an on site FS Task for FE to replace the affected drives.  Note in the task which Bricks are affected.
      
      
2. FCO Implementation - FE On Site:
   
   
   1. Confirm no reconstruction or copy back processes are active.
   2. Using Axiom's Guided Maintenance, replace all affected Hot Spare drives that are NOT in use.
      
      If a Hot Spare Drive is in use, use Guided Maintenance to replace the failed drive.  Only use a 2TB drive if the failed drive is in slots 3-8.
      
      
   3. If any drive errors were observed in 1-e above, replace those drives first starting with the drives with the highest error count.
      1. Slots 0-2 & 9-11 replace with the same part # of the existing drive.
      2. Slots 3-8 & Hot Spare replace with new 2TB drives as part of FCO 333. 
      3. Only use Guided Maintenance for these drive replacements.
   4. If the Axiom is running R5.3 or higher use the CopyAway_R5.exe utility to copy data to Hot Spare drive and avoid reconstruction, otherwise use Guided Maintenance to replace. 
   5. Repeat steps 2-a through 2-d until all the affected drives have been replaced being sure to wait until the Hot Spare has completed the copy-back before replacing the next drive.
      
      

References

This solution has no attachment