How to Replace a Hard Drive in an Exadata Storage Server (Predictive Failure)

Asset ID:	1-71-1390836.1
Update Date:	2018-04-30
Keywords:

Solution Type Technical Instruction Sure

Solution 1390836.1 : How to Replace a Hard Drive in an Exadata Storage Server (Predictive Failure)

Applies to:

Exadata X6-8 Hardware - Version All Versions and later
Oracle SuperCluster T5-8 Half Rack - Version All Versions and later
Exadata X4-2 Full Rack - Version All Versions and later
Zero Data Loss Recovery Appliance X6 Hardware - Version All Versions and later
Exadata X3-2 Half Rack - Version All Versions and later
Information in this document applies to any platform.

Goal

How to Replace a Hard Drive in an Exadata Storage Server (Cell) (Predictive Failure)
Disks with status "Poor Performance" should follow this procedure also. The status may not exactly state "Predictive Failure", it may also be in one of several "Proactive Failure" states.
(For Hard Failure, please see Doc ID 1386147.1)

Solution

DISPATCH INSTRUCTIONS:
The following information will be required prior to dispatch of a replacement:

Exadata Model (V2, X2, X3 etc.) / Exadata Storage Expansion Rack (X2, X3 etc.)
Type of storage cell/Node (V2=x4275 / X2 =x4270m2 / X3 = X3-2L / X4 = X4-2L / X5 = X5-2L / X6=X6-2L / X7 = X7-2L)
Size of failed drive and part number
Name/location of storage cell
Slot number of failed drive
Image Version (output of "/opt/oracle.cellos/imageinfo -all")

Special Instructions for Dispatch are required for this part.

For Attention of Dispatcher:

The parts required in this action plan may be available as spares owned by the customer, which they received with the Engineered System. (These are sometimes referred to as ride-along spares.)

If parts are not available to meet the customer preferred delivery time/planned end date, then request TAM or field manager to contact the customer, and ask if the customer has parts available, and would be prepared to use them.

If customer spare parts are used, inform the customer that Oracle will replenish the customer part stock as soon as we can. More details on this process can be found in GDMR procedure "Handling Where No Parts Available" step 2: https://ptp.oraclecorp.com/pls/apex/f?p=151:138:38504529393::::DN,BRNID,DP,P138_DLID:2,86687,4,9082,

WHAT SKILLS DOES THE ENGINEER NEED:
The engineer must be Exadata trained, have familiarity with the storage cells and replacing hard drives.

TIME ESTIMATE: 60 minutes

Complete process may take longer depending on rebalance time that may be required.

TASK COMPLEXITY: 0
CRU-optional; default is FRU with Task Complexity: 2

FIELD ENGINEER INSTRUCTIONS:
PROBLEM OVERVIEW:
Failed hard drive in Exadata.

This document is specific to hard drives in "predictive failure" or "proactive failure" or "poor performance" states and sub-states. There are situations where a drive will be flagged at first as a predictive failure or proactive failure or poor performance but the drive will hard fail (go into "critical" status) before the rebalance operation has completed. In such cases, please reference Doc ID 1386147.1 for replacement steps.

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?:
It is expected that the Exadata Machine is up and running and the storage cell containing the failed drive is booted and available.

If there are multiple drives to be replaced within an Exadata machine (or between an Exadata interconnected with another Exadata or Expansion Cabinet), it is critical that only ONE DRIVE BE REPLACED AT A TIME to avoid the risk of data loss. This is particularly important in the case of disks running in predictive failure status. Before replacing another disk in Exadata, ensure the rebalance operation has completed from the first replacement.

Before proceeding, confirm the part number of the part in hand (either from logistics or an on-site spare) matches the part number dispatched for replacement (especially important in cases where the customer has multiple racks of different drive types/sizes).

600GB Special Handling (Exadata Critical Alert EX32): Exadata Storage Servers in V2, X2-2 and X2-8 systems with 600GB high performance disk drives must run version 11.2.2.4.1 (released December 2011) or higher, prior to completing this procedure to replace the disk, or the replacement will not be accepted by the Exadata Storage Server software. See Doc ID 2199949.1 for details.

8TB Special Handling: Exadata Storage Servers in X2-2 and later with 8TB disk drives must run version 12.1.2.3.6 or 12.2.1.1.2 (released July 2017) or higher, prior to completing this procedure to replace the disk if the replacement part is 7337414, or the replacement may not be accepted by the Exadata Storage Server software. If the image is earlier, then only use part 7301588. For Exadata/ZDLRA refer to Doc ID 2352138.1 for details. For SuperCluster refer to Doc ID 2376948.1 for details.

Customer Critical Preparation Required: It is expected that the customer's DBA has completed these steps in Doc ID 1326611.1 prior to arriving to replace the disk.

If the customer or the FSE requires more assistance prior to the physical replacement of the device, EEST/TSC should be contacted.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Confirm the drive needing replacement based on the output provided ("name" or "slotNumber" value) and LED status of the drive. For a predictive failure, the LED for the failed drive should have the "Service Action Required" amber LED illuminated/flashing. The cell server within the rack can be determined from the hostname usually, and the known default Exadata server numbering scheme. The server should also have its LOCATE white LED illuminated/flashing.

Perform the physical replacement of the disk following the directions from the service manual of the respective server (see REFERENCE INFORMATION below):

Slot locations for Exadata Storage Servers based on Sun Fire X4275 and Sun Fire X4270M2 servers:
View from the front:

HDD 2  5  8  11
HDD 1  4  7  10
HDD 0  3  6  9

Slot locations for Exadata Storage Servers based on Sun Server X3-2L/X4-2L and Oracle Server X5-2L/X6-2L/X7-2L servers:
View from the front:

HDD 8  9  10 11
HDD 4  5  6  7
HDD 0  1  2  3

1. If it is not already, turn on the service LED for the device with the following command, where <ID> is the "name" value provided in the action plan (such as 20:3 in the example above):

CellCLI> alter physicaldisk <ID> serviceled on

CellCLI> alter physicaldisk 20:3 serviceled on

This will cause the disk's Amber fault LED to blink rapidly as a locate indication.
Note: This step only applies to older images that had bugs that caused inconsistent LED behavior.

2. On the drive you plan to remove, push the storage drive release button to open the latch.

3. Grasp the latch and pull the drive out of the drive slot (Caution: The latch is not an ejector. Do not bend it too far to the right. Doing so can damage the latch. Also, whenever you remove a storage drive, you should replace it with another storage drive or a filler panel, otherwise the server might overheat due to improper airflow.)

4. Wait three minutes for the MS daemon to recognize the removal of the old drive.

5. Slide the new drive into the drive slot until it is fully seated.

6. Close the latch to lock the drive in place.

7. Verify the "OK/Activity" Green LED begins to flicker as the system recognizes the new drive. The other two LEDs for the drive should no longer be illuminated.

8. Wait three minutes for the MS daemon to start rebuilding the virtual drives before proceeding. Note: Do not run any controller commands in the service manual when replacing the disk.

9. The server's locate and disk's service LED locate blinking function should automatically turn off. If it does not, it can be manually turned off for the device if it was turned on in step 1, using the same "<ID>" value:

CellCLI> alter physicaldisk 20:3 serviceled off

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

It is expected that the engineer stay on-site until the customer has given the approval to depart. After the drive has been physically replaced, the system will automatically perform required actions to bring the drive active within ASM and mdadm if applicable. The customer should check the status of the drive after replacement. The following commands are provided as guidance in case the customer needs assistance checking the status of the system following replacement. If the customer or the FSE requires more assistance following the physical replacement of the device, EEST/TSC should be contacted.

