VolumeDirty flag is NTFS flag, is set by ntfs.sys driver on your drive(not in registry, not in wmi repository, directly on the drive in $MFT file). No other way to clear it but running chrdsk /f /r there is of course unsupported way to set this bit to false using direct NTFS structure editing. You can do this via dskprobe from support tools. ps. you can also query this bit by running "fsutil dirty query C:"

Ive read up on some posts here and it has helped me figure out why this is happening. If anyone has pointers on the next move I would appreciate it. We replaced a large data volume on a production server. The old volume and the new are SAN drives. I wasnt part of that process but I believe they just unpresented the volume, did a SAN copy, and presented the new volume. Not sure if that matter but just giving a few details. SCOM gives the "Logical Disk Not Available" alert with the Alert Context as "BAD". I ran WBEMTEST and it shows up as VolumeDirty=True. So that seems to explain the alert. Runing Chdksk /f makes us a little nervous. Is there another way to change this to False? Or should we be even more nervous about that? again, any input is appreciated

this monitor alerts only for single condition VolumeDirty=true. you may check it yourself inspecting script Microsoft.Windows.Server.LogicalDiskHealthCheck.vbs in SCOM cache.

Thats how I understand it and I have verified by running WBEMTEST that the value is TRUE. I guess what im saying is we dont believe thats accurate and the thought is it is TRUE from the old volume (which is using the same drive letter). The system has a new volume using the drive letter of the old volume. We believe the drive to be fine and I am wondering if there is a way to mark this as FALSE. Im guessing I can do that via WMI so maybe my question is, would that be the way to do it? running chdksk /f concerns us. This is a very large volume with data from a custom (and somewhat legacy) application. That app has its own consistency checking and running things like defrag (for example) cause big problems. Thanks agian

VolumeDirty flag is NTFS flag, is set by ntfs.sys driver on your drive(not in registry, not in wmi repository, directly on the drive in $MFT file). No other way to clear it but running chrdsk /f /r there is of course unsupported way to set this bit to false using direct NTFS structure editing. You can do this via dskprobe from support tools. ps. you can also query this bit by running "fsutil dirty query C:"