[ZBX-24056] Disk discovery discovers non-existent disks Created: 2024 Feb 07  Updated: 2024 Mar 06

Status: Open
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 6.0.26
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: David Koski Assignee: Zabbix Support Team
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2016 Standard, Backup Exec version 22.0.1193

Attachments: PNG File 01-airtherm.png     PNG File 01-harding.png     PNG File 01-krey.png     PNG File 01-lvat.png     PNG File 01-nwpr.png     PNG File 01-renco.png     PNG File 01-wpud.png     PNG File Untitled.png    

 Description   

Steps to reproduce:

  1. Changes in configuration...
    None.
  2. Navigate to screen title...
    Latest Data
  3. Click on screen element...
    <some host>
  4. ...

We monitor over 200 hosts and there is only one that persists with this issue. Latest Data reveals disks that have "No Data Available". Graphs reveal spotty access. Successful drives are indicated by "0 C:...", etc. but failing drives are "1: ..." (without a drive letter). I suspect Backup Exec is making temporary VHD disks but I don't have a good reason for saying so, just my gut. This has been reported to Zabbix forum with no responses:

https://www.zabbix.com/forum/zabbix-help/476767-disk-discovery-discovers-non-existent-disks

The above link has screenshots and log file.

Result:
See screenshot...
See log file...
See memory dump...
Expected:
See screenshot....
See attached patch file...

 Comments   
Comment by David Koski [ 2024 Feb 28 ]

See new images.  I have found seven more systems that have the same issue.  None of these are VMs.  I believe the "failing" drives are external USB.  They cannot be related to BackupExec as it is not installed on these latest ones.  The graphs for these have the same issue as the original.  They have mostly blank space.

Generated at Fri Apr 04 14:44:29 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.