In a storage array if a Disk fails, then Disk Rebuild starts on the Spare Disk.

Let the primary Disk be 0_0_1 and the Spare Disk be 0_0_24.

Workflow

  1. When Disk 0_0_1 fails, then rebuild on the spare Disk 0_0_24 begins. GUID-74496129-427B-4057-9D83-ECD51259D12F.html#GUID-74496129-427B-4057-9D83-ECD51259D12F___EISM_APPDX_DISK_REBUILD_96241 lists the notifications that are generated for the failed Disk and the Spare Disk. Root-cause and impact analysis — GUID-74496129-427B-4057-9D83-ECD51259D12F.html#GUID-74496129-427B-4057-9D83-ECD51259D12F___EISM_APPDX_DISK_REBUILD_39329 explains the root-cause and impact of the Down problem in Disk 0_0_1.

  2. The failed Disk 0_0_1 is fixed and replaced before the completion of rebuild on the Spare Disk 0_0_24. The rebuild on Spare Disk 0_0_24 continues till rebuild is complete.

  3. Notifications statuses:

    • DiskFault event and Down problem for Disk 0_0_1 are cleared.

      • DiskRebuildEvent and DiskRebuild are generated for Spare Disk 0_0_24 and remain till rebuild is complete.

  4. Disk Rebuild on Disk 0_0_1 starts only after the completion of Disk Rebuild on Spare Disk 0_0_24.

  5. The notifications DiskRebuildEvent and DiskRebuild are generated for Disk 0_0_1. GUID-74496129-427B-4057-9D83-ECD51259D12F.html#GUID-74496129-427B-4057-9D83-ECD51259D12F___EISM_APPDX_DISK_REBUILD_48061 explains the root-cause and impact of the DiskRebuild problem for Disk 0_0_1.

  6. When Disk Rebuild on Disk 0_0_1 is complete, all notifications are cleared.