When using the SMART by Zabbix Agent 2 template, some disks are not discovered if not attached to a set of predefined controllers, and dmesg log is flooded with error messages (see screenshot dmesg.png and agent2log.png).

Result:
Agent2 log reveals that only the following smartctl device types are attempted (see screenshot agent2log.png):

sudo -n smartctl -a /dev/sdo -d 3ware,0 -j

sudo -n smartctl -a /dev/sdo -d sat -j

sudo -n smartctl -a /dev/sdo -d areca -j

sudo -n smartctl -a /dev/sdo -d cciss -j
Expected:

If manually running command:

sudo -n smartctl -a /dev/sdo -d scsi -j

Data is returned as expected, without errors in dmesg. See screenshot smartctl_scsi.png.

Suggested fix:

Implement a more dynamic way of detecting which device type a disk is using when agent2 is running smart.disk.discovery

Or

Add a macro in the template that makes it possible to add additional device types to the discovery operation, so the agent will check for these as well, besides the four hardcoded ones.