After replacing the physical disk on Exadata Storage Server, wait for three minutes before running any commands to query the device from the server. CellCLI (examples below) should be the principle tool to query the drives. If that is unsuccessful you can use "lsscsi" and "/opt/MegaRAID/MegaCli/MegaCli64 -PDList -a0" to verify the drive from an OS perspective.

1. When you replace a physical disk, first the disk must be acknowledged by the RAID controller before the rest of the system can access it. Login to the cell server and enter the CellCLI interface, and run the following command, where <ID> is the "name" value provided in the action plan:

CellCLI> LIST PHYSICALDISK <ID> detail

CellCLI> list physicaldisk 20:3 detail
         name:                   20:3
         ...
         luns:                   0_3
         ...
         physicalInsertTime:     2012-07-23T19:11:58-04:00
         ...
         slotNumber:             3
         status:                 normal

The "status" field should report "normal". Note also that the physicalInsertTime should be current date and time, and not an earlier time. If they are not, then the old disk entries may still be present and the disk replacement did not complete succesfully. If this is the case, refer to the SR owner for further assistance.

2. The firmware of the drive will be automatically upgraded to match the other disks in the system when the new drive is inserted, if it is below the supported version of the current image. If it is above the minimum supported version then no action will be taken, and the newer firmware will remain. This can be validated by the following command:

CellCLI> alter cell validate configuration

3. After the physical disk is replaced, a lun should be automatically created, and the grid disks and cell disks that existed on the previous disk in that slot are automatically re-created on the new physical disk. If those grid disks were part of an Oracle ASM group, then they will be added back to the disk group and the data will be rebalanced on them, based on the disk group redundancy and asm_power_limit parameter values.

