Weird problem with Drive Free Space test.

mrw · Post by **mrw** » Fri Jul 12, 2019 8:35 am

Hi,
IÂ´m monitoring a pretty standard virtual Win2012R2 server using an active RMA from another server in the same subnet and domain.

It has 2 drives. C: and D:
The test that checks C: works perfectly.
But the test that checks the D: has some problem and always returns the status unknown.
This has worked before. But after we migrated this virtual server to another datacenter, this particular test stopped working.
All other tests such as CPU(Win RPC), Memory(SNMP/WMI), service checks and other SNMP tests work fine.

Any ideas on this?

Thanks in advance,
//Andreas..

KS-Soft · Post by **KS-Soft** » Fri Jul 12, 2019 10:01 am

Yes, its strange.
What test method do you use? UNC? Drive Free Space?
Any error in Reply field?
Disk D is local (not mapped network) drive?

Regards
Alex

mrw · Post by **mrw** » Mon Jul 15, 2019 2:04 am

The test method is Drive Free Space. I run the exact same test on the C: which works.
The only Status reply I get from the test is "Unknown".
The D: is a normal disk. In Disk Management C: is on disk 0 and D: is on disk 1.
The disks are created in VMware so everything is virtual.

And the D: drive itself works for the users. Several folders on the D: has shares that works for the users.

KS-Soft · Post by **KS-Soft** » Mon Jul 15, 2019 8:09 am

Could you check Win32_LogicalDisk class on target system using WMI Explorer?
https://www.ks-soft.net/hostmon.eng/wmi/index.htm

Regards
Alex

mrw · Post by **mrw** » Mon Jul 15, 2019 9:01 am

Ok, I installed the WMI explorer locally on that server and selected Win32_LogicalDisk from the huge list.
In the instances frame I get A:, C:, D:, G:.

KS-Soft · Post by **KS-Soft** » Mon Jul 15, 2019 9:31 am

H'm, may be you setup HostMonitor test using some non-latin letter that looks like "D"?
May be wrong host specified?

btw: WMI Explorer can check remote systems as well

Regards
Alex

mrw · Post by **mrw** » Tue Jul 16, 2019 2:19 am

Ok, I have tried to rewrite the D: but still same problem.
I have compared the two(C: and D: ) tests and they are exactly the same.
Tried writing with small letter, d:, which changes itself to capitals.
Doublechecked the ipaddress and the RMA. Everything is correct.
Removed the test and copied the one using C: and then only changing the drive to D:. Then it fails.
Also tested to change the RMA-setting from inherit from parent to setting the agent directly but still no difference.

Then I manually stopped the SNMP service on the server, refreshed all tests and then the service test for SNMP failed, and also all other tests that rely on SNMP failed. Just as they should. This was to test if somehow I am on the wrong server or something other strange.

Also had some colleagues look through the tests incase the problem is me

So the other tests are correct and relate to this server. As far as I can tell.

Scratching my head here... Never had this problem on any server.

Are there some other test we could do verify the existance of D: from the Hostmon side?

//Andreas..

mrw · Post by **mrw** » Tue Jul 16, 2019 2:41 am

Ha!
Solved it!

I noticed that the test for the C: didnÂ´t really returned the correct number compared when I checked tha values on the server manually.
Then I saw that it returned the exact same as the test on the server that is the RMA.
So I checked all the ipaddresses but everything looked correct.
But finally I checked the internal DNS in the AD and there I found a reference in the reverse zone which was wrong. It had an extra record giving the ipaddress of my testserver to the name of the server running the RMA.
Removed that and voila! The D: test worked!
And also the C: test now shows the correct number and differs from the same on the RMA-server..

Regards!
//Andreas..

KS-Soft · Post by **KS-Soft** » Tue Jul 16, 2019 6:01 am

Thank you for the report!

Regards
Alex