V7000 Drive Replacement Issue
talor 27000411MV Comments (12) Visits (40244)
Typically when a disk fails in a V7000, you just go into events, and follow the procedure to replace the disk and the drive is re-build automatically.
I have done this before without issue, on firmware older than 6.4, however possibly this is a 6.4 code issue.
Today we had an issue where a disk failed, but when we looked in events we could see that a spare disk was in use, however we had no procedure to replace the failed drive.
Under the internal storage tab, the drive was offline.
Work out what drive is offline, in the internal storage tab. Identify the drive. Take out the failed disk, and insert the new disk. Make sure you pick the disk that has the amber light on it!
When you return to the Internal storage tab in the GUI, the drive will still be offline and failed. Right click the drive, and mark it as "unused". Right click the same drive again and mark as candidate. Right click the drive again, and mark it as a spare.
The array (mdisk) will start to rebuild, and the health of the stroage will go back to green, healthy. Some time later you will get an alert ath the array mdisk has rebuilt, and the original spare that was used is a spare again.
You can also do this on the command line.
- Check the ID of the failed disk:
For this example lets say that the drive number is 35.
- Mark the disk as unused / candidate / spar
It would always be best to do this under the guidance of IBM Support. This is just a handy thing to know as we hit this issue today.