Disk discovery discovers non-existent disks

[dkoski]

Zabbix Agent version: 6.0.25
OS: Windows Server 2016

Latest data shows devices: 0 C:, 1, 2, 3, 4, 5, 6. Only "0 C:" has data. All the others report "No data available". The graphs report sporadic and short bursts of data. This is a backup server running BackupExec on bare metal. It does do tape and external disk backups. Presumably, these disks that show no data are transient but it seems like a bug to not flush them out on discovery.

David Koski

[dkoski]

Additional information: Here is some log information at debug level 4:

2024/01/15 09:55:43.060670 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(1)\Avg. Disk sec/Read",60]' error: 'No data available.'
2024/01/15 09:55:43.060670 executing direct exporter task for key 'perf_counter_en["\PhysicalDisk(2)\% Idle Time",60]'
2024/01/15 09:55:43.060670 executed direct exporter task for key 'perf_counter_en["\PhysicalDisk(2)\% Idle Time",60]'
2024/01/15 09:55:43.060670 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(6)\Avg. Disk Write Queue Length",60]' error: 'No data available.'
2024/01/15 09:55:43.060670 executing direct exporter task for key 'perf_counter_en["\PhysicalDisk(5)\Current Disk Queue Length",60]'
2024/01/15 09:55:43.061670 executed direct exporter task for key 'perf_counter_en["\PhysicalDisk(5)\Current Disk Queue Length",60]'
2024/01/15 09:55:43.061670 executing direct exporter task for key 'perf_counter_en["\PhysicalDisk(4)\Current Disk Queue Length",60]'
2024/01/15 09:55:43.061670 executed direct exporter task for key 'perf_counter_en["\PhysicalDisk(4)\Current Disk Queue Length",60]'
2024/01/15 09:55:43.064678 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(5)\Avg. Disk Write Queue Length",60]' error: 'No data available.'
2024/01/15 09:55:43.065681 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(1)\Avg. Disk Write Queue Length",60]' error: 'No data available.'
2024/01/15 09:55:43.065681 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
2024/01/15 09:55:43.065681 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(2)\Avg. Disk sec/Read",60]' error: 'No data available.'
2024/01/15 09:55:43.066684 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
2024/01/15 09:55:43.066684 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(2)\Avg. Disk Write Queue Length",60]' error: 'No data available.'
2024/01/15 09:55:43.066684 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
2024/01/15 09:55:43.066684 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
2024/01/15 09:55:43.067686 direct exporter task expired for key 'perf_counter_en["\PhysicalDisk(1)\% Idle Time",60]' error: 'No data available.'
2024/01/15 09:55:43.067686 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
2024/01/15 09:55:43.068689 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
2024/01/15 09:55:43.068689 sending passive check response: ZBX_NOTSUPPORTED: 'No data available.' to '192.168.201.21'
​

[dkoski]

I think these phantom drives may be temporary drive images, possibly created by BackupExec. There are many errors in the Windows System log that appear to be benign but may shed some light on this. They are "FilterManager" errors, Eveng ID: 3, that look like this:

"Filter Manager failed to attach to volume '\Device\Harddisk1\DR437'. This volume will be unavailable for filtering until a reboot. The final status was 0xC03A001C."

Also, Disk Manager does not show these volumes. The Zabbix graphs show they are on line intermittently, then go away. See image. The question is how to get Zabbix to ignore these.