Scenario 2: Disk Failure, Spare Disk Rebuild and Replacement of Failed Disk

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. If Disk 0_0_1 fails, then rebuild on the spare Disk 0_0_24 begins. Root-cause and impact analysis explains the root-cause and impact of the Down problem in Disk 0_0_1.

2. Rebuild on Spare Disk 0_0_24 is complete. Notifications statuses:

   • The DiskRebuildEvent and DiskRebuild problem are cleared.

     • RaidGroup::Degraded and VirtualMachine::PerformanceMightBeImpacted events are cleared.

     • For Disk 0_0_1, the DiskFault event and Down problem remains.

3. The failed drive 0_0_1 is replaced.

4. Triggers rebuild of Disk 0_0_1.

5. The following notifications are generated for Disk 0_0_1:

   • DiskRebuildEvent

     • DiskRebuild

       Note:

       DiskFault event is not generated.

6. Root-cause and impact analysis — Root-cause and impact analysis of DiskRebuild problem in Disk 0_0_1 explains the root-cause and impact of the DiskRebuild problem. The VMHighDiskLatency event is generated if the corresponding VM alarm is configured in the vCenter.

Table 1. Root-cause and impact analysis of DiskRebuild problem in Disk 0_0_1

Root-Cause problem	Event	Impacted class
DiskRebuild	DiskRebuildEvent	PhysicalDisk
	Degraded	RAIDGroup
	PerformanceMightBeImpacted	VirtualMachine
	VMHighDiskLatency	VirtualMachine

1. Once the rebuild on Disk 0_0_1 is complete, all notifications are cleared.