Troubleshooting hot spare device parity protection
Identify some common conditions associated with hot spare device parity protection and failed drives.
- If you are having trouble starting hot spare or starting device parity protection with hot spare protection, verify the following:
- There is an adequate number of disk units attached to the desired IOA which could become hot spare disk units.
- The disk units to become hot spares are in Non-configured status (not part of an disk pool).
- The disk units to become hot spares are of appropriate size to protect the disk units in the parity sets under the desired IOA.
- If the desired IOA is the load source IOA, the disk units to become hot spares must be installed in a valid load source location for the specific enclosure.
If the option to start device parity protection with hot spare protection is selected and the above requirements are not met, the desired IOA will not be shown as capable of starting device parity protection.
If the option to start hot spare protection is selected and the above requirements are not met, the desired disk units will not be shown as capable of becoming hot spares.
- If you are trying to identify a failed disk unit which was automatically replaced by a hot spare, or if the hot spare disk unit itself has failed, see the following:
When a device parity protected disk unit fails and the automatic rebuild to the hot spare has started or completed, the failed disk will have a status of Not operational or Read/Write protected. Follow normal disk unit service and recovery procedures for replacement of the failed disk unit.
When a hot spare disk unit fails, the failed disk will have a status of Not operational or Read/Write protected. Follow normal disk unit service and recovery procedures for replacement of the failed disk unit.
Parent topic:
Using hot spare device parity protectionRelated concepts
Device parity protection with hot spare disk units concepts