SMART reporting not functioning

[literally a cat]

Hi there,

I've been using FreeNAS 8 for a couple of months now, but haven't yet been able to get the SMART reporting function to work as it should. I have set a daily schedule of short tests, but I simply can't get them to run.

My tests are configured as follows...

The SMART service is enabled, obviously :)

My system is a HP Proliant Microserver with 5x 2TB Samsung drives. When I was first setting the box up, I became aware of the firmware issue on these drives, and flashed them to the new version asap. However, the smartctl tool still produces the 'SamsungF4EGBadBlocks' warning message for each drive on boot up, and also whenever I edit any of my SMART tasks, despite my drives having the correct firmware. At this point, I'm assuming that the 'SamsungF4EGBadBlocks' message is something to do with why SMART tasks aren't running.

All I want is to receive emails updating me with the results of the SMART tests. FWIW, other email reporting from the system works fine (i receive two emails every day, security log and ifs volume health).

If anyone could advise me on how to get these working, then I'd be very grateful. Thanks!

 

[joeschmuck]

What version of FreeNAS 8 are you using? The current release is 8.0.3.

smartctl will always produce that badblocks message as a message for people may not have upgraded the firmware in those hard drives. Samsung didn't change the firmware number in the fix, that is why you will always see it.

Have you checked manually to see if the self tests are actually occurring as scheduled? Log in as root and run smartctl -a /dev/ada0 and see what the test results are.

I don't know if the email reporting works, I'll give it a shot but it may not occur until the turn of the day.

 

[literally a cat]

Hi joeschmuck,

Thanks for the reply. I'm currently on 8.0.2, and wasn't aware that a newer version had been released. I shall upgrade now, and see if that helps.

Here's the output from the smartctl -a command...

Code:

[root@freenas] ~# smartctl -a /dev/ada0
smartctl 5.41 2011-06-09 r3365 [FreeBSD 8.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AFT)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2H7J9JB715891
LU WWN Device Id: 5 0024e9 205c593b2
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Sun Feb  5 14:57:51 2012 GMT

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386
http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

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: 		(20100) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					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: 	 ( 255) minutes.
SCT capabilities: 	       (0x003f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   055   055   000    Old_age   Always       -       18340
  3 Spin_Up_Time            0x0023   068   039   025    Pre-fail  Always       -       9946
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       32
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       2920
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       33
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       2582
191 G-Sense_Error_Rate      0x0022   252   252   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   064   000    Old_age   Always       -       29 (Min/Max 17/34)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       6
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       34

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      2158         -
# 2  Short offline       Completed without error       00%      1887         -
# 3  Short offline       Completed without error       00%      1863         -
# 4  Short offline       Completed without error       00%      1839         -
# 5  Short offline       Completed without error       00%      1815         -
# 6  Short offline       Completed without error       00%      1791         -
# 7  Short offline       Completed without error       00%      1767         -
# 8  Short offline       Completed without error       00%      1743         -
# 9  Short offline       Completed without error       00%      1719         -
#10  Short offline       Completed without error       00%      1695         -
#11  Short offline       Completed without error       00%      1671         -
#12  Short offline       Completed without error       00%      1647         -
#13  Short offline       Completed without error       00%      1623         -
#14  Short offline       Completed without error       00%      1599         -
#15  Short offline       Completed without error       00%      1575         -
#16  Short offline       Completed without error       00%      1551         -
#17  Short offline       Completed without error       00%      1527         -
#18  Short offline       Completed without error       00%      1503         -
#19  Short offline       Completed without error       00%      1479         -
#20  Short offline       Completed without error       00%      1455         -
#21  Short offline       Completed without error       00%      1431         -

Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Am i right in saying that the 'SMART Self-test log' section implies that my tests have been running, and it's just the email that isn't being sent for whatever reason?

 

[joeschmuck]

Am i right in saying that the 'SMART Self-test log' section implies that my tests have been running, and it's just the email that isn't being sent for whatever reason?

Look at the LifeTime (hours) column and that is when the test was done. Compare that to #9 Power_on_Hours and you will know when it was performed. Based on your setting I would say it's not running. You could create a CRON job and enter smartctl -t short /dev/ada0 and that will run the test.


I'm not sure what it will take to get the email to work properly. I have included the extra parameters '-m root' in the SMART configuration for each drive with hopes a report is generated eventually. I'll know tomorrow if it worked. And I don't think 8.0.3 will make a difference but I could be wrong. If you wanted to wait for 8.0.4 I would expect to see that in March.