Backup and Recovery - Oracle Exadata Recipes: A Problem-Solution Approach - page 202

GMON updating disk modes for group 3 at 14 for pid 30, osid 8507
NOTE: PST update grp = 3 completed successfully
NOTE: initiating PST update: grp = 3, dsk = 35/0xec5ff760, mode = 0x7e, op = 4
GMON updating disk modes for group 3 at 15 for pid 30, osid 8507
NOTE: cache closing disk 35 of grp 3: RECO_CD_05_CM01CEL01
NOTE: PST update grp = 3 completed successfully
NOTE: process _user8507_+asm1 (8507) initiating offline of disk 33.3965712156
(DATA_CD_05_CM01CEL01) with mask 0x7e in group 1
NOTE: checking PST: grp = 1
GMON checking disk modes for group 1 at 16 for pid 30, osid 8507
NOTE: checking PST for grp 1 done.
WARNING: Disk 33 (DATA_CD_05_CM01CEL01) in group 1 mode 0x7f is now being offlined
WARNING: Disk 33 (DATA_CD_05_CM01CEL01) in group 1 in mode 0x7f is now being taken offline on
ASM inst 1
... output omitted for brevity
WARNING: Disk 33 (DATA_CD_05_CM01CEL01) in group 1 will be dropped in: (12960) secs on ASM inst 1
WARNING: Disk 35 (RECO_CD_05_CM01CEL01) in group 3 will be dropped in: (12960) secs on ASM inst 1

As you can see, your Oracle ASM instance will automatically offline the failed disks from the appropriate ASM
disk group.
Now it's time to replace your failed disk drive. If you have a spare drive in your Exadata spares kit, you can use this
as your replacement and replenish your spare via your Service Request. If you require an Oracle Support hardware
engineer to bring a new disk drive to your data center because you do not have an available spare, you must wait for
the drive to arrive.

■ We recommend using one of your spares to replace failed disks once oracle Support confirms that the disk
drive is indeed in a failed state. It is worth mentioning, however, that some types of drive failures are transient in nature
and can be resolved simply by reseating the disk drive. you can do this by simply pressing the release button on the failed
drive, removing it, and inserting it back into its slot. In some cases, this will correct transient errors; if it does, the server
will automatically sense the correction and set the status back to normal .

Note

When you have a replacement drive in hand, simply remove the failed disk drive by depressing the release button
and insert the replacement drive. You should be able to identify the failed drive based on a blinking amber LED on the
left side of the disk drive; if you do not see a blinking light, log in as root to the storage server and run the following
MegaCli64 command to turn the service LED on:

[root@cm01cel01 ~]# /opt/MegaRAID/MegaCli/MegaCli64 -pdlocate -physdrv \[20:5\] -a0
Adapter: 0: Device at EnclId-20 SlotId-5 -- PD Locate Start Command was successfully sent to
Firmware
Exit Code: 0x00
[root@cm01cel01 ~]#

Note that you can turn off the service light by using the following command:

[root@cm01cel01 ~]# /opt/MegaRAID/MegaCli/MegaCli64 -pdlocate -stop -physdrv \[20:5\] -a0
Adapter: 0: Device at EnclId-20 SlotId-5 -- PD Locate Stop Command was successfully sent to
Firmware
Exit Code: 0x00
[root@cm01cel01 ~]#