March
2
V7000: "Ghost" drive repair
There seems to be a bug in 6.2 and 6.3 of IBM’s V7000 code that when replacing a bad drive, the V7000 is not properly deleting the bad drive information from the system.
The end result is that you have a drive that shows up in the list,but you cannot do anything to it in the GUI.
Repair procedure:
Login through the CLI
If repairing drive ID 33 enter the following:
1) svctask chdrive -use failed 33
2) svctask chdrive -use unused 33
The GUI will need refreshed to reflect the changes properly. You may need to log out then back in.