IBM Storage Scale System 6000 Service Manual page 23

Important: If the faulty drive is an IBM FlashCore Module 4 (FCM 4), before you can proceed to
replace and prepare all the NVMe drives, an additional subprocedure is required to trigger and collect
the drive data export.
First, confirm that the IBM Storage Scale System 6000 has FCM 4 drives by running the
tslsenclslot_nvme | grep -i NVMe command.
In the next example output of the tslsenclslot_nvme command, all drives show FCM4 NMVe G4.
[root@lothal-qa2-1 ~]# tslsenclslot_nvme | grep NVMe
/dev/nvme4n1 03NK361YS10BG31G006 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme5n1 03JN353YS35BG29V00K 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme6n1 03JN353YS10BG31G03K 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme7n1 03JN353YS34BG27T006 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme8n1 03JN353YS34BG27T00A 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme9n1 03JN353YS35BG29V008 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme0n1 03JN353YS10BG31G02N 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme2n1 03JN353YS34BG27T00D 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme1n1 03JN353YS34BG27T00K 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme11n1 03JN353YS35BG29V00J 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme12n1 03JN353YS10BG31G03C 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_7
/dev/nvme13n1 03JN353YS34BG27T001 19.2 TBu FCM4 NVMe G4
TB 4 KiB + 0 B 4_1_4
If you get an output that is similar to the one highlighted in the previous example, follow the steps of
the "Preparing an FCM 4 drive for service" on page 17 subprocedure before you continue through the
rest of this service procedure.
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 Storage
Scale System: Problem Determination Guide.
• Option 2. Removing a drive by using CLI commands.
If one or more physical disks 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 s6k_lothal_qa6_1_hs_lothal_qa6_2_hs recovery group
needs service:
# mmvdisk recoverygroup list
recovery group
current or master server
-----------------------------------
-----------------------------------
s6k_lothal_qa6_1_hs_lothal_qa6_2_hs
lothal-qa6-2-hs.tms.stglabs.ibm.com
Service is needed when the number of faulty physical disks 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:
78L0001-2 V1-gems!5149F48-5000C5FAB30EE000-1
78L0001-4 V1-gems!5149F48-5000C5FAB30EE000-3
78L0001-6 V1-gems!5149F48-5000C5FAB30EE000-5
78L0001-8 V1-gems!5149F48-5000C5FAB30EE000-7
78L0001-10 V1-gems!5149F48-5000C5FAB30EE000-9
78L0001-12 V1-gems!5149F48-5000C5FAB30EE000-11
78L0001-14 V1-gems!5149F48-5000C5FAB30EE000-13
78L0001-16 V1-gems!5149F48-5000C5FAB30EE000-15
78L0001-18 V1-gems!5149F48-5000C5FAB30EE000-17
78L0001-20 V1-gems!5149F48-5000C5FAB30EE000-19
78L0001-22 V1-gems!5149F48-5000C5FAB30EE000-21
78L0001-24 V1-gems!5149F48-5000C5FAB30EE000-23
needs user
node class
service
-----------------------------------
s6k_lothal_qa6_1_hs_lothal_qa6_2_hs
yes
1
1
1
1
1
1
1
1
1
1
1
1
vdisks remarks
8
Chapter 1. Servicing (customer tasks) 11
23.11 TB / 57.60
23.08 TB / 57.60
23.12 TB / 57.60
23.09 TB / 57.60
23.10 TB / 57.60
23.13 TB / 57.60
23.02 TB / 57.60
23.09 TB / 57.60
23.12 TB / 57.60
23.11 TB / 57.60
23.03 TB / 57.60
16.02 TB / 57.60
active
-------
yes