This rule monitors virtual hard disks (VHD) that cannot be initialized for the iSCSI Target service. When this occurs, VHDs will be unavailable to any iSCSI Target that uses the VHD.
An alert will be generated for every VHD that cannot be initialized. The alert description will contain the device ID and local path to the VHD that has failed. Only a single alert will be generated per unique VHD that exhibits a problem.
A VHD can fail to initialize for a number of reasons such as:
The VHD file has been moved, deleted or renamed
The underlying storage hosting the VHD is unavailable
The file is in use by another application
Multiple VHDs may be affected and you should review additional alerts which have been generated for the iSCSI Target service.
On the Windows Server computer hosting the iSCSI Target service, ensure the VHD file that is referred to in the alert is present and available.
If the file was unavailable when the iSCSI Target service started, and is now available, the iSCSI Target service must be restarted. Note that this can cause an interruption in iSCSI target services to iSCSI initiators while the service is restarted.
To restart the iSCSI Target service, use the following steps:
On the affected server, run an elevated command prompt
Type net stop wintarget and then press ENTER
Once the service has stopped, type net start wintarget and then press ENTER
Open the Microsoft iSCSI Software Target MMC snap-in
In the left pane, locate Devices and verify the VHDs are now available.
You must manually resolve alerts after the issues have been resolved.