gnu linux smart s.m.a.r.t enabled harddisks (also ssds) try to predict when they fail – monitor disk health

10.Jul.2017

Administration / Server, GNU-Linux, Hardware / Reviews, hardware fail, storage / NAS / QNAP

smart and ssds?

and: is smart really that smart?

to do regular smart, is better than doing no smart, but as confirmed here, it can be only minutes of time from reporting an error-problem to complete harddisk failure, so smart might not prevent admins from catching an problem on time.

“drives break in a very short period of time, and neither SMART or any other software catches them on time.”

TESTING BACKUP MEDIA BEFORE USAGE: what definately makes sense and should BE ROUTINE, to extensively test a backup media for the capability of correctly storing and reading data, at least once, before putting it into productive use.

nothing threatens survival of data more than a backup that does not work (reproduce the data correctly) when most desperately needed (after ransomeware attack).

su - root
apt install e2fsprogs
badblocks -v /dev/sdX

checkout

what other tools are there

https://superuser.com/questions/171195/how-to-check-the-health-of-a-hard-drive

and just use all of em.

SMART attributes

Although S.M.A.R.T. status items vary by software, the most important item is “Health”.

This is a general indication of error-resolution and maintenance.

Details are usually listed after the Health score, indicating any areas that need attention.

Generally, there will be entries for:

Raw Read Error Rate – number of errors while reading data
Retired Blocks – blocks that have become unsafe for data storage during the life of the drive
Power On Hours – number of total hours the drive has been on
Power Cycles – number of times the drive has been turned off, then on again
Device Temperature – current internal temperature of the drive
Total LBAs Written – number of Logical Block Addresses that have been written to
Total LBAs Read – number of Logical Block Addresses that have been read from

Other items are included at the manufacturer’s discretion.

Conclusion

SMART tools allow you to perform an SSD health check.

For the most accurate information, use the proprietary software from your drive manufacturer.

src: https://www.crucial.com/articles/about-ssd/smart-and-ssds

also a gui gnu linux program available:

might be also interesting: https://dwaves.de/2019/09/08/linux-bash-script-iterate-over-all-harddisks-in-the-system-and-check-their-smart-status/

and: https://dwaves.de/2019/09/06/linux-server-monitor-software-raid-mail-notification-on-failure/

harddisks… are blackboxes of data – if something fails… you do not repair – you replace.

65% of all harddisk failurs can be announced with smart. wohoo! so don’t rely on it 😀

CentOS: https://www.linuxtechi.com/smartctl-monitoring-analysis-tool-hard-drive/

su - root; # become root

# create a script
# that permanently monitors changes to all log files
vim /scripts/mon_all_logs.sh
find /var/log/ -type f \( -name "*" \) ! -path '*.gz*' -exec tail -n0 -f "$file" {} +

# run it and open a new terminal
# on deb(apt) based systems ubuntu/debian/mint
apt-get install smartmontools; # install software
# rpm based systems fedora/redhat/centos
yum install smartmontools
# enable service
service smartd start ; chkconfig smartd on
lsblk; # check what harddisks are in your system
# enable smart for all
smartctl -s on /dev/sda
smartctl -s on /dev/sdb

# some example commands

# this is probably all the user/admin wants to know
# if the drive is healthy or not (PASSED health test)
smartctl -H /dev/sda

# wanna know more?
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.18.13] (local build)

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

smartctl -c /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] (local build)

=== START OF READ SMART DATA SECTION ===
General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  85) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

what does it do?

-c, –capabilities

[ATA] Prints only the generic SMART capabilities.

These show what SMART features are implemented and how the device will respond to some of the different SMART commands.

For example it shows if the device logs errors, if it supports offline surface scanning, and so on.

If the device can carry out self-tests, this option also shows the estimated time required to run those tests.

[NVMe] [NEW EXPERIMENTAL SMARTCTL FEATURE] Prints various NVMe device capabilities obtained from the Identify Controller and the Identify Namespace data structure.

smartctl -i /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] (local build)

