storage:v7k_replace_disk
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
storage:v7k_replace_disk [2024/08/26 22:02] manu [Procedure 1] |
storage:v7k_replace_disk [2024/08/26 22:03] (current) manu |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| * Mark the drive that requires a reseat as failed (even if this drive is already in 'failed' state) via **chdrive -use failed 6** (NOTE: check that there is sufficient redundancy in the array before doing this). | * Mark the drive that requires a reseat as failed (even if this drive is already in 'failed' state) via **chdrive -use failed 6** (NOTE: check that there is sufficient redundancy in the array before doing this). | ||
| | | ||
| - | Mark the failed drive as unused via the GUI or via **chdrive -use unused 6**. This logically removes the drive from the array and means it will not automatically add back in after being reseated. | + | * Mark the failed drive as unused via the GUI or via **chdrive -use unused 6**. This logically removes the drive from the array and means it will not automatically add back in after being reseated. |
| | | ||
| - | Re-seat the drive, or perform a virtual power cycle of the drive slot by running the command **chenclosureslot -slot 2 -power cycle 1**. Wait until the drive is online (can take up to 5 minutes) | + | * Re-seat the drive, or perform a virtual power cycle of the drive slot by running the command **chenclosureslot -slot 2 -power cycle 1**. Wait until the drive is online (can take up to 5 minutes) |
| | | ||
| - | If the drive comes back as 1674 "Drive offline because it is locked by a missing encryption key", secure erase this drive via GUI or CLI **chdrive -task erase 6**. Wait until the drive is online (can take up to 5 minutes) | + | * If the drive comes back as 1674 "Drive offline because it is locked by a missing encryption key", secure erase this drive via GUI or CLI **chdrive -task erase 6**. Wait until the drive is online (can take up to 5 minutes) |
| | | ||
| - | Trigger at least two drive dump after the power cycle with **triggerdrivedump 6**. This will ensure that older data are de-staged from the FCM internal memory and newer data could follow in the next drivedump. | + | * Trigger at least two drive dump after the power cycle with **triggerdrivedump 6**. This will ensure that older data are de-staged from the FCM internal memory and newer data could follow in the next drivedump. |
| | | ||
| - | Upload a SNAP option 1 (this will also include the drivedump) for IBM support review | + | * Upload a SNAP option 1 (this will also include the drivedump) for IBM support review. Wait until we completed the drivedump analysis before integrating the drive back in the array. |
| - | Wait until we completed the drivedump analysis before integrating the drive back in the array. | + | |
| | | ||
| ===== Procedure 2 ===== | ===== Procedure 2 ===== | ||
storage/v7k_replace_disk.1724702560.txt.gz · Last modified: 2024/08/26 22:02 by manu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
