Symptom:
The customer is using RAID 6 and experienced the failure of two drives. Even after the rebuild process is reported as complete, the Logical Drive (LD) remains in degraded mode.
Example logs:
- Information: 0x020A8304 LD:16E1D82C Logical drive rebuild started
- Information: 0x020A8402 LD:16E1D82C Logical drive rebuild completed
Diagnosis:
This issue can occur if the ‘rebuild’ function was used instead of the ‘add drive’ function after replacing a failed drive. In this example, two failed drives were added back to the LD, but only one global spare drive was used to rebuild it. As a result, the LD was only rebuilt with one drive, leaving the other failed drive unrepaired, which causes the LD to remain in degraded mode.
Example errors:
- Error: Pool: vol (ID: 475DAFA139C7F8A2) LD: Logical_drive_1 (ID: 16E1D82C) Enclosure Slot: 2 The first LD member drive failed.
- Error: Pool: vol (ID: 475DAFA139C7F8A2) LD: Logical_drive_1 (ID: 16E1D82C) Enclosure Slot: 3 The second LD member drive failed.
- Information: 0x020A8908 LD:16E1D82C Logical drive add drive action started
- Information: 0x020A8A08 LD:16E1D82C Logical drive add drive completed
Solution:
Prepare a new drive, assign it as a global spare drive, and rebuild the LD again to repair the remaining failed drive.
Conclusion:
When encountering a scenario where the rebuild process is complete but the LD remains in degraded mode, ensure that all failed drives are properly replaced and accounted for during the rebuild process. Assigning an additional global spare drive and performing another rebuild should resolve the issue.