File system error or corruption

Monitor Name : File system error or corruption
Description      : Monitors whether the file system has reported an error with the file system or corruption on the logical disk.
Monitor Target:Windows Server 2008 Logical Disk

Summary

NTFS has reported that the logical disk is either corrupted or completely unavailable. Some data stored on the volume may be inaccessible.

Causes

A logical disk may become corrupted or inaccessible due to a number of reasons some of which include:

•	A physical disk related to the logical disk has been removed or failed
•	A physical disk related to the logical disk has become corrupt (for example; bad sectors) or inoperable
•	The disk driver may've encountered an issue

Resolutions

Check the status of your hardware for any failures (for example, a disk, controller, cabling failure). In most cases, the system log contains additional events from the lower-level storage drivers that indicate the cause of the failure.
After you have isolated and resolved the hardware problem:
1. Open the Disk Management snap-in.
2. Rescan the disks and then reactivate any disks with errors.
Resynchronize or regenerate the volume as necessary if the disk was a member of a mirrored or RAID-5 volume.
3. Run chkdsk on any reactivated volumes.

You check this yourself:

1. Run\Open WBEMTEST
2. Connect... root\CIMV2
3. Select Query..., and paste in:  “select * from Win32_LogicalDisk where (DriveType=3 or DriveType=6) and FileSystem != null” Apply
4. Whichever drive letter is red : select that one by double click.
5. On the right side – click Show MOF
6. Scroll all the way down in the list to “VolumeDirty”

If VolumeDirty = TRUE, then this monitor will be “BAD”.

What this means is – at some point this volume got a NTFS error, or was removed from the OS in a critical manner.  It *requires* a Chdksk /f to be run against this volume to restore VolumeDirty to a FALSE condition.

So – if you see these – you can double check this by running the simple WMI query… and then just schedule a Chkdsk on the volume during the next available maintenance window.