Tearing Hair out with Logical Disk Free Space Monitor


  • All, we are tearing our hair out with the Logical Disk Free Space Monitor. We just cannot get the state to change at all with the default management pack monitor.

    We are running SCOM 2007 SP1.

    If we create our own monitor for % Free Space and megabyte free space it works great but we want to be able to use the default monitor as that includes both the % and megabytes counters.

    Other monitors included within the MP alert fine such as services rollup, just not the Logical Disk Free Space Monitor.

    We have a test server with the agent installed, it currently has 2% and 68mb free on the D drive therefore BOTH thresholds are breached but SCOM will not change it to a critical state, as I say if we enable our own monitors it does.

    Please dont link to the Jonathan Almquist blog, we have read it and it does not answer this question.

    If anyone can solve this it would be much appreciated.

    Tuesday, July 02, 2013 11:16 AM

All replies

  • Typically the recommendation would be to make sure you have conditions that meet the thresholds for both available free disk space % and available MBs of free space:

    Since you have that covered the next three places to focus on would be as follows:

    1. Have you checked to make sure you have the thresholds set not just for System Drives but for Non-System Drives since you are concerned with D:?

    2. Have you made sure you have modified the thresholds for each type of operating system. You need separate overrides for Windows Server 2003 Logical Disks, Windows Server 2008 Logical Disks, and Windows Server 2012 Logical Disks. Go to Authoring--Monitors--search for: "logical disk -Free"

    3. Though I don't think you should need to do this, I would be curious what would happen if you modified and set the parent Aggregate Rollups for Free Space to generate an alert, I believe by default this is set to not generate an alert since the alerts should be generated by the child monitors:

    • Proposed as answer by OpsConfig Tuesday, July 02, 2013 12:20 PM
    • Edited by OpsConfig Tuesday, July 02, 2013 12:21 PM clarity
    Tuesday, July 02, 2013 12:20 PM
  • Hi, thanks for the reply, answers:-

    1. Yes, thresholds are set for non-system drives, we are using the "out-the-box" monitor which has a hard-coded threshold for non-systems drives at 5 and 10% and megabytes 1000 and 2000mb, both of which are breached on our test server.

    2, Yes, fully aware of the monitors being os specific, the out-of-the-box monitors are sealed so you cannot modify the thresholds (can only create overrides). Our test server is a 2008 box but we have also tried it against 2003 boxes and still doesnt work.

    3. Will try what you suggest there and let you know.

    I believe this is something to do with the monitor that has been installed with SCOM that just doesnt work, unfortunatley we have been unable to update the management pack to latest due to an error detailed here

    The management pack we are running at the moment is 6.0.6972.0 - can anyone confirm if the Logical Disk Free Space monitor definitley works with that management pack?


    Tuesday, July 02, 2013 12:48 PM
  • The aggregate rollup didnt make a difference unfortunatley
    Tuesday, July 02, 2013 1:33 PM
  • 1- Free space monitor runs on shedule. 1h for Windows 2000 and 15 min for 2003 and newer.

    2 - sometimes alerts are not displayed if instance is allready in warning/error state. Check Healt explorer for this computer.

    Wednesday, July 10, 2013 10:31 AM
  • Hi, thanks for the response

    1. Yes, we are aware of the schedules

    2. We have a test server here that has 68mb free on 3gb Volume, this is obviously well below the default 5% and 1GB default values. Are you saying we put this into a healthy state and then back to critical, if so then we have already tried that numerous times. Each time we also reset health but it will not change the state. This is the same behaviour for any servers we try.

    This is so annoying as all the other monitors work fine, just not the logical disk, there MUST be something obvious we are missing with this, just cant work out what.

    Again, if we create our own % Free Space monitor it works ok, just not the built-in one, which is the one we need to work.

    Thursday, July 11, 2013 11:14 AM
  • No overrides (disables) for class or object?
    Thursday, July 11, 2013 1:27 PM
  • It wont change state with or without an override set, is that what your meaning?
    Friday, July 12, 2013 11:46 AM