Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-9081

Disks on a HBA are not discovered by zabbix

XMLWordPrintable

    • 2

      Steps to reproduce:

      1. Server with SAS-harddisks which are directly connected to an HBA
      2. add smart-template or ask zabbix-agent2 directly

      Result:
      in short:

      smartctl raw output:

      smartctl --scan 
/dev/sda -d scsi # /dev/sda, SCSI device 
/dev/sdb -d scsi # /dev/sdb, SCSI device 
/dev/sdc -d scsi # /dev/sdc, SCSI device 
/dev/sdd -d scsi # /dev/sdd, SCSI device 
/dev/sde -d scsi # /dev/sde, SCSI device 
/dev/sdf -d scsi # /dev/sdf, SCSI device 
/dev/sdg -d scsi # /dev/sdg, SCSI device 
/dev/sdh -d scsi # /dev/sdh, SCSI device 
/dev/sdi -d scsi # /dev/sdi, SCSI device 
/dev/sdj -d scsi # /dev/sdj, SCSI device 
/dev/sdk -d scsi # /dev/sdk, SCSI device 
/dev/sdl -d scsi # /dev/sdl, SCSI device 
/dev/sdm -d scsi # /dev/sdm, SCSI device 
/dev/sdn -d scsi # /dev/sdn, SCSI device 
/dev/sdo -d scsi # /dev/sdo, SCSI device 
/dev/sdp -d scsi # /dev/sdp, SCSI device 
/dev/sdq -d scsi # /dev/sdq, SCSI device 
/dev/sdr -d scsi # /dev/sdr, SCSI device 
/dev/sds -d scsi # /dev/sds, SCSI device 
/dev/sdt -d scsi # /dev/sdt, SCSI device 
/dev/sdu -d scsi # /dev/sdu, SCSI device 
/dev/sdv -d scsi # /dev/sdv, SCSI device 
/dev/sdw -d scsi # /dev/sdw, SCSI device 
/dev/sdx -d scsi # /dev/sdx, SCSI device 
/dev/sdy -d scsi # /dev/sdy, SCSI device 
/dev/sdz -d scsi # /dev/sdz, SCSI device 
/dev/sdaa -d scsi # /dev/sdaa, SCSI device 
/dev/sdab -d scsi # /dev/sdab, SCSI device 
/dev/sdac -d scsi # /dev/sdac, SCSI device 
/dev/sdad -d scsi # /dev/sdad, SCSI device 
/dev/sdae -d scsi # /dev/sdae, SCSI device 
/dev/sdaf -d scsi # /dev/sdaf, SCSI device

      but zabbix discover just two of them, which are SATA:

      smart.disk.discovery                          [s|[{"{#NAME}":"sdae sat","{#DISKTYPE}":"ssd","{#MODEL}":"INTEL SSDSC2KB480GZ","{#SN}":"PHYI233307HB480BGN","{#PATH}":"/dev/sdae","{#RAIDTYPE}":"sat","{#ATTRIBUTES}":"Reallocated_Sector_Ct Power_On_Hours Power_Cycle_Count Available_Reservd_Space Program_Fail_Count Erase_Fail_Count Unsafe_Shutdown_Count Power_Loss_Cap_Test SATA_Downshift_Count End-to-End_Error_Count Uncorrectable_Error_Cnt Drive_Temperature Unsafe_Shutdown_
Count Temperature_Celsius Pending_Sector_Count CRC_Error_Count Host_Writes_32MiB Workld_Media_Wear_Indic Workld_Host_Reads_Perc Workload_Minutes Unknown_SSD_Attribute Available_Reservd_Space Media_Wearout_Indicator Thermal_Throttle_Status Power_Loss_Cap_Test Host_Writes_32MiB Host_Reads_32MiB NAND_Writes_32MiB"},{"{#NAME}":"sdaf sat","{#DISKTYPE}":"ssd","{#MODEL}":"INTEL SSDSC2KB480GZ","{#SN}":"PHYI233307QZ480BGN","{#PATH}":"/dev/sdaf","{#RAIDTYPE}":"sat","{#ATTRIBUTES}":"Reallocated_Sector_Ct Power_On_Hours Power_Cycle_Count Available_Reservd_Space Program_Fail_Count Erase_Fail_Count Unsafe_Shutdown_Count Power_Loss_Cap_Test SATA_Downshift_Count End-to-End_Error_Count Uncorrectable_Error_Cnt Drive_Temperature Unsafe_Shutdown_Count Temperature_Celsius Pending_Sector_Count CRC_Error_Count Host_Writes_32MiB Workld_Media_Wear_Indic Workld_Host_Reads_Perc Workload_Minutes Unknown_SSD_Attribute Available_Reservd_Space Media_Wearout_Ind
icator Thermal_Throttle_Status Power_Loss_Cap_Test Host_Writes_32MiB Host_Reads_32MiB NAND_Writes_32MiB"}]]

      I also attached an more detailed (verbose) output..

      Expected:

      that all Disks are discovered, which is important in a storage area  

       

      The go script should discover all disks and remove dublicates by serialnumber, so we don't need to iterate through all combinations, just the things that smartctl --scan discovered

        1. zabbix_agent2_smart-discovery_scsi.log
          179 kB

            rzvejs Rudolfs Zvejs
            shad0w Stefan
            Team B
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: