Volume Capacity- Drive is missing
Some servers are not monitoring J Drives anymore. There is J Drive in Physical Disks but not in Volume Capacity. In Audit Logs there is information about new instances being found and some instances disappeared from host but there's no explanation why. Drive exists on the host. I attached screenshot.
In Global Definition I run Active Discovery on WinVolumeUsage and there were discovered Drives except the J Drive. Also, received a Active Discovery- 3 instances being filtered out- I attached screenshot.
Were there any recent changes in Logic Monitor? I didn't update any modules so that is not a cause.
lucjad
Posted 2 years ago·Last reply 2 years ago
8 comments
fadeinthemix
·2 years agoMine was read access to the service account to the volume
fadeinthemix
·2 years agoI had this issue.
Get-WmiObject Win32_Volume | Select-Object Name,Cap*
Drives showed that were missing had 2 extra integers from the ones that were showing up.
I changed greater from 0 to exists in the volume capacity module and the drives showed up.
fadeinthemix
·2 years agoBut there were empty/
I checked my Local account admin and it was in capacity. But the Script that ran non admin account doesn't have it.
As a test I will grant Local Admin to the service account
LM User
·2 years agoThat part of the UI lacks discoverability, but each of those filter rules can be clicked on to show which items were filtered out by that rule. That will let you know if the instances are not discovered because they do not meet the criteria to pass through the filter.
lucjad
OP2 years agoI clicked on the J Drive and it says Filtered Out Messages of Capacity Greater Than 0. This Drive's Volume was monitored for months and now it's just not there.
LM User
·2 years agoIs there any reason WMI would think that the drive has 0 capacity?
lucjad
OP2 years agoNot sure. There were no recent changes to the host or Logic Monitor's configurations. What else can I check? This also happened to other server being monitored in LM.
LM User
·2 years agoHm, try running:
On the target machine. It should tell you what the OS thinks the capacity of the drive is. If the capacity is null or 0, LM is doing what it's supposed to. If the OS says it's got a non-zero capacity, then LM is broken and you would want to take it up with support.