Replacing an NVMe disk
Follow the instructions to replace an NVMe disk.
About this task
Procedure
What to do next
- Ensure that the error event of a bad disk disappears from the Events page.
- Ensure that the new disk shows up with the different serial number in the Physical Disks page.
- Check the file system mount and physical disks in a core scale pod.
- Run the OC command to check Scale core pod.
oc get pod NAME READY STATUS RESTARTS AGE compute-0 2/2 Running 0 17d compute-1 2/2 Running 0 17d compute-2 2/2 Running 0 17d control-0 2/2 Running 0 17d control-1 2/2 Running 0 17d control-2 2/2 Running 0 17d
- Run the OC command to see all the containers in this pod.
oc describe pod/compute-2 -n ibm-spectrum-scale
- Run the following command to check the file system
mount.
mmlsmount all
- Run the following commands to check the current physical disks health.
mmvdisk pdisk list --rg all --not-ok mmvdisk: All pdisks are ok.
mmlsrecoverygroup rg1 -L --pdisk declustered current allowable recovery group arrays vdisks pdisks format version format version ----------------- ----------- ------ ------ -------------- -------------- rg1 1 25 12 5.1.5.0 5.1.5.0 declustered needs replace scrub background activity array service vdisks pdisks spares threshold BER trim free space duration task progress priority ----------- ------- ------ ------ ------ --------- ------- ---- ---------- -------- ------------------------- DA1 no 25 12 1,3 1 enable no 326 GiB 14 days rebalance 2% low n. active, declustered state, pdisk total paths array free space remarks ----------------- ----------- ----------- ---------- ------- n001p001 1, 1 DA1 212 GiB ok n001p002 1, 1 DA1 208 GiB ok n002p001 1, 1 DA1 300 GiB ok n002p002 1, 1 DA1 252 GiB ok n003p001 1, 1 DA1 236 GiB ok n003p002 1, 1 DA1 234 GiB ok n004p001 1, 1 DA1 4552 GiB ok n004p002 1, 1 DA1 512 GiB ok n005p001 1, 1 DA1 232 GiB ok n005p002 1, 1 DA1 266 GiB ok n006p001 1, 1 DA1 250 GiB ok n006p002 1, 1 DA1 222 GiB ok
- Run the OC command to check Scale core pod.