=== START OF INFORMATION SECTION ===
Device Model:     Samsung SSD 860 EVO 500GB
Serial Number:    ...
LU WWN Device Id: X XXXXXX XXXXXXXXX
Firmware Version: RVT03B6Q
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 25 22:20:57 2021 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

what does it do?

-i, –info

Prints the device model number, serial number, firmware version, and ATA Standard version/revision information.

Says if the device supports SMART, and if so, whether SMART support is currently enabled or disabled.

If the device supports Logical Block Address mode (LBA mode) print current user drive capacity in bytes. (If drive is has a user protected area reserved, or is “clipped”, this may be smaller than the potential maximum drive capacity)

Indicates if the drive is in the smartmontools database (see ‘-v’ options below).

If so, the drive model family may also be printed.

If ‘-n’ (see below) is specified, the power mode of the drive is printed.

[NVMe] [NEW EXPERIMENTAL SMARTCTL FEATURE] For NVMe devices the information is obtained from the Identify Controller and the Identify Namespace data structure.

# more intensive testing
smartctl --test=long /dev/sda

# user can also redirect output to a log file
smartctl --test=long /dev/sdb > /var/log/sdb.smartl.txt
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 10 minutes for test to complete. (depending on harddisk size and speed this could take longer/shorter)
Test will complete after Tue Jan 15 16:09:36 2019

Use smartctl -X to abort test.

# when test is finished view results like this
smartctl -l selftest /dev/sdb
# check error log of drive
smartctl -l error /dev/sdb

# show temp of hd
smartctl -A /dev/sda | grep -i temperature
194 Temperature_Celsius 0x0002 176 176 000 Old_age Always - 34 (Min/Max 25/39)
smartctl -d ata -A /dev/sda | grep -i temperature
194 Temperature_Celsius 0x0002 176 176 000 Old_age Always - 34 (Min/Max 25/39)
# Debian GNU/Linux 8 (jessie)/should be the same for ubuntu
# enable permanent supervision

# rpm/fedora/redhat/centos based distros, main config resides here
vim /etc/smartmontools/smartd.conf

# The word DEVICESCAN will cause any remaining lines in this
# configuration file to be ignored: it tells smartd to scan for all
# ATA and SCSI devices. DEVICESCAN may be followed by any of the
# Directives listed below, which will be applied to all devices that
# are found. Most users should comment out DEVICESCAN and explicitly
# list the devices that they wish to monitor.
DEVICESCAN -H -m root -M exec /usr/libexec/smartmontools/smartdnotify -n standby,10,q

# debian/ubuntu it is here
vim /etc/default/smartmontools; # uncomment those lines
# Defaults for smartmontools initscript (/etc/init.d/smartmontools)
# This is a POSIX shell fragment

# List of devices you want to explicitly enable S.M.A.R.T. for
# Not needed (and not recommended) if the device is monitored by smartd
# enable_smart="/dev/sda"
# optional, because per default smart mon service will monitor all smart enabled devices

# uncomment to start smartd on system startup
start_smartd=yes

# uncomment to pass additional options to smartd on startup
smartd_opts="--interval=1800"

# save and quit
/etc/init.d/smartmontools start
/etc/init.d/smartmontools status

grep smartd /var/log/syslog;