Grid disks and cell disks can be verified with the following CellCLI command, where the lun name is reported in the physicaldisk output from step 1 above ("0_3" in this example"):

CellCLI> list lun 0_3 detail
         name:                   0_3
         cellDisk:               CD_03_edx2cel01
         ...
         status:                 normal

CellCLI> list celldisk where lun=0_3 detail
         name:                   CD_03_edx2cel01
         comment:
         creationTime:           2012-07-23T19:12:04-04:00
         ...
         status:                 normal

CellCLI> list griddisk where celldisk=CD_03_edx2cel01 detail
         name:                   DATA_Q1_CD_03_edx2cel01
         availableTo:
         cellDisk:               CD_03_edx2cel01
         ...
         status:                 active

         name:                   DBFS_DG_CD_03_edx2cel01
         availableTo:
         cellDisk:               CD_03_edx2cel01
         ...
         status:                 active

         name:                   RECO_Q1_CD_03_edx2cel01
         availableTo:
         cellDisk:               CD_03_edx2cel01
         ...
         status:                 active

Status should be normal for the cell disks and active for the grid disks. All of the creation times should also match the insertion time of the replacement disk. If they are not, then the old disk entries may still be present and the disk replacement did not complete succesfully. If this is the case, refer to the SR owner for further assistance.

Note: The lun name attribute will also be shown in the original alert generated by the storage cell.

4. To confirm that the status of the rebalance, connect to the ASM instance on a database node, and validate the disks were added back to the ASM diskgroups and a rebalance is running:

SQL> set linesize 132
SQL> col path format a50
SQL> select group_number,path,header_status,mount_status,name from V$ASM_DISK where path like '%CD_03_edx2cel01';

GROUP_NUMBER PATH                                         HEADER_STATU MOUNT_S NAME
------------ -------------------------------------------- ------------ ------- ------------------------------
           1 o/192.168.9.9/DATA_Q1_CD_03_edx2cel01         MEMBER       CACHED DATA_Q1_CD_03_edx2cel01
           2 o/192.168.9.9/DBFS_DG_CD_03_edx2cel01         MEMBER       CACHED DBFS_DG_CD_03_edx2cel01
           3 o/192.168.9.9/RECO_Q1_CD_03_edx2cel01         MEMBER       CACHED RECO_Q1_CD_03_edx2cel01

SQL> select * from gv$asm_operation;

   INST_ID GROUP_NUMBER OPERA STAT      POWER     ACTUAL      SOFAR   EST_WORK EST_RATE
---------- ------------ ----- ---- ---------- ---------- ---------- ---------- ----------
EST_MINUTES ERROR_CODE
----------- --------------------------------------------
         2            3 REBAL WAIT         10

         1            3 REBAL RUN          10         10       1541       2422
      7298           0

An active rebalance operation can be identified by STATE=RUN. The column group_number and inst_id provide the diskgroup number of the diskgroup being rebalanced and the instance number where the operation is running. The rebalance operation is complete when the above query returns "no rows selected".

Validate the expected number of griddisks per failgroup and diskgroup. Normal deployment includes 12 griddisks for data, 12 for reco and 10 for dbfs_dg. (MODE_STATUS = ONLINE or MOUNT_STATUS=CACHED) (via SQL> )

SQL> select group_number,failgroup,mode_status,count(*) from v$asm_disk group by group_number,failgroup,mode_status;

The rebalance operation has completed when there are no "group_number" values of 0, and each disk group has count the same number of disks.

If the new griddisks were not automatically added back into the ASM diskgroup configuration, then locate the disks with group_number=0, and add them back in manually using "alter diskgroup <name> add disk <path> rebalance power 10;" command:

SQL> select path,header_status from v$asm_disk where group_number=0;

PATH                                               HEADER_STATU
-------------------------------------------------- ------------
o/192.168.9.9/DBFS_DG_CD_03_edx2cel01        FORMER
o/192.168.9.9/DATA_Q1_CD_03_edx2cel01        FORMER
o/192.168.9.9/RECO_Q1_CD_03_edx2cel01        FORMER

SQL> alter diskgroup dbfs_dg add disk 'o/192.168.9.9/DBFS_DG_CD_03_edx2cel01' rebalance power 10;
SQL> alter diskgroup data_q1 add disk 'o/192.168.9.9/DATA_Q1_CD_03_edx2cel01' rebalance power 10;
SQL> alter diskgroup reco_q1 add disk 'o/192.168.9.9/RECO_Q1_CD_03_edx2cel01' rebalance power 10;

Repeat the prior queries to validate the rebalance has started and there are no longer any disks with "group_number" values of 0.

5. If the disk replaced was a system disk in slot 0 or 1, then the status of the OS volume should also be checked. Login as 'root' on the Storage cell and check the status using the same 'df' and 'mdadm' commands listed above:

[root@dbm1cel1 ~]# mdadm -Q --detail /dev/md5
/dev/md5:
        Version : 0.90
Creation Time : Thu Mar 17 23:19:42 2011
     Raid Level : raid1
...
    Update Time : Wed Jul 18 11:56:36 2012
          State : active, degraded
Active Devices : 1
Working Devices : 2
Failed Devices : 1
Spare Devices : 1

           UUID : e75c1b6a:64cce9e4:924527db:b6e45d21
         Events : 0.215

    Number   Major   Minor   RaidDevice State
       3      65      213        0      spare rebuilding   /dev/sdad5
       1       8       21        1      active sync   /dev/sdb5

       2       8        5        -      faulty spare

[root@dbm1cel1 ~]#

While the system disk is rebuilding, the state will show as "active, degraded" or "active,degraded,recovering" with one indicating it is rebuilding and the 3rd being the 'faulty' disk. After rebuild has started, re-running this command will give a "Rebuild Status: X% complete" line in the output. When the system disk sync status is complete, the state should return to "clean" only with 2 devices. If an extra entry (faulty spare) is seen, this can be ignored - refer to Doc ID 2031054.1 for details.

If the status of any of the above checks (firmware, grid disk / cell disk creation, rebalance) is not successful, re-engage Oracle Support to get the correct action plan to manually complete the required steps.

PARTS NOTE:

Refer to the Exadata Database Machine Maintenance Guide for part information. https://docs.oracle.com/cd/E80920_01/DBMMN/toc.htm

How to identify which Exadata disk FRU part number to order , based on image and vendor and mixed disk support status - Note 1416303.1 and Oracle System Handbook.

REFERENCE INFORMATION:

HALRT-02004: Data hard disk predictive failure (Doc ID 1112995.1)
Exadata Database Machine Documentation:
- Exadata Database Machine Maintenance Guide is available on the Storage Server OS image in /opt/oracle/cell/doc/welcome.html or online here:
  https://docs.oracle.com/cd/E80920_01/DBMMN/toc.htm
Sun Fire X4170, X4270, and X4275 Servers Service Manual (Servicing Customer-Replaceable Devices) https://docs.oracle.com/cd/E19477-01/820-5830-13/hotswap.html#50634786_83028
Sun Fire X4270 M2 Server Product Library Documentation (includes Sun Fire X4270 M2 Server Service Manual) https://docs.oracle.com/cd/E19245-01/index.html
Sun Server X3-2L Documentation Library https://docs.oracle.com/cd/E23393_01/index.html
Sun Server X4-2L Documentation Library https://docs.oracle.com/cd/E36974_01/index.html
Oracle Server X5-2L Documentation Library https://docs.oracle.com/cd/E41033_01/html/E48325/index.html
Oracle Server X6-2L Documentation Library https://docs.oracle.com/cd/E62172_01/html/E62184/index.html
Oracle Server X7-2L Documentation Library https://docs.oracle.com/cd/E72463_01/html/E72479/index.html

Replacing an Oracle Exadata System disk drive (Doc ID 1088475.1)
Replacing an Oracle Exadata V2 Data disk drive (Doc ID 1087742.1)
Mirror partitions not resynched after replacing failed system drive (lun 0 or 1) (Doc ID 1316829.1)
Replacing a physicaldisk on a storage cell , cellcli list physicaldisk reports two entries on same slot but LUN is not created (Doc ID 1352938.1)
INTERNAL Exadata Database Machine Hardware Current Product Issues (V2, X2-2, X2-8) (Doc ID 1360343.1)
INTERNAL Exadata Database Machine Hardware Troubleshooting (Doc 1360360.1)

References

<NOTE:1112995.1> - HALRT-02004: Data hard disk predictive failure
<NOTE:1524329.1> - Root Volume of Predictive Failure Boot Hard Drive in an Exadata Storage Server Remains in State of 'active'
<NOTE:2199949.1> - (EX32) V2 and X2 Storage Servers with 600GB High Performance Disks Running Exadata Version 11.2.2.4.0 or Lower Require Software Update to Receive Replacement Drives
<NOTE:1386147.1> - How to Replace a Hard Drive in an Exadata Storage Server (Hard Failure)
<NOTE:1326611.1> - Things to Check in ASM When Replacing an ONLINE disk from Exadata Storage Cell
<NOTE:1113013.1> - HALRT-02003: Data hard disk failure
<NOTE:1071220.1> - Oracle Sun Database Machine V2 Diagnosability and Troubleshooting Best Practices
<NOTE:1274324.1> - Oracle Exadata Database Machine Diagnosability and Troubleshooting Best Practices
<NOTE:1509105.1> - Identification of Underperforming Disks feature in Exadata
<NOTE:1281395.1> - Steps to manually create cell/grid disks on Exadata if auto-create fails during disk replacement
<NOTE:1664262.1> - EXADATA: What Is Drop Hard Disk For Replacement Feature ? ("ALTER PHYSICALDISK DROP FOR REPLACEMENT". )
<NOTE:2352138.1> - Storage servers with 8TB high capacity disks running Exadata older 12.2 or 12.1 versions require software update to receive newer model replacement drives
<NOTE:2376948.1> - Support Strategy for Replacing a 8TB HDD in SPARC Based Systems

Attachments

This solution has no attachment