IBM Elastic Storage System 3500 Service Manual page 13

Figure 4. Displaying physical disks state
You can also select the Display unhealthy devices option in the Display unhealthy devices >
Hardware Details page to see all the unhealthy devices with the faulty disks.
2. Prepare the failed drive for replacement.
In an IBM Elastic Storage System 3500 enclosure, a faulty drive has amber fault LED ON (non-flashing)
on the driver carrier. At the end of this step, confirm that the amber LED in the ON state for the drive to
be removed.
a) Identify drives for removal with the help one of the following two options:
• Option 1. Removing a drive by using the management GUI.
To replace disks by using the management GUI, follow the direct maintenance procedure (DMP)
that is available in the Maintenance procedures chapter, section Replace disks in the IBM Elastic
Storage System: Problem Determination Guide.
• Option 2. Removing a drive by using CLI commands.
If one or more pdisks in the recovery group are marked for replacement, the following command
reports it with a yes in the "needs service" column:
mmvdisk recoverygroup list
In the following example, the BB01L recovery group needs service:
# mmvdisk recoverygroup list
recovery group
--------------
BB01L
BB01R
It happens when the number of failed pdisks in one of the recovery group's declustered arrays
reaches or exceeds the replacement threshold for the declustered array.
The following command lists disks with the threshold for replacement:
mmvdisk pdisk list --recovery-group {all | RgName[,RgName]} --replace
# mmvdisk pdisk list --recovery-group all --replace
recovery group
--------------
active current or master server
------- --------------------------------
yes server01.gpfs.net
yes server02.gpfs.net
pdisk priority
------------ --------
needs
service
-------
yes
no
FRU (type) location
--------------- --------
Chapter 1. Servicing (customer tasks) 3
user
vdisks remarks
------ -------
3
3