SMART
Self-Monitoring, Analysis and Reporting Technology (SMART) is a technology built into modern hard drives to monitor the health of the drive and anticipate failures. The two classes of failures are: predictable and unpredictable. Examples of predicable failures are increased number of bad sectors and increased temperature from wear; they typically occur from slow processes. Unpredictable failures occur without warning and suddenly; for example, a hard drive dropped may report more than a normalized number of read errors.
The hard drives within SafeNet Luna Network HSM appliances implements SMART. A background process called the SMART control daemon (smartd) starts automatically at power up and is responsible for monitoring the hard drive via the SMART technology in it. The daemon records its findings via syslog.
|
Facility Keyword |
Software Process |
Log File |
|---|---|---|
|
|
|
|
SMART Attributes
From LunaSH, you can query the SMART attributes (Luna SA/SP: status disk; Luna IS: system disk). The example below shows the SMART attributes reported from the shell command lunash:>status disk:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 154 152 021 Pre-fail Always - 1300 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 601 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1383 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 601 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 138 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 462 194 Temperature_Celsius 0x0022 115 092 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
The ID# and ATTRIBUTE NAME columns are the SMART attribute defined by the drive vendor. Note that vendors have generally standardized on the attributes and their meaning. The FLAG column indicates the main purpose of each attribute; correlating to the text in the TYPE and UPDATED columns. Only the last two bits are of any significance. Bit 0 identifies whether the attribute is an advisory (0) or a pre-fail notification (1). An advisory means that the disk has exceeded its intended design life while a pre-fail notification means that the disk is predicated to fail within 24 hours. Bit 1 indicates whether attribute monitoring occurs strictly offline (0) or during offline and normal operations (1).
The RAW_VALUE, VALUE, WORST and THRESH columns report on the specific attribute. The drive controller reports the RAW_VALUE. VALUE is normalized where a higher value is better. As VALUE drops (i.e., becomes worse), it approaches a threshold. THRESH is the value at which SMART reports a ‘threshold exceeded’ event. WORST is the most extreme reading recorded for the attribute. A VALUE of 100 is an initial default value. Consider attribute #174 (Temperature) as an example to put these four values in context. The example shows the current temperature reading of the drive as 28 degrees Celsius. Normalized, this reading is 115. A value of 100 therefore is 43 degrees Celsius. The worst reading recorded is a normalized value of 092 which translates to 51 degrees Celsius. This attribute has no threshold as it represents an advisory.
Assume that the SMART control daemon generated the following log message:
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 200 to 92
The next query of the SMART attributes might report the following information for attribute #1:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 092 092 051 Pre-fail Always - 37767785
If the drive controller reads a value that, once normalized, is less than or equal to the THRESH value, the daemon generates a critical log message and a query of the SMART attributes reports a VALUE less than or equal to THRESH as the following example shows.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 92 to 51 ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 051 051 051 Pre-fail Always FAILING_NOW 4528445
The WHEN_FAILED column indicates that the attribute has reached the THRESH value.
Significant Expected Log Messages
Banner at Start Up
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: smartd version 5.38 [i686-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Home page is http://smartmontools.sourceforge.net/#012
These two messages are the first log entries written by the smart control daemon. When Thales updates the SMART control daemon to a more recent version, the following messages more closely resemble the startup banner.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: 1411:smartd 6.2 2013-07-26 r3841 [i686-linux-2.6.18-164.el5] (local build) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Read Configuration File
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Opened configuration file /etc/smartd.conf 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Configuration file /etc/smartd.conf parsed.
These messages indicate that the SMART control daemon successfully opened and read the contents of the configuration file that contains the directives for how the daemon is to operate. When Thales updates the daemon to a newer release, the location of the configuration file will change as represented in the follow examples.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Opened configuration file /usr/local/etc/smartd.conf 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Configuration file /usr/local/etc/smartd.conf parsed.
Monitoring Devices at Start Up
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, opened 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device /dev/sda: using '-d sat' for ATA disk behind SAT layer. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, opened 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, not found in smartd database. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, enabled SMART Attribute Autosave. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, enabled SMART Automatic Offline Testing. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, is SMART capable. Adding to "monitor" list. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Monitoring 0 ATA and 1 SCSI devices
These messages indicate that the SMART control daemon was successful in starting up and identifies the type and number of each device the daemon is monitoring. For SafeNet Luna Network HSM appliances, only one serial ATA device applies. The daemon opens the device to query its capabilities [the first message in the examples above]. The daemon uses SCSI/ATA Translation (SAT) to enable communication with the drive [the second message]. In SAT mode, the daemon reopens the device [third message] and looks for it in an internal database [fourth message] but does not find an entry for the device. The smart.conf file sets the directives for the daemon and these directives include attribute autosave (-S on) and automatic offline testing (-o on) [fifth and sixth messages]. Turning on attribute autosave instructs the disk drive to use non-volatile storage for attributes such as error counters, power-up hours and other useful data so that these values do not get reset to zero the next time the device is power-cycled. Turning on automatic offline testing instructs the drive to update certain SMART attributes every four hours. The disk used in the SafeNet Luna Network HSM appliance is SMART-capable [seventh message] so the daemon monitors it [eighth message].
In preparing this document, Thales reviewed the source code of a newer version of the smart control daemon. Thales plans to update the daemon at some future date. The next set of messages show the messages this new daemon outputs at start up.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, type changed from 'scsi' to 'sat' 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], opened 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], WDC WD2500BHTZ-04JCPV0, S/N:WD-WX11EC1TE568, WWN:5-0014ee-058a177e6, FW:04.06A00, 250 GB 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], not found in smartd database. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], enabled SMART Attribute Autosave. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], enabled SMART Automatic Offline Testing. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Monitoring 1 ATA and 0 SCSI devices 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda [SAT], initial Temperature is 28 Celsius (Min/Max ??/28)
The SMART control daemon opens the device [third message] and successfully queries it for device-specific information [fourth message]. Similar messages follow in the output. The newer daemon reports the initial temperature reading from a sensor built into the disk [tenth message].
Fork Into Background Process
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: smartd has fork()ed into background mode. New PID=23509.
This message indicates that the startup sequence for the smart control daemon completed successfully, leading to the daemon to fork into a background mode process as exhibited if you query the process list.
root 23509 1 0 11:04 ? 00:00:00 /usr/sbin/smartd -q never
Self Tests
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, starting scheduled Short Self-Test. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, starting scheduled Long Self-Test.
These messages record that the smart-enabled drive ran a short and/or long self-test. The short self-test runs daily; the long self-test runs weekly, an hour after the short test. These tests usually run early in the morning.
Attribute Change
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, SMART Usage Attribute: 7 Seek_Error_Rate changed from 100 to 200 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, SMART Usage Attribute: 9 Power_On_Hours changed from 100 to 99 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, SMART Usage Attribute: 200 Multi_Zone_Error_Rate changed from 100 to 200
These messages show changes in SMART attributes. The log severity of info means that the new values are still within acceptable ranges.
Prefailure Change
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 100 to 200
Messages such as this example show changes in SMART pre-failure attributes.
Temperature Change
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Temperature changed +5 Celsius to 37 Celsius (Min/Max 26/37)
This message is common in the log file and indicates a change in temperature measured at the hard disk sensor. The SMART control daemon monitors the sensor once every 30 minutes and logs the temperature if it has changed from the last reading.
Temperature Limit Reached
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, Temperature 45 Celsius reached limit of 44 Celsius (Min/Max 31/49)
This message indicates that the temperature measured at the hard disk drive reached an upper limit for normally expected readings.
Critical Temperature Change
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, Temperature 49 Celsius reached critical limit of 48 Celsius (Min/Max 31/49)
This message indicates that the temperature measured at the hard disk drive exceeds the critical upper limit.
Received Exit Signal
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: smartd received signal 15: Terminated 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: smartd received signal 3: Quit 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: smartd received signal <#>: <Xxxxxxx>
These messages indicate that the SMART control daemon received an exit signal. info severity messages are normal and expected; crit severity messages are not. In the latter case, the signal number is <#> and the text translation of this signal is <Xxxxxx>.
Unexpected Log Messages
Under normal circumstances, you should not see any of these log messages. If you do so, please contact Thales Technical Support to report the message and seek guidance on what to do next.
Configuration File not in Expected Location
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: No configuration file /usr/local/etc/smartd.conf found, scanning devices
At start up, the SMART control daemon expects to find the configuration file for its directives in the /usr/local/etc directory.
Cannot Open Configuration File
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: <error message>: Unable to open configuration file /usr/local/etc/smartd.conf
This message indicates that although the SMART control daemon located the configuration file, the daemon was unable to open it for the reason cited by <error message> in the log message.
Configuration File Format Errors
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Error: line 14 of file /usr/local/etc/smartd.conf is more than MAXLINELEN=256 characters.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Error: continued line 44 (actual line 14) of file /usr/local/etc/smartd.conf is more than MAXCONTLINE=1023 characters.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 1 (drive DEVICESCAN): unknown Directive: /dev/sd4
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Run smartd –D to print a list of valid Directives.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 15 (drive /dev/sda): -s argument "(" is INVALID extended regular expression. Unmatched ( or \(.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: File /usr/local/etc/smartd.conf line 15 (drive /dev/sda): ignoring previous Test Directive -s (S/../.././02)
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: File /usr/local/etc/smartd.conf line 15 (drive /dev/sda): warning, character 4 (x) looks odd in extended regular expression (S/x./.././02)
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: File /usr/local/etc/smartd.conf line 15 (drive /dev/sda): ignoring previous Address Directive -m john@email.com
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Configuration file /usr/local/etc/smartd.conf has fatal syntax errors.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Configuration file /usr/local/etc/smartd.conf parsed but has no entries (like /dev/hda)
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 16 (drive /dev/sda): Directive -M 'exec' argument: missing closing quote
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 16 (drive /dev/sda): Directive -M 'exec' argument must be followed by executable path.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: File /usr/local/etc/smartd.conf line 16 (drive /dev/sda): ignoring previous mail Directive -M exec /usr/local/smtp
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line %18 (drive /dev/sda): unknown Directive: -b
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line %19 (drive /dev/sda): Missing argument to -W Directive
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line %20 (drive /dev/sda): Invalid argument to -M Directive: yearly
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Valid arguments to -n Directive are: never[,N][,q], sleep[,N][,q], standby[,N][,q], idle[,N][,q] *
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Drive: /dev/sda, implied '-a' Directive on line 21 of file /usr/local/etc/smartd.conf
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Drive: /dev/sda, -M Directive(s) on line 22 of file /usr/local/etc/smartd.conf need -m ADDRESS Directive
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Drive: /dev/sda, -m <nomailer> Directive on line 23 of file /usr/local/etc/smartd.conf needs -M exec Directive
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 35 (drive /dev/sda): Directive: -i takes integer argument from 1 to 255.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 36 (drive /dev/sda): Directive: -I has argument: on; needs integer from 1 to 255.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 37 (drive /dev/sda): Directive: -W takes 1-3 integer argument(s) from 0 to 255.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: File /usr/local/etc/smartd.conf line 38 (drive /dev/sda): Directive: -W has argument: off; needs 1-3 integer(s) from 0 to 255.
These messages indicate format errors in the smartd.conf file. Depending upon the version of the smart control daemon, the configuration file might be /etc/smartd.conf or /usr/local/etc/smartd.conf.
* This text is an example. See man smartd.conf for a complete list and description of directives and arguments.
Cannot Register Device
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Unable to register scsi device /dev/sda at line 17 of file /usr/local/etc/smartd.conf 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Unable to register scsi device /dev/sda
These messages indicate that the smart control daemon was unable to register the device specified in the smartd.conf file.
Force Scan For Devices
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Configuration file /usr/local/etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
This message indicates that the configuration file specified that the SMART control daemon was to scan for devices rather than rely on entries in the file.
Could Not Scan For Devices or No Devices To Scan
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Problem creating device name scan list 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: In the system's table of devices NO devices found to scan
The first message indicates that the configuration file specified that the SMART control daemon was to scan for devices but that the scan failed. The second message indicates that daemon has no SMART-enabled devices to scan.
Out of Memory
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Smartd: Out of memory
This message indicates that the SMART control daemon did not have sufficient memory on startup.
Exception
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Smartd: Exception: <xxxxxx>
This message indicates that the SMART control daemon encountered an exception <xxxxxx> on startup and exited.
Received Hang Up or Interrupt Signal
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Signal HUP - rereading configuration file /etc/smartd.conf
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Signal INT - rereading configuration file /etc/smartd.conf ("SIGQUIT_KEYNAME" quits)
These messages indicate that the SMART control daemon was instructed via a signal to reread the configuration file normally read on startup.
Continue on Error
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Reusing previous configuration
This message indicates that while rereading the configuration file, the daemon encountered an error and reverted to the previously-read configuration settings instead.
Unable to Monitor Devices
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
This message indicates that the SMART control daemon did not find any SMART-enabled devices to monitor.
Mail-Related Messages
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Mail can't be enabled together with --capabilities. All mail will be suppressed. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Sending a mail was suppressed. Mails can't be send when capabilites [sic] are enabled 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: internal error in MailWarning(): cfg.mailwarn->emailfreq=0 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Contact smartmontools-support@lists.sourceforge.net; internal error in MailWarning(): which=-1, size=88 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Sending warning via <mail> to <nomailer> ... 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Executing test of <mail> to <nomailer> ... 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: failed (fork or pipe failed, or no memory) <error string> 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer> produced unexpected output (here truncated to 1024 bytes) to STDOUT/STDERR: <unexpected output> 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: flushed remaining STDOUT/STDERR 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: more than 1 MB STDOUT/STDERR flushed, breaking pipe 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: pclose(3) failed <error string> 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: failed (32-bit/8-bit exit status: 255/133) perhaps caught signal 5 [Trace/breakpoint trap] 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: failed (32-bit/8-bit exit status: 255/133) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Warning via <mail> to <nomailer>: successful 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Warning via <mail> to <nomailer>: exited because of uncaught signal 5 [Trace/breakpoint trap] 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Warning via <mail> to <nomailer>: process STOPPED because it caught signal 5 [Trace/breakpoint trap] 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Read SMART Self-Test Log worked again, warning condition reset after 16 emails
Thales does not compile the SMART control daemon with libcap-ng enabled to send mail. The first two messages indicate that the daemon is compiled this way and that the settings in the configuration file are incompatible with libcap-ng settings. The latter messages indicate problems with how mail is configured to be sent and/or status of sending mail.
One Check
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Started with '-q onecheck' option. All devices successfully [sic] checked once. smartd is exiting (exit status 0)
The message indicates that the smartd.conf file contains a directive for the SMART control daemon to start and terminate with only a check of any SMART-enabled devices.
Ignore Device or Duplicate Device
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda[auto], ignored 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, duplicate, ignored
The first message indicates that the smartd.conf file identifies a device but directs the SMART control daemon to ignore the device for monitoring. The second message indicates that the device is specified more than once in the smartd.conf file.
Could Not Detect Device, Unsupported Device, Not a ATA/SCSI Device or Device Cannot be Registered
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, unable to autodetect device type 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, unsupported device type 'auto' 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, neither ATA nor SCSI device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, not available 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Unable to register device /dev/sda (no Directive -d removable). Exiting.
The first message indicates that the SMART control daemon was unable to interrogate the device specified in the smartd.conf file. The second message indicates that the device is not SMART-enabled. The third message indicates that the device is not ATA or SCSI. The fourth message is a warning that the daemon could not detect the device but is continuing, while the fifth message indicates that the daemon is stopping because it could not detect the device and the smartd.conf file contains a directive to do so under this circumstance.
Could Not Open Device
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, open() failed: <xxxxxx>
If debug is enabled or scanning is not, this message indicates that the SMART control daemon was unable to open the device for monitoring: <xxxxxx> is the reason why.
Could Not Fork Into Background Process
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: smartd unable to fork daemon process! 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: PID file /var/run/smartd.pid0 didn't show up! 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: unable to write PID file /var/run/smartd.pid0 - exiting.
These messages indicate that the startup sequence for the SMART control daemon was unable to complete successfully because the daemon could not properly fork a new process.
Writing PID File
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: file /var/run/smartd.pid0 written containing PID 1729
This message identifies the process identifier and process identifier file for the background smart control daemon process.
Help for Configuration File Directives
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]:Configuration file (/usr/local/etc/smartd.conf) Directives (after device name): -d TYPE Set the device type: auto, ignore, removable ... -T TYPE Set the tolerance to one of: normal, permissive -o VAL Enable/disable automatic offline tests (on/off) -S VAL Enable/disable attribute autosave (on/off) -n MODE No check if: never, sleep[,N][,q], standby[,N][,q], idle[,N][,q] -H Monitor SMART Health Status, report if failed -s REG Do Self-Test at time(s) given by regular expression REG -l TYPE Monitor SMART log or self-test status: error, selftest, xerror, offlinests[,ns], selfteststs[,ns] -l scterc,R,W Set SCT Error Recovery Control -e Change device setting: aam,[N|off], apm,[N|off], lookahead,[on|off], security-freeze, standby,[N|off], wcache,[on|off] -f Monitor 'Usage' Attributes, report failures -m ADD Send email warning to address ADD -M TYPE Modify email warning behavior (see man page) -p Report changes in 'Prefailure' Attributes -u Report changes in 'Usage' Attributes -t Equivalent to -p and -u Directives -r ID Also report Raw values of Attribute ID with -p, -u or -t -R ID Track changes in Attribute ID Raw value with -p, -u or -t -i ID Ignore Attribute ID for -f Directive -I ID Ignore Attribute ID for -p, -u or -t Directive -C ID[+] Monitor [increases of] Current Pending Sectors in Attribute ID -U ID[+] Monitor [increases of] Offline Uncorrectable Sectors in Attribute ID -W D,I,C Monitor Temperature D)ifference, I)nformal limit, C)ritical limit -v N,ST Modifies labeling of Attribute N (see man page) -P TYPE Drive-specific presets: use, ignore, show, showall -a Default: -H -f -t -l error -l selftest -l selfteststs -C 197 -U 198 -F TYPE Use firmware bug workaround: ... Attribute ID is a decimal integer 1 <= ID <= 255 Use ID = 0 to turn off -C and/or -U Directives Example: /dev/sda -a
This text is the help information for configuring the smartd.conf file.
Write State File
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, state written to /var/log/devstate
This message indicates that the SMART control daemon wrote the state(s) of monitored device(s) to a file.
Cannot Unlink PID File
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Can't unlink PID file /var/run/smartd.pid0 (<error string>).
This message indicates that the SMART control daemon was unable to delete a process identifier file because of the error reported: <error string>.
Close Failed
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, <error string>, close() failed
This message indicates that the SMART control daemon was unable to close a monitored device because of the error reported: <error string>.
Code Bug
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Please inform smartmontools-support@lists.sourceforge.net, including output of smartd -V. 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: smartd is exiting (exit status 10)
These messages indicate a coding error in the SMART control daemon.
ATA Error Log Read Failure
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, Read Summary SMART Error Log failed 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, Read Extended Comprehensive SMART Error Log failed 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, Read SMART Self Test Log Failed
These messages indicate a failure to read the error log(s) of ATA devices.
ATA Device Scan Messages
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, not ATA, no IDENTIFY DEVICE Structure
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, packet devices [this device CD/DVD] not SMART capable
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, smartd database not searched (Directive: -P ignore).
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, found in smartd database.
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, WARNING: <warning text>*
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, presets are: ...
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, lacks SMART capability
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, ATA IDENTIFY DEVICE words 82-83 don't specify if SMART capable.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, proceeding since '-T permissive' Directive given.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, to proceed anyway, use '-T permissive' Directive.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, could not enable SMART capability
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, could not disable SMART Attribute Autosave.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, disabled SMART Attribute Autosave.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, could not enable SMART Attribute Autosave.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, not capable of SMART Health Status check
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, Read SMART Values failed
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, Read SMART Thresholds failed, ignoring -f Directive
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, can't monitor Temperature, ignoring -W 3,44,48
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no Attribute 279, ignoring -r 279!
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, not monitoring Prefailure Attributes, ignoring -r 196!
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, could not disable SMART Automatic Offline Testing.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, SMART Automatic Offline Testing unsupported...
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, enable SMART Automatic Offline Testing failed.
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SMART Self-test Log, ignoring -l selftest (override with -T permissive)
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SMART Self-test Log, ignoring -l selftest
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SMART Error Log, ignoring -l error (override with -T permissive)
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SMART Error Log, ignoring -l error
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no Extended Comprehensive SMART Error Log, ignoring -l xerror (override with -T permissive)
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no Extended Comprehensive SMART Error Log, ignoring -l xerror
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, SMART Error Logs report different error counts: 12 != 143
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SMART Offline Data Collection capability, ignoring -l offlinests (override with -T permissive)
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SMART Self-test capability, ignoring -l selfteststs (override with -T permissive)
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, no ATA CHECK POWER STATUS support, ignoring -n Directive
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, CHECK POWER STATUS returned 17, not ATA compliant, ignoring -n Directive
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, ATA settings applied: <settings string>
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, no SCT Error Recovery Control support, ignoring -l scterc
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, set of SCT Error Recovery Control failed
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, SCT Error Recovery Control set to: Read: 7, Write: 7
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, state read from /var/lib/smartmontools/smartd.ST3500620AS-5QM2644Q.ata.state
* Example: ATA error count 9 inconsistent with error log pointer 5
These messages indicate the status or a failure of a scan of an ATA device. The SafeNet Luna Network HSM appliance does not use ATA devices.
SCSI Device Scan Messages
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Both 36 and 64 byte INQUIRY failed; skip device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, INQUIRY response less than 36 bytes; skip device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, not a disk like device [PDT=0x7], skip 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, WDC WD2500JS-60NCB1 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, NOT READY (e.g. spun down); skip device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, NO MEDIUM present; skip device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, BECOMING (but not yet) READY; skip device 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, failed Test Unit Ready [err=-22] 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Bad IEC (SMART) mode page, err=-5, skip device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, IE (SMART) not enabled, skip device Try 'smartctl -s on /dev/sda' to turn on SMART features 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, unexpectedly failed to read SMART values 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, can't monitor Temperature, ignoring -W 3,44,48 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, does not support SMART Self-Test Log. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, could not disable autosave (set GLTSD bit). 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, disabled autosave (set GLTSD bit). 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, could not enable autosave (clear GLTSD bit). 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, enabled autosave (cleared GLTSD bit). 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, state read from /var/lib/smartmontools/smartd.ST3500620AS-5QM2644Q.ata.state
These messages indicate the status or a failure of a scan of a SCSI or SCSI-like device. The SafeNet Luna Network HSM appliance uses a serial ATA device which SMART considers SCSI-like. However, the messages in this section are unexpected in the logs.
Log Self-Test Progress & Errors
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, previous self-test completed without error 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, previous self-test was aborted by the host 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, previous self-test was interrupted by the host with a reset 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, previous self-test could not complete due to a fatal or unknown error 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, previous self-test completed with error (unknown test element) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, previous self-test completed with error (electrical test element) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, previous self-test completed with error (servo/seek test element) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, previous self-test completed with error (read test element) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, previous self-test completed with error (handling damage?) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, self-test in progress, 80% remaining 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, unknown self-test status 0x1f 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, Self-Test Log error count increased from 12 to 13 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, new Self-Test Log error at hour timestamp 7202 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Self-Test Log error count decreased from 27 to 26 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, does not support Self-Tests 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, skip since Self-Test already in progress 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, not capable of L Self-Test 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, not capable of Long Self-Test 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, execute Long Self-Test failed (err: -1) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Offline or Self-Testing. 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Offline or Self-Testing. 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Offline Immediate Test 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Conveyance Self-Test 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Short Self-Test 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Long Self-Test 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of Selective Self-Test 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, will not skip scheduled Offline Immediate Test despite unclear Self-Test byte (SAMSUNG Firmware bug). 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, skip scheduled Offline Immediate Test; 20% remaining of current Self-Test. 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, prepare Offline Immediate Test failed 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, next test span at LBA 1256500 - 1460000 2500000 sectors, 50% - 58% of disk). 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, execute Offline Immediate Test failed.
These messages indicate the status of an in-progress self-test, a failure to log self-tests or a self-test error.
Test Schedule
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, old test of type S not run at Wed Feb 29 02:00:00 2012 GMT, starting now. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Next scheduled self tests (at most 5 of each type per device): 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, will do test 1 of type S at Wed Feb 29 02:00:00 2012 GMT 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Totals [Wed Feb 29 12:05:00 2012 GMT - Wed Feb 29 02:00:00 2012 GMT]: 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, will do 050 tests of type S
These messages indicate status of scheduled tests.
Check Pending Sector Count Identifier
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, can't monitor Current Pending Sector count - no Attribute 197 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, ignoring Current Pending Sector count - bogus Attribute 197 value 3442 (0xd72)
These messages indicate an error on the sector count identifier for a SMART attribute.
Critical Attribute Change
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, SMART Usage Attribute: 7 Seek_Error_Rate changed from 10000 to 20000
Messages such as this example, show critical changes in SMART attributes, possibly indicating impending disk failure.
Critical Prefailure Change
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 92 to 51
Messages such as this example, show critical changes in SMART pre-failure attributes, possibly indicating impending disk failure.
Sector Count Change
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, 1237505 Currently unreadable (pending) sectors 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, 1237505 Total unreadable (pending) sectors 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, 1237505 Offline uncorrectable sectors 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, 1237505 Total offline uncorrectable sectors
These messages indicate sector attribute changes. Any one of these messages may include additional information at the end of the message to indicate the change from the last measure, [e.g., (changed 57500)].
Temperature Change
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, failed to read Temperature 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: [trip Temperature is 65 Celsius]
The first message indicates that the SMART control daemon was unable to obtain a measure of the temperature attribute. The second message indicates the temperature at which the drive shuts down if it measures this value.
Attribute Error
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, Failed SMART usage Attribute: 185 Head Stability. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, same Attribute has different ID numbers: 185 = 200
These messages indicate errors by the SMART control daemon to interpret SMART attributes.
Check ATA Device Health
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, open() failed: No such device or address 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, opened ATA device 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, CHECK POWER STATUS spins up disk (0x00 -> 0xff) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, CHECK POWER STATUS returned 1, not ATA compliant, ignoring -n Directive 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, is in STANDBY mode, suspending checks 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, IDLE mode ignored due to reached limit of skipped checks (15 checks skipped) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/ada, is back in ACTIVE or IDLE mode, resuming checks (1 check skipped) 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, not capable of SMART self-check 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, FAILED SMART self-check. BACK UP DATA NOW! 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, failed to read SMART Attribute Data 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/ada, ATA error count increased from 15 to 16
These messages provide health status of ATA device attributes.
Check SCSI Device Health
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, open() failed: No such device or address
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, opened SCSI device
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, failed to read SMART values
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, SMART Failure: <failure string>
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, self-test in progress
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, non-SMART asc,ascq: 4,26
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, SMART health: passed*
* if debug mode enabled.
These messages provide health status of SCSI device attributes.
Auto Standby Feature
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, System auto standby enable failed: <failure string> 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Disable auto standby not supported, ignoring ',ns' from -l offlinests,ns and -l selfteststs,ns 2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: Device: /dev/sda, Self-test(s) completed, system auto standby enable failed: <failure string> 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Self-test(s) completed, system auto standby enabled 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Self-test(s) in progress, system auto standby disable rejected: <failure string> 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, Self-test(s) in progress, system auto standby disabled
These messages indicate failures of the auto standby feature of the hard disk.
Sleep and Wakeup
2012 Feb 29 12:05:01 myLuna daemon crit smartd[1234]: System clock time adjusted to the past. Resetting next wakeup time. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Sleep time was 10 seconds too long, assuming wakeup from standby mode. 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Signal USR1 - checking devices now rather than in 30 seconds.
These messages indicate failures in the mechanism to sleep and wake up the SMART control daemon at prescribed intervals to query and report on SMART attributes.
Offline Log Collection Status
2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, offline data collection was never started (auto:on) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, offline data collection was completed without error (auto:on) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, offline data collection is in progress (auto:on) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, offline data collection was suspended by an interrupting command from host (auto:on) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, offline data collection was aborted by an interrupting command from host (auto:on) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, offline data collection was aborted by the device with a fatal error (auto:on) 2012 Feb 29 12:05:01 myLuna daemon info smartd[1234]: Device: /dev/sda, unknown offline data collection status 0x78
These messages indicate failures to perform offline data collection. Depending upon the status, the SMART control daemon logs these messages as either crit or info; the examples above show info only.
