Physical disk procedures
This topic describes the various procedures that you can perform for the maintenance of disks.
- Identify the problem disks. Use the following command to check the current disks that have a
problem:
# mmvdisk pdisk list --rg all --not-okdeclustered recovery group pdisk array paths capacity free space FRU (type) state -------------- ------------ ----------- ----- -------- ---------- --------------- ----- rg_1 n002p001 DA1 0 894 GiB 890 GiB PX04PMB096 missing/drained rg_1 n005p002 DA1 0 894 GiB 890 GiB PX04PMB096 failing/replaceNote: If you find the state of a disk as "missing", it usually does not mean that there is a problem with the disk drive. Therefore, the "missing" state might be because of a disk connection problem or a network problem of the node, and you need to find the root cause of the problem. For example, to re-seat the drive or bring back the node. If the missing disk is confirmed of drive hardware failure after checking the system, the disk can be replaced by completing step 2 after it is drained. - Perform the following steps to replace disks:
- To identify the pdisk to be replaced within all recovery
groups:
The system displays the following output:mmvdisk pdisk list --rg all --replacerecovery group pdisk priority FRU (type) location -------------- ------------ -------- --------------- -------- rg_1 n005p003 12.95 00YK014 Enclosure J1005744 Drive 6 rg_1 n005p004 12.95 00YK014 Enclosure J1005744 Drive 7 mmvdisk: A lower priority value means a higher need for replacement.Note:- If you replace a pdisk not on this list, you risk data loss.
- If the number of disks need replacement is below the replacement threshold for its member declustered array, then those disks will not generate call home behavior.
- It is recommended to set your replacement threshold to 1 if you want call home happening as earlier as possible when you have only one disk failing.
- To set your replacement threshold to
1:
mmvdisk rg change --rg RgName --da DaName --replace-threshold 1 - To replace hot swappable disk devices:
- Issue the following
command:
mmvdisk pdisk replace --prepare --recovery-group RgName --pdisk PdiskNameThe system displays an output as follows:mmvdisk: Suspending pdisk n005p003 of RG rg_1 in location J1005744-6. mmvdisk: Location J1005744-6 is Enclosure J1005744 Drive 6. mmvdisk: Carrier released. mmvdisk: mmvdisk: - Remove carrier. mmvdisk: - Replace disk in location J1005744-6 with type '00YK014'. mmvdisk: - Reinsert carrier. mmvdisk: - Issue the following command: mmvdisk: mmvdisk: mmvdisk pdisk replace --recovery-group rg_1 --pdisk 'n005p003' - Go to the node to replace a new disk for the
pdiskaccording to the slot location. - Issue the following
command:
mmvdisk pdisk replace --recovery-group RgName --pdisk PdiskNameThe system displays an output as follows:mmvdisk: mmvdisk: mmchcarrier : [I] Preparing a new pdisk for use may take many minutes. mmvdisk: mmvdisk: The following pdisks will be formatted on node HostName: mmvdisk: // HostName /dev/DevName mmvdisk: Pdisk PdiskName of RG RgName successfully replaced. mmvdisk: Resuming pdisk PdiskName#nnn of RG RgName. mmvdisk: Carrier resumed.
Note: After you replace a new pdisk in the slot, ensure to check and disable the volatile write cache on the new pdisk. For more information, see Volatile write cache detection. - Issue the following
command:
- To identify the pdisk to be replaced within all recovery
groups: