Ad Widget

**Vladimir Goriachev** · 05-02-2024, 22:13

How this trigger should work, I have Exit Status = 64 on several devices, and at the same time the trigger status is OK?

SMART [{#NAME}]: Error log contains records

The device error log contains records of errors.

( count(/SMART by Zabbix agent 2/smart.disk.es[{#NAME}],#2) = 1 and bitand(last(/SMART by Zabbix agent 2/smart.disk.es[{#NAME}]),64) = 64 ) or ( bitand(last(/SMART by Zabbix agent 2/smart.disk.es[{#NAME}]),64) = 64 and bitand(last(/SMART by Zabbix agent 2/smart.disk.es[{#NAME}]),64) > bitand(last(/SMART by Zabbix agent 2/smart.disk.es[{#NAME}],#2),64) )

**vicyn** · 07-02-2024, 09:08

Hi,
I want to get "total byte written"(TWB). Smartctl shows the values "Sector Size" and "Total_LBAs_Written". TWB = Total_LBAs_Written * Sector Size / 1024*1024*1024*1024. In the zabbix template "SMART by Zabbix agent 2 active" i don't see metric "Sector Size". Please tell me how add metric "Sector Size" to template?

**Zsolt** · 03-04-2024, 16:30

Hi,

I'm having some difficulties with the smart plugin. I'm using Debian 10 on both my server and client:

Code:

Server: debian 10 4.19.0-17-amd64, zabbix: 6.0.0 Revision 5203d2ea7d
Client: debian 11 5.10.0-0.bpo.12-amd64, zabbix: 6.0.0 Revision 5203d2ea7d

I installed the zabbix-agent2 on the client, setup its config, added `SMART by Zabbix agent 2` template to this host on the zabbix web interface.
However, all I get as smart response is a faulty smart.disk.get with the following error message:

error: 'Cannot fetch data: Failed to scan for devices: Cannot unmarshal JSON: invalid character 's' looking for beginning of value..'

After fiddling with every possibility (double checking permissions, installed modules and packages, everything I could think of), I finally found something useful in the logs:

Code:

2024/04/03 15:57:48.194180 received passive check request: 'smart.disk.discovery' from '10.0.0.215'
2024/04/03 15:57:48.194265 [1] processing update request (1 requests)
2024/04/03 15:57:48.194288 [1] adding new request for key: 'smart.disk.discovery'
2024/04/03 15:57:48.194300 [1] created direct exporter task for plugin 'Smart' itemid:0 key 'smart.disk.discovery'
2024/04/03 15:57:48.194372 executing direct exporter task for key 'smart.disk.discovery'
2024/04/03 15:57:48.194468 [Smart] executing smartctl command: sudo -n smartctl --scan -j
2024/04/03 15:57:48.207429 [Smart] command sudo -n smartctl --scan -j smartctl raw response: smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.12-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=======> UNRECOGNIZED OPTION: j

Use smartctl -h to get a usage summary
2024/04/03 15:57:48.207465 failed to obtain PID of dead child process: no child processes
2024/04/03 15:57:48.207494 failed to execute direct exporter task for key 'smart.disk.discovery' error: 'Cannot fetch data: Failed to scan for devices: Cannot unmarshal JSON: invalid character 's' looking for beginning of value..'
2024/04/03 15:57:48.207546 sending passive check response: ZBX_NOTSUPPORTED: 'Cannot fetch data: Failed to scan for devices: Cannot unmarshal JSON: invalid character 's' looking for beginning of value..' to '10.0.0.215'

As I see, smartctl doesn't even have an option "-j", that's why I'm getting this otherwise completely useless error (the returned motd starts with smartctl version, thus with the letter s...). Did I miss something very obvious at the smartmontool install?

**schoeppi** · 22-04-2024, 16:52

Once per day I get this message for all disks in all our servers:

Problem name: SMART [sdXYZ sat]: Disk self-test is not passed

This seems to be a bug which occures when a selftest is running for the disks on the servers which is the case for our machines.

Do you have the same issue and how do you handle it? Do you have selftests deactivated?

Now I've changed the trigger to this to hopefulle stop this error till it is fixed in the smart zabbix agnet2 active template, but I don't know if this the right approach:

last(/SMART by Zabbix agent 2/smart.disk.test[{#NAME}],#1)="false" and last(/SMART by Zabbix agent 2/smart.disk.test[{#NAME}],#2)="false"

What do you think and how do you get around this bug?

**beriapl** · 23-04-2024, 12:54

Originally posted by anmg

I have different results with running smartctl:

Code:

sudo -u zabbix /usr/local/sbin/smartctl --scan

---- I get only virtual drive

Code:

sudo -u zabbix sudo /usr/local/sbin/smartctl --scan

---- I get full drive list (screenshot is for both commands)

so when i run

Code:

zabbix_get -shostname -p 10050 -k smart.disk.discovery

I have empty reply

Code:

[]

smartmotools v. 7.3-7.4
zabbix-agent 6.4.10

I've got a similar issue.

Locally all commands work well, but zabbix_get from the zabbix server is an empty response.

Did you manage to sort it out?

Code:

root@pve01-01:~# ip a | grep vlan25
12: vlan25@vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.2.128.67/17 scope global vlan25
root@pve01-01:~# sudo -u zabbix /usr/sbin/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
root@pve01-01:~# sudo -u zabbix sudo /usr/sbin/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/bus/0 -d megaraid,0 # /dev/bus/0 [megaraid_disk_00], SCSI device
/dev/bus/0 -d megaraid,1 # /dev/bus/0 [megaraid_disk_01], SCSI device
/dev/bus/0 -d megaraid,5 # /dev/bus/0 [megaraid_disk_05], SCSI device
/dev/bus/0 -d megaraid,6 # /dev/bus/0 [megaraid_disk_06], SCSI device
/dev/bus/0 -d megaraid,7 # /dev/bus/0 [megaraid_disk_07], SCSI device

Code:

root@zabbix6:~# zabbix_get -s 10.2.128.67 -k smart.disk.discovery
[]
root@zabbix6:~# zabbix_get -s 10.2.128.67 -k smart.disk.get
[]

However it is the same with zabbix_agent locally:

Code:

root@pve01-01:~# zabbix_agent2 -t smart.disk.get
smart.disk.get                                [s|[]]
root@pve01-01:~# sudo -u zabbix zabbix_agent2 -t smart.disk.get
smart.disk.get                                [s|[]]

smartctl 7.3
zabbix_agent2 (Zabbix) 6.4.13
Revision 6e531c40ff3 25 March 2024, compilation time: Mar 25 2024 15:21:36
Plugin communication protocol version is 6.4.0

zabbix_server (Zabbix) 6.4.13
Revision 6e531c40ff3 25 March 2024, compilation time: Mar 25 2024 15:12:00

**Gomo** · 01-06-2024, 00:00

I would appreciate if someone could take a look at my issue posted here https://www.zabbix.com/forum/zabbix-...-agent-2-issue and assist. Thanks!

**Turbid** · 05-09-2024, 09:16

Originally posted by ga6QWsJ2dVEF

I am having some difficulty with this template as the smart.disk.discovery uses random RAID controllers to obtain the SMART stats (see output below), but the only one that works well for me is the scsi device type (specifically: -d scsi -- output not shown, but trust me, it works).

Code:

 14:31:20.917075 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sda -d 3ware,0 -j
14:31:20.917116 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdb -d areca,1 -j
14:31:20.917161 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdh -d sat -j
14:31:20.917224 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdf -d cciss,0 -j
14:31:20.917281 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sda -d sat -j
14:31:20.917315 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdi -d areca,1 -j
14:31:20.917417 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdb -d 3ware,0 -j
14:31:20.917482 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdf -d 3ware,0 -j
14:31:20.917542 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdf -d sat -j
14:31:20.917592 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdf -d areca,1 -j
14:31:20.917704 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sde -d cciss,0 -j
14:31:20.917751 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sda -d areca,1 -j
14:31:20.917799 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sda -d cciss,0 -j
14:31:20.917865 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdc -d 3ware,0 -j
14:31:20.917952 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdi -d 3ware,0 -j
14:31:20.918036 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdb -d cciss,0 -j
14:31:20.918150 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdg -d cciss,0 -j
14:31:20.918316 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdg -d sat -j
14:31:20.918486 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdh -d cciss,0 -j
14:31:20.918588 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdb -d sat -j
14:31:20.918685 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdc -d cciss,0 -j
14:31:20.918733 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdc -d sat -j
14:31:20.918838 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdi -d cciss,0 -j
14:31:20.918925 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdg -d areca,1 -j
14:31:20.918971 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdi -d sat -j
14:31:20.919022 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdj -d sat -j
14:31:20.919139 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdc -d areca,1 -j
14:31:20.919192 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdh -d 3ware,0 -j
14:31:20.919263 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdj -d cciss,0 -j
14:31:20.919362 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdd -d areca,1 -j
14:31:20.919428 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdj -d 3ware,0 -j
14:31:20.919803 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sde -d 3ware,0 -j
14:31:20.919886 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdg -d 3ware,0 -j
14:31:20.919967 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sde -d sat -j
14:31:20.920031 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdd -d 3ware,0 -j
14:31:20.920094 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdd -d cciss,0 -j
14:31:20.920157 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sde -d areca,1 -j
14:31:20.920245 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdh -d areca,1 -j
14:31:20.920425 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdj -d areca,1 -j
14:31:20.920585 [Smart] executing smartctl command: sudo -n smartctl -a /dev/sdd -d sat -j

On the Zabbix template, I tried to set an LLD macro {#RAIDTYPE} and {#RAID} to scsi but this was unsuccessful. I tried to force the Zabbix Agent SMART Plugin executable path to include the full executable path with the -d scsi, and that did not work (don't recommend it, the smart.disk.discovery process keeps continuously looping.

Any hints? This template gets the correct data only with the SCSI device type, but I have no idea how to set this on the Zabbix Agent2 config or on the Zabbix Template for the host.

I encountered the same problem. According to the logs, the agent is in an infinite loop and the request smart.disk.discovery is timed out:

Code:

# sudo -u zabbix zabbix_agent2 -c /etc/zabbix/zabbix_agent2.conf -t smart.disk.discovery
smart.disk.discovery [m|ZBX_NOTSUPPORTED] [Timeout occurred while gathering data.]
#
# journalctl -u zabbix-agent2 | tail
сен 05 10:15:52 node-3-krd sudo[1271362]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdd -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271363]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdc -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271357]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdc -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271366]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdd -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271370]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdc -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271374]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdb -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271378]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdb -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271377]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdb -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271375]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdb -d cciss,0 -j
сен 05 10:15:52 node-3-krd sudo[1271380]:   zabbix : PWD=/ ; USER=root ; COMMAND=/sbin/smartctl -a /dev/sdd -d cciss,0 -j

Also someone encountered this on reddit: https://www.reddit.com/r/zabbix/comm...oring_timeout/

P.S. https://support.zabbix.com/browse/ZBX-25181

**whoops** · 10-09-2024, 11:54

Is it possible to use it normally on windows?
I am using Win11 as monitored host with Zabbix Agent 2 v7.0.3, and installed last smartmontools as default.

Out of the box:

17822:20240910:121835.500 discovery rule "win11host:smart.disk.discovery" became not supported: Failed to execute smartctl: failed to look up smartctl exec path: exec: "smartctl": executable file not found in %PATH%.

Defined:

Code:

Plugins.Smart.Path="C:\Program Files\smartmontools\bin\smartctl.exe"

at "C:\Program Files\Zabbix Agent 2\zabbix_agent2.d\plugins.d\smart.conf" and got:

Cannot fetch data.: failed to scan for devices: failed to look up smartctl exec path: exec: ""C:\\Program Files\\smartmontools\\bin\\smartctl.exe"": file does not exist.

**molnart** · 19-09-2024, 22:49

Originally posted by mhk

same here.
the thing I found in regards to Proxmox - that I can't find a way to undo - is this:

from the agent log:

Code:

2022/08/23 15:30:52.485456 executing direct exporter task for key 'smart.disk.discovery'
2022/08/23 15:30:52.485476 [Smart] executing smartctl command: sudo -n smartctl --scan -j
2022/08/23 15:30:52.485900 [Smart] command sudo -n smartctl --scan -j smartctl raw response: sh: 1: sudo: not found
2022/08/23 15:30:52.485926 failed to execute direct exporter task for key 'smart.disk.discovery' error: 'Cannot fetch data: Failed to scan for devices: Cannot unmarshal JSON: invalid character 's' looking for beginning of value..'

Notice the "sudo -n smartctl --scan [...]" and then the "sh: 1: sudo: not found"
which from my assumption is what causes it, since Proxmox runs on Debian as root (no sudo pre-installed) but the plugin always want's to call the discovery with sudo and hence fails...

any idea (apart from installing sudo, which I really don't want tbh) how to tell the thing to call it's function without sudo?

at least that's what I found out so far, trying to solve this

was there ever a solution for this? I am too struggling with getting smart data without sudo installed

**eTawR** · 13-10-2024, 09:36

I've got smart integration working so far. My only problem is, that the graphs are not really graphs:

did anybody else have this problem and found a solution?

Originally posted by molnart

was there ever a solution for this? I am too struggling with getting smart data without sudo installed

maybe you can define an alias (or a script at /usr/local/bin for that matter) which does nothing except for executing the following command(s)?

**dixie2k** · 24-10-2024, 13:00

Originally posted by schoeppi

Once per day I get this message for all disks in all our servers:

Problem name: SMART [sdXYZ sat]: Disk self-test is not passed

This seems to be a bug which occures when a selftest is running for the disks on the servers which is the case for our machines.

Do you have the same issue and how do you handle it? Do you have selftests deactivated?

Now I've changed the trigger to this to hopefulle stop this error till it is fixed in the smart zabbix agnet2 active template, but I don't know if this the right approach:

last(/SMART by Zabbix agent 2/smart.disk.test[{#NAME}],#1)="false" and last(/SMART by Zabbix agent 2/smart.disk.test[{#NAME}],#2)="false"

What do you think and how do you get around this bug?

schoeppi

Have you managed a resolution? If so, how?

Thanks!

**schoeppi** · 29-10-2024, 20:25

No, I do not have a better solution than the adapted trigger posted before. And I still don't know if this is the right aproach.

Smart monitoring with Zabbix is IMHO not really good. The described problem I have triggers much false alerts and if smart values are changing only a generic number with the problem is shown in the operational data which makes it necessary to find out if there is a real serious problem or not.

I wonder how others do smart monitoring with Zabbix and I wonder if there are better solutions then the template.

In general I am very happy with Zabbix, but smart monitoring is one of the less things which really should be improved.

**DmitryDonskikh** · 02-12-2024, 01:56

Hi guys!
I have a working Zabbix server 7.0.6 and a bunch of Win10/11 PCs with Zabbix agent2 7.0.6, with smartctl 7.4.
Zabbix template template_module_smart_agent2.yaml version 7.0-1.
Discovery works ok, "Get disk attributes" item receives data, BUT: JSON contains not all attributes, and only RAW values.
See, this is what it retutrns on "Wear levelling count":

zabbix plugin:

Code:

"wear_leveling_count": {
"value": 633,
"raw": "633"
}

while smartctl -a -j is much more informational:

smatrctl:

Code:

{
"id": 173,
"name": "Wear_Leveling_Count",
"value": 50,
"worst": 50,
"thresh": 5,
"when_failed": "",
"flags": {
"value": 51,
"string": "PO--CK ",
"prefailure": true,
"updated_online": true,
"performance": false,
"error_rate": false,
"event_count": true,
"auto_keep": true
},
"raw": {
"value": 633,
"string": "633"
}
}

Moreover, plugin's JSON lacks a lot of valuable information which smartctl can obtain: disk size, speed, form-factor etc:

smartctl:

Code:

  "user_capacity": {
    "blocks": 250069680,
    "bytes": 128035676160
  },
  "logical_block_size": 512,
  "physical_block_size": 4096,
  "rotation_rate": 0,
  "form_factor": {
    "ata_value": 3,
    "name": "2.5 inches"
  },
  "interface_speed": {
    "current": {
      "sata_value": 3,
      "string": "6.0 Gb/s",
      "units_per_second": 60,
      "bits_per_unit": 100000000
    }
  },

and so on.
Why so? IIUC, I should rely on SMART-calculated values, not RAW values. Am I missing something? Or how should I deal with it?

**PavelZ** · 05-12-2024, 17:08

Originally posted by DmitryDonskikh

Discovery works ok, "Get disk attributes" item receives data, BUT: JSON contains not all attributes, and only RAW values.
See, this is what it retutrns on "Wear levelling count":

There is a separate ticket dedicated to this problem https://support.zabbix.com/browse/ZBX-25646
And I suggest you leave a mark there. I also can't figure out how to get this data.

Also, it is unclear how you are going to unify these indicators between different SSD manufacturers? According to my research, everything is not that simple.
The situation is somewhat smoothed out by the fact that in modern NVMe disks the attributes have been standardized.

**PavelZ** · 05-12-2024, 19:29

Originally posted by eTawR

did anybody else have this problem and found a solution?

This is a fairly common situation with many indicators now. This preprocessing step in this item is to Discard unchanged with heartbeat 6h.
It's not easy to decide how the Zabbix creators should handle this. When you look at the item graph, you just have to keep this in mind.

I suggest using updated dashboards or grafana, where missing values can be connected.

Ad Widget

Discussion thread for official Zabbix SMART Disk monitoring

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment