So I have one machine, SCOM shows error or corruption on three drives. I use either of those queries, and for the one I see DirtyBit set to <null> for each drive, or with the other query I see the VolumeDirty set to <null> for each drive. It too is running W2008R2 Std SP1
On Tue, Oct 7, 2014 at 11:23 AM, Kevin Holman <[email protected]> wrote: > That monitor runs the > Microsoft.Windows.Server.LogicalDiskHealthCheck.vbs script with a single > parameter of the computername. > > > > > > My article is incomplete (actually, a bit wrong, or the script changed > over time). > > > > The script actually works like this: > > > > It checks the OS build number to be >3624, which is Server 2003 and later, > and/or Windows Vista and later for client OS. > > Then – as long as this is true – we query Win32_Volume (select * from > Win32_Volume) and examine the DirtyBitSet property. > > > > ONLY if the version if the OS version is older, do we run the longer WMI > query, and examine VolumeDirty property. > > > > > > Either way – either the DirtyBitSet is true, or the VolumeDirty is true, > in order to make this monitor go red. > > > > > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Justin Thomas > *Sent:* Tuesday, October 7, 2014 10:50 AM > *To:* msmom > *Subject:* Re: [msmom] Re: File System Error or Corruption > > > > the number is 6.0.7026.0, and I am seeing this on Windows Server 2008 R2 > Std, SP1, and Windows Server 2008 R2 Std. > > > > On Tue, Oct 7, 2014 at 9:19 AM, Kevin Holman <[email protected]> > wrote: > > Justin – what is the version **number** of the Windows Server 2008 > Operating System (Monitoring) MP that you have imported, and what is the > version and SP level of the operating system having the issue? > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Justin Thomas > *Sent:* Tuesday, October 7, 2014 8:47 AM > *To:* msmom > *Subject:* [msmom] Re: File System Error or Corruption > > > > that was the wrong link, this is the one I was following: > > http://blogs.technet.com/b/kevinholman/archive/2012/08/13/3347532.aspx > > > > On Mon, Oct 6, 2014 at 3:17 PM, Justin Thomas <[email protected]> wrote: > > I have a few servers that are generating File System Error or Corruption > alert. Per this article I've gone to those servers to verify with wbemtest > and I am not finding these drives to be in error. How do I clear this/keep > them from alerting? > > > > > http://blogs.technet.com/b/kevinholman/archive/2011/09/30/opsmgr-new-base-os-mp-6-0-6956-0-adds-cluster-shared-volume-monitoring-bpa-and-many-changes.aspx > > > > Thanks > > -- > > Probable Contrarian > > > > > > > -- > > Probable Contrarian > > > > > > > > > > > -- > > Probable Contrarian > > > > > > -- Probable Contrarian