# EXAMPLES from the man page
       smartctl -a /dev/sda
       Print a large amount of SMART information for drive /dev/sda.

       smartctl -s off /dev/sdd
       Disable SMART monitoring and data log collection on drive /dev/sdd.

       smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda
       Enable SMART on drive /dev/sda, enable automatic offline testing every four hours, and enable autosaving of SMART Attributes.  This is a good start-up line for your system's init
       files.  You can issue this command on a running system.

       smartctl -t long /dev/sdc
       Begin  an  extended self-test of drive /dev/sdc.  You can issue this command on a running system.  The results can be seen in the self-test log visible with the '-l selftest' op‐
       tion after it has completed.

       smartctl -s on -t offline /dev/sda
       Enable SMART on the disk, and begin an immediate offline test of drive /dev/sda.  You can issue this command on a running system.  The results are only used to update  the  SMART
       Attributes, visible with the '-A' option.  If any device errors occur, they are logged to the SMART error log, which can be seen with the '-l error' option.

       smartctl -A -v 9,minutes /dev/sda
       Shows the vendor Attributes, when the disk stores its power-on time internally in minutes rather than hours.

       smartctl -q errorsonly -H -l selftest /dev/sda
       Produces output only if the device returns failing SMART status, or if some of the logged self-tests ended with errors.

       smartctl -q silent -a /dev/sda
       Examine  all SMART data for device /dev/sda, but produce no printed output.  You must use the exit status (the $?  shell variable) to learn if any Attributes are out of bound, if
       the SMART status is failing, if there are errors recorded in the self-test log, or if there are errors recorded in the disk error log.

       smartctl -a -d 3ware,0 /dev/twl0
       Examine all SMART data for the first SATA (not SAS) disk connected to a 3ware RAID 9750 controller card.

       smartctl -t long -d areca,4 /dev/sg2
       Start a long self-test on the fourth SATA disk connected to an Areca RAID controller addressed by /dev/sg2.

       smartctl -a -d hpt,1/3 /dev/sda (under Linux)
       smartctl -a -d hpt,1/3 /dev/hptrr (under FreeBSD)
       Examine all SMART data for the (S)ATA disk directly connected to the third channel of the first HighPoint RocketRAID controller card.

       smartctl -t short -d hpt,1/1/2 /dev/sda (under Linux)
       smartctl -t short -d hpt,1/1/2 /dev/hptrr (under FreeBSD)
       Start a short self-test on the (S)ATA disk connected to second pmport on the first channel of the first HighPoint RocketRAID controller card.

       smartctl -t select,10-100 -t select,30-300 -t afterselect,on -t pending,45 /dev/sda
       Run a selective self-test on LBAs 10 to 100 and 30 to 300.  After the these LBAs have been tested, read-scan the remainder of the disk.  If the disk is  power-cycled  during  the
       read-scan, resume the scan 45 minutes after power to the device is restored.

       smartctl -a -d cciss,0 /dev/cciss/c0d0
       Examine all SMART data for the first SCSI disk connected to a cciss RAID controller card.

