Message that an error occurred during volume onlineĮvent ID 80: A failure occurred during the check of volume. Message that volume is dirty and needs to be checked Running chkdsk again checks and should repair any remaining corruption on the volume. The following messages will be logged in the Application Event log:Įvent ID 101: Checking the dirty flag on volume However, canceling or interrupting chkdsk should not leave the volume any more corrupt than it was before chkdsk was run. Please refer to the Microsoft blog on this specific issue It is highly recommended to change the flag on all nodes in such circumstances. Large volumes may take a long time to complete the check therefore, it is recommended that the chkdsk be done during planned maintenance by setting the flag to 0 for each DataKeeper volume. Running chkdsk before a volume is brought online is recommended to ensure that the volume is healthy. The complete list of values are numeric and are documented in the Microsoft article (v=vs.85).aspx The location of this flag is in HKEY_LOCAL_MACHINE/Cluster/Resources//Parameters.

The volume command performed depends on the argument located in the DiskRunChkDsk flag for each DataKeeper volume. The flag determines how chkdsk runs on each volume during disk check operations.įlag value 0 means chkdsk is enabled and the entire volume will be checkedįlag value 4 means chkdsk is skipped for the entire volume

DataKeeper now creates a new flag DiskRunChkDsk in Windows Failover Clustering for each DataKeeper volume.

Running chkdsk on Cluster Volumes during Cluster Volume OnlineĪs of version 7.6 DataKeeper now runs chkdsk on all mirrored volumes prior to the volume being available for use.