Note |
Ensure that the data is backed up. |
This happens when the Intel RAID Controller lost access (permanent or temporary) to one or more drives belonging to a RAID array. Possible reasons are surprise removal followed by re-insertion of the same drive, bad or loose cable, bad or failing drive, and so on. If the access is lost only temporarily, the drive may become Unconfigured Bad (UB).
It is important to understand and identify the cause to determine the appropriate action. For example, if a drive became UB due to surprise removal or bad cable and the drive is known to be good, it is safe to continue using the same drive by making it Unconfigured Good (UG) and put it back to the array for rebuild. However, if the drive is failing (still functional but fails intermittently), it should be replaced with a new drive and not to continue using it as it's likely going to fail again soon.
An effective way to identify the possible cause is by looking at the event histories from the RAID log or Intel® RAID Web Console utility.
Other possible troubleshooting methods that may require additional hardware/system for testing:
After the cause or failing part is determined
For bad or failing drive:
For non-drive–related causes:
Note |
The time required for the rebuild largely depends on the size of the VD. |
If uncertain, contact Intel Customer Support for assistance.