EXIT STATUS
       The  exit  statuses  of smartctl are defined by a bitmask.  If all is well with the disk, the exit status (return value) of smartctl is 0 (all bits turned off).  If a problem oc‐
       curs, or an error, potential error, or fault is detected, then a non-zero status is returned.  In this case, the eight different bits in the exit status have the following  mean‐
       ings for ATA disks; some of these values may also be returned for SCSI disks.

       Bit 0: Command line did not parse.

       Bit 1: Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode (see '-n' option above).

       Bit 2: Some SMART or other ATA command to the disk failed, or there was a checksum error in a SMART data structure (see '-b' option above).

       Bit 3: SMART status check returned "DISK FAILING".

       Bit 4: We found prefail Attributes <= threshold.

       Bit 5: SMART status check returned "DISK OK" but we found that some (usage or prefail) Attributes have been <= threshold at some time in the past.

       Bit 6: The device error log contains records of errors.

       Bit 7: The device self-test log contains records of errors.  [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.

       To  test  within the shell for whether or not the different bits are turned on or off, you can use the following type of construction (which should work with any POSIX compatible
       shell):
       smartstat=$(($? & 8))
       This looks at only at bit 3 of the exit status $?  (since 8=2^3).  The shell variable $smartstat will be nonzero if SMART status check returned "disk failing" and zero otherwise.

       This shell script prints all status bits:
       val=$?; mask=1
       for i in 0 1 2 3 4 5 6 7; do
         echo "Bit $i: $(((val & mask) && 1))"
         mask=$((mask << 1))
       done

FILES
       /usr/sbin/smartctl
              full path of this executable.

       /var/lib/smartmontools/drivedb/drivedb.h
              drive database (see '-B' option).

       /etc/smart_drivedb.h
              optional local drive database (see '-B' option).


grep smartd /var/log/*
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: smartd 6.5 2016-05-07 r4318 [x86_64-linux-4] (local build)
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: Opened configuration file /etc/smartmontools/smartd.conf
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: Configuration file /etc/smartmontools/smartd.conf was parsed, found DEVICESCAN, scanning devices
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: Device: /dev/sda, type changed from 'scsi' to 'sat'
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: Device: /dev/sda [SAT], opened
/var/log/messages-20190106:Jan  5 20:02:40 domainName smartd[896]: Device: /dev/sda [SAT], TOSHIBA DT01ACA300, S/N: WWN:5-000039-ff4e20a1

# very detailed bulk mass of informations
smartctl -a /dev/sda

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: LITEONIT LCS-256M6S 2.5 7mm 256GB
Serial Number: ....
Firmware Version: DC8110D
User Capacity: 256,060,514,304 bytes [256 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 4a
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Jan 15 15:49:47 2019 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 10) seconds.
Offline data collection
capabilities: (0x15) SMART execute Offline immediate.
No Auto Offline data collection support.
Abort Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x00) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0003 100 100 000 Pre-fail Always - 0 (0 24)
12 Power_Cycle_Count 0x0003 100 100 000 Pre-fail Always - 2011
175 Program_Fail_Count_Chip 0x0003 100 100 000 Pre-fail Always - 0
176 Erase_Fail_Count_Chip 0x0003 100 100 000 Pre-fail Always - 0
177 Wear_Leveling_Count 0x0003 100 100 000 Pre-fail Always - 319134
178 Used_Rsvd_Blk_Cnt_Chip 0x0003 100 100 000 Pre-fail Always - 3
179 Used_Rsvd_Blk_Cnt_Tot 0x0003 100 100 000 Pre-fail Always - 96
180 Unused_Rsvd_Blk_Cnt_Tot 0x0003 093 093 005 Pre-fail Always - 1408
181 Program_Fail_Cnt_Total 0x0003 100 100 000 Pre-fail Always - 0
182 Erase_Fail_Count_Total 0x0003 100 100 000 Pre-fail Always - 0
187 Reported_Uncorrect 0x0003 100 100 000 Pre-fail Always - 96
195 Hardware_ECC_Recovered 0x0003 100 100 000 Pre-fail Always - 0
241 Total_LBAs_Written 0x0003 100 100 000 Pre-fail Always - 328352
242 Total_LBAs_Read 0x0003 100 100 000 Pre-fail Always - 492805

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 1

ATA Error Count: 0
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 0 occurred at disk power-on lifetime: 768 hours (32 days + 0 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 62 00 00 08 80 fc

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
62 00 08 00 08 80 fc 01 27d+14:41:32.897 [RESERVED FOR SERIAL ATA]
00 00 08 00 00 00 00 01 27d+14:39:35.936 NOP [Abort queued commands]
00 00 08 00 00 00 00 01 27d+14:38:30.400 NOP [Abort queued commands]
00 00 08 00 00 00 00 01 27d+14:37:24.864 NOP [Abort queued commands]
00 00 08 00 00 00 00 00 27d+14:36:19.328 NOP [Abort queued commands]

Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 03 00 00 00 00 00 00 00:00:00.000 NOP [Reserved subcommand] [OBS-ACS-2]

Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 80 00 00 00 00 08

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 eb 01 00 00 00 00 ce 00:00:00.000 NOP [Reserved subcommand] [OBS-ACS-2]
80 00 00 00 08 00 08 00 39d+00:10:14.140 [VENDOR SPECIFIC]

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 0 -

followed log files:

when restarting smartmon tools service, output is like this:

==> /var/log/daemon.log <==
Jan 25 22:29:59 giada smartd[31180]: smartd received signal 15: Terminated
Jan 25 22:29:59 giada smartd[31180]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Samsung_SSD_860_EVO_500GB-SERIAL.ata.state
Jan 25 22:29:59 giada smartd[31180]: Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD10EACS_00ZJB0-WD_SERIAL.ata.state
Jan 25 22:29:59 giada smartd[31180]: smartd is exiting (exit status 0)
Jan 25 22:29:59 giada systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
Jan 25 22:29:59 giada systemd[1]: smartd.service: Succeeded.
Jan 25 22:29:59 giada systemd[1]: Stopped Self Monitoring and Reporting Technology (SMART) Daemon.
Jan 25 22:29:59 giada systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
Jan 25 22:29:59 giada smartd[31217]: smartd 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] (local build)
Jan 25 22:29:59 giada smartd[31217]: Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
Jan 25 22:29:59 giada smartd[31217]: Opened configuration file /etc/smartd.conf
Jan 25 22:29:59 giada smartd[31217]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Jan 25 22:29:59 giada smartd[31217]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], opened
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], Samsung SSD 860 EVO 500GB, S/N:SERIAL, WWN:X-XXXXXX-XXXXXXXXX, FW:RVT03B6Q, 500 GB
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], not found in smartd database.
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.Samsung_SSD_860_EVO_500GB-SERIAL.ata.state
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sdc [SAT], opened
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sdc [SAT], WDC WD10EACS-00ZJB0, S/N:WD-SERIAL, WWN:X-XXXXXX-XXXXXXXXX, FW:01.01B01, 1.00 TB
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sdc [SAT], found in smartd database: Western Digital Caviar Green

==> /var/log/syslog <==
Jan 25 22:29:59 giada smartd[31180]: smartd received signal 15: Terminated
Jan 25 22:29:59 giada smartd[31180]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Samsung_SSD_860_EVO_500GB-SERIAL.ata.state
Jan 25 22:29:59 giada smartd[31180]: Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD10EACS_00ZJB0-WD_SERIAL.ata.state
Jan 25 22:29:59 giada smartd[31180]: smartd is exiting (exit status 0)
Jan 25 22:29:59 giada systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
Jan 25 22:29:59 giada systemd[1]: smartd.service: Succeeded.
Jan 25 22:29:59 giada systemd[1]: Stopped Self Monitoring and Reporting Technology (SMART) Daemon.
Jan 25 22:29:59 giada systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
Jan 25 22:29:59 giada smartd[31217]: smartd 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] (local build)
Jan 25 22:29:59 giada smartd[31217]: Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
Jan 25 22:29:59 giada smartd[31217]: Opened configuration file /etc/smartd.conf
Jan 25 22:29:59 giada smartd[31217]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Jan 25 22:29:59 giada smartd[31217]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], opened
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], Samsung SSD 860 EVO 500GB, S/N:SERIAL, WWN:X-XXXXXX-XXXXXXXXX, FW:RVT03B6Q, 500 GB
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], not found in smartd database.
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.Samsung_SSD_860_EVO_500GB-SERIAL.ata.state
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sdc [SAT], opened
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sdc [SAT], WDC WD10EACS-00ZJB0, S/N:WD-SERIAL, WWN:X-XXXXXX-XXXXXXXXX, FW:01.01B01, 1.00 TB
Jan 25 22:29:59 giada smartd[31217]: Device: /dev/sdc [SAT], found in smartd database: Western Digital Caviar Green

==> /var/log/daemon.log <==
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list.
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sdc [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD10EACS_00ZJB0-WD_SERIAL.ata.state
Jan 25 22:30:00 giada smartd[31217]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Samsung_SSD_860_EVO_500GB-SERIAL.ata.state
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD10EACS_00ZJB0-WD_SERIAL.ata.state

==> /var/log/syslog <==
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list.
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sdc [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD10EACS_00ZJB0-WD_SERIAL.ata.state
Jan 25 22:30:00 giada smartd[31217]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Samsung_SSD_860_EVO_500GB-SERIAL.ata.state
Jan 25 22:30:00 giada smartd[31217]: Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD10EACS_00ZJB0-WD_SERIAL.ata.state