Custom Query (1469 matches)

Running FreeBSD 11.2-RELEASE, steps to reproduce below:

smartd.conf:

DEVICESCAN -a -o on -S on -s (S/../.././02|L/../../6/03) -W 4,35,40 -m root

smartd flags:

smartd -c /usr/local/etc/smartd.conf -p /var/run/smartd.pid -A /var/log/smartd/ -i 600

/var/log/smartd/ contains attribute logs all my SATA drives, but not my NVMe drives.

If I do smartclt -a /dev/nvme0 I get expected output, and smartd sends alerts as normal (temp etc.) for the NVMe devices.

In short, the sole issue is that the attribute log fails to be written.

Thanks!

OS: OpenSUSE Leap 15.3 (x86-64) smartmontools version 7.0-6.1

I've received a number of smartd email notifications over the past few weeks. Every time, the system journal suggests that smartd detected a temperature change on /dev/sda but that an error was logged against /dev/nvme.

My system has two SSDs: /dev/sda: Samsung 850 EVO /dev/nvme0: SK Hynix P31

The following warning/error was logged by the smartd daemon today:

   Device: /dev/nvme0, number of Error Log entries increased from 11 to 12
   Device info:
   SHGP31-1000GM-2, S/N:XXXXXX, FW:41060C20

The system journal from that timestamp shows the following:

smartd[1511]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 [Raw 26] to 73 [Raw 27]
smartd[1511]: Device: /dev/nvme0, number of Error Log entries increased from 11 to 12
smartd[1511]: Sending warning via <mail> to xxxxxxxx@xxxxxxxx ...
smartd[1511]: Warning via <mail> to xxxxxx@xxxxxxxx: successful

For some reason, it looks like smartd logged the error against /dev/nvme0?

As reported in ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862908 "smartd" fails to start on the system without disks (e.g. KVM).

It would be better to start the daemon anyway and wait for pluggable disks to appear.

This could help to prevent init system failures on attempted start of "smartd".