[smartmontools-support] smartd mails different from smartctl results

[Christian Franke]

Nicola Urbinati wrote:
> Hi,
>
> One more insight, I'm seeing this:
>
> Mar 07 12:05:11 pbs1 smartd[1236]: Device: /dev/nvme0, number of Error
> Log entries increased from 41 to 42
> Mar 07 13:05:12 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
> unreadable (pending) sectors
> Mar 07 13:35:11 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
> unreadable (pending) sectors
> Mar 07 14:05:12 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
> unreadable (pending) sectors
> Mar 07 14:35:12 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
> unreadable (pending) sectors
> Mar 07 15:05:11 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
> unreadable (pending) sectors
>
> And that's why I'm receiving all those emails, and I see no email reset.

The above messages are logged with LOG_CRIT syslog level. The related 
"warning condition reset" and "Sending warning via mail to ADDRESS" 
messages are only logged with LOG_INFO level and may not appear in the 
above log.


>
>> Thank you very much for pointing me in the right direction.
>>
>> I do have this drive:
>>
>> === START OF INFORMATION SECTION ===
>> Device Model:     CT4000MX500SSD1
>> Serial Number:    2204E602EAA2
>> LU WWN Device Id: 5 00a075 1e602eaa2
>> Firmware Version: M3CR044

Please don't sent only such small snippets of smartctl output. This 
snippet lacks drive database information ("Device is: ... smartctl 
database").


>> And smartmontools 7.2 (default I think with debian 11, even if it's a
>> Proxmox Backup Server instance?).

Yes, only Debian unstable and testing provide 7.3.

7.2 is r5155, so it already includes the related changeset r5093.

>> I tried to download the new database file for the same release (7.2)
>> from github, but a diff command showed no difference at all.

Then you didn't use the correct drive database update branch which is 
RELEASE_7_2_DRIVEDB. Note that on github there is only a R/O mirror of 
the smartmontools SVN repo at sourceforge.


>> Is there a better way to use a newer database, if the device is there
>> at all? I do not have the machine on the internet at the moment,
>> probably in a few days.

Please try /usr/sbin/update-smart-drivedb, see "man 
update-smart-drivedb" and
https://www.smartmontools.org/wiki/Download#Updatethedrivedatabase