Scenario 1: Simple Disk Failure and Spare Disk Rebuild

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. The notification generated for the failed Disk and the Spare Disk are listed in Notifications for Failed Disk and Spare Disk.

Table 1. Notifications for Failed Disk and Spare Disk

Disk	Notifications
Disk 0_0_1	DiskFault (Event)
	Down (Problem)
Disk 0_0_24	DiskRebuildEvent (Event)
	DiskRebuild (Problem)

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

Table 2. Root-cause analysis and impact of Disk Down

Root-Cause problem	Event or symptom of Root-Cause problem	Impacted Class
Down	DiskFault	PhysicalDisk
	Degraded	RAIDGroup
	PerformanceMightBeImpaired	VirtualMachine
	VMHighDiskLatency	VirtualMachine
	DiskRebuildEvent	SparePhysicalDisk

1. Rebuild on Spare Disk 0_0_24 is complete:

   • The DiskRebuildEvent and DiskRebuild events are cleared.

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

     • The DiskFault event and Down problem still remains for Disk 0_0_1.