If Chkdsk has been started automatically, we recommend that you allow it to run so that it can correct any problems with the file system. Chkdsk output will be logged to the <systemroot>\Cluster\Reports folder. Note that file-system errors might indicate that the hardware is deteriorating. For information about other ways of gathering information about a clustered disk that appears to have file system errors, see "Using logs and the clustering validation wizard to gather information about the state of a clustered disk" and "Running a disk maintenance tool such as Chkdsk on a clustered disk."
To view or change the current setting for the triggers for running Chkdsk on a clustered disk, see "Viewing or changing the setting for the triggers that cause Chkdsk to run on a clustered disk," later in this topic.
If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering."
To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
To use logs and the clustering validation wizard to gather information about the state of a clustered disk:
Important If a clustered service or application is using a disk when you start the wizard, the wizard will prompt you about whether to take that clustered service or application offline for the purposes of testing. If you choose to take a clustered service or application offline, it will remain offline until the tests finish.
If you need to run a disk maintenance tool such as Chkdsk on a clustered disk, use maintanence mode to prevent the disk maintenance tool from triggering failover.
To run a disk maintenance tool such as Chkdsk on a clustered disk:
When maintenance mode is on, the disk remains online in the cluster, but the disk maintenance tool can finish running without triggering a failover.
Disk resources in a cluster have a private property setting called DiskRunChkDsk that specifies the triggers that will cause Chkdsk to run on the disk.
To view or change the setting for the triggers that cause Chkdsk to run on a clustered disk:
CLUSTER RESOURCE /STATUS
CLUSTER RESOURCE "DiskResourceName" /PRIV
CLUSTER RESOURCE "DiskResourceName" /PRIV DISKRUNCHKDSK=n
CLUSTER RESOURCE "DiskResourceName" /PRIV
To open Event Viewer and view events related to failover clustering:
Target | Microsoft.Windows.2008.Cluster.Monitoring.Service | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.2008.Cluster.EventProvider | Default |
WA | WriteAction | Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription | Default |
<Rule ID="Microsoft.Windows.2008.Cluster.Management.Monitoring.One.or.more.cluster.disk.volumes.may.be.corrupt" Enabled="true" Target="Clus2008Library!Microsoft.Windows.2008.Cluster.Monitoring.Service" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.2008.Cluster.EventProvider">
<Criteria>
<RegExExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesRegularExpression</Operator>
<Pattern>^(1066|1037)$</Pattern>
</RegExExpression>
</Criteria>
<LogName>System</LogName>
<PublisherName>Microsoft-Windows-FailoverClustering</PublisherName>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="ClusLibrary!Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.2008.Cluster.Management.Monitoring.One.or.more.cluster.disk.volumes.may.be.corrupt.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>