SMART report

Status
Not open for further replies.

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
Here is a bit of the SMART report I am doubtful about
Code:
SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description	Status				  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline	   Completed without error	   00%	 16541		 -
# 2  Extended offline	Completed without error	   00%	 16456		 -
# 3  Short offline	   Completed without error	   00%	 16373		 -
# 4  Short offline	   Completed without error	   00%	 16204		 -
# 5  Extended offline	Completed without error	   00%	 16150		 -
# 6  Short offline	   Completed without error	   00%	 16039		 -
# 7  Short offline	   Completed without error	   00%	 15797		 -
# 8  Extended offline	Completed: read failure	   70%	 15703		 880016000
# 9  Short offline	   Completed without error	   00%	 15629		 -
#10  Short offline	   Completed without error	   00%	 15464		 -
#11  Extended offline	Completed: read failure	   70%	 15369		 880016000
#12  Short offline	   Completed without error	   00%	 15296		 -
#13  Short offline	   Completed without error	   00%	 15078		 -
#14  Extended offline	Completed: read failure	   60%	 14984		 880016000
#15  Short offline	   Completed without error	   00%	 14910		 -
#16  Short offline	   Completed without error	   00%	 14745		 -
#17  Extended offline	Completed: read failure	   70%	 14650		 880016000
#18  Short offline	   Completed without error	   00%	 14577		 -
4 of 4 failed self-tests are outdated by newer successful extended offline self-test # 2

As you guys can see the disk was failing to go beyond 30% of the extended test. However in the last few tests it has managed to "clear" the hurdle and going to 100%. Can I trust this completely? Can/Should I RMA this disk?
This is the Full SMARTCTL output
Code:
# smartctl -x /dev/ada4
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p31 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:	 Western Digital Red
Device Model:	 WDC WD40EFRX-68WT0N0
Serial Number:	WD-WCC4E0ESU744
LU WWN Device Id: 5 0014ee 2623ee4e2
Firmware Version: 82.00A82
User Capacity:	4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:	 512 bytes logical, 4096 bytes physical
Rotation Rate:	5400 rpm
Device is:		In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Sun Feb  4 23:10:25 2018 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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:				(52560) seconds.
Offline data collection
capabilities:					(0x7b) SMART execute Offline immediate.
										Auto Offline data collection on/off support.
										Suspend Offline collection upon new
										command.
										Offline surface scan supported.
										Self-test supported.
										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:		( 526) minutes.
Conveyance self-test routine
recommended polling time:		(   5) minutes.
SCT capabilities:			  (0x703d) 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		  FLAGS	VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate	 POSR-K   200   200   051	-	0
  3 Spin_Up_Time			POS--K   181   178   021	-	7933
  4 Start_Stop_Count		-O--CK   100   100   000	-	74
  5 Reallocated_Sector_Ct   PO--CK   200   200   140	-	0
  7 Seek_Error_Rate		 -OSR-K   200   200   000	-	0
  9 Power_On_Hours		  -O--CK   078   078   000	-	16775
 10 Spin_Retry_Count		-O--CK   100   253   000	-	0
 11 Calibration_Retry_Count -O--CK   100   253   000	-	0
 12 Power_Cycle_Count	   -O--CK   100   100   000	-	73
192 Power-Off_Retract_Count -O--CK   200   200   000	-	34
193 Load_Cycle_Count		-O--CK   200   200   000	-	1484
194 Temperature_Celsius	 -O---K   116   107   000	-	36
196 Reallocated_Event_Count -O--CK   200   200   000	-	0
197 Current_Pending_Sector  -O--CK   200   200   000	-	0
198 Offline_Uncorrectable   ----CK   100   253   000	-	0
199 UDMA_CRC_Error_Count	-O--CK   200   200   000	-	0
200 Multi_Zone_Error_Rate   ---R--   200   200   000	-	0
							||||||_ K auto-keep
							|||||__ C event count
							||||___ R error rate
							|||____ S speed/performance
							||_____ O updated online
							|______ P prefailure warning

General Purpose Log Directory Version 1
SMART		   Log Directory Version 1 [multi-sector log support]
Address	Access  R/W   Size  Description
0x00	   GPL,SL  R/O	  1  Log Directory
0x01		   SL  R/O	  1  Summary SMART error log
0x02		   SL  R/O	  5  Comprehensive SMART error log
0x03	   GPL	 R/O	  6  Ext. Comprehensive SMART error log
0x06		   SL  R/O	  1  SMART self-test log
0x07	   GPL	 R/O	  1  Extended self-test log
0x09		   SL  R/W	  1  Selective self-test log
0x10	   GPL	 R/O	  1  NCQ Command Error log
0x11	   GPL	 R/O	  1  SATA Phy Event Counters
0x21	   GPL	 R/O	  1  Write stream error log
0x22	   GPL	 R/O	  1  Read stream error log
0x80-0x9f  GPL,SL  R/W	 16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS	  16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS	   1  Device vendor specific log
0xb7	   GPL,SL  VS	  39  Device vendor specific log
0xbd	   GPL,SL  VS	   1  Device vendor specific log
0xc0	   GPL,SL  VS	   1  Device vendor specific log
0xc1	   GPL	 VS	  93  Device vendor specific log
0xe0	   GPL,SL  R/W	  1  SCT Command/Status
0xe1	   GPL,SL  R/W	  1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 1
		CR	 = Command Register
		FEATR  = Features Register
		COUNT  = Count (was: Sector Count) Register
		LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
		LH	 = LBA High (was: Cylinder High) Register	]   LBA
		LM	 = LBA Mid (was: Cylinder Low) Register	  ] Register
		LL	 = LBA Low (was: Sector Number) Register	 ]
		DV	 = Device (was: Device/Head) Register
		DC	 = Device Control Register
		ER	 = Error register
		ST	 = Status register
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 1 [0] occurred at disk power-on lifetime: 8036 hours (334 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 00 00 00 34 73 fa 80 40 00

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  ea 00 00 00 00 00 00 00 00 00 00 40 08  1d+12:05:10.391  FLUSH CACHE EXT
  61 00 10 00 70 00 00 34 73 fd 18 40 08  1d+12:05:10.390  WRITE FPDMA QUEUED
  61 00 30 00 70 00 01 a0 cd d4 b0 40 08  1d+12:05:10.390  WRITE FPDMA QUEUED
  61 00 08 00 70 00 01 a0 cd d4 a0 40 08  1d+12:05:10.390  WRITE FPDMA QUEUED
  61 00 08 00 70 00 00 ac 7f 1d a8 40 08  1d+12:05:10.390  WRITE FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description	Status				  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline	   Completed without error	   00%	 16541		 -
# 2  Extended offline	Completed without error	   00%	 16456		 -
# 3  Short offline	   Completed without error	   00%	 16373		 -
# 4  Short offline	   Completed without error	   00%	 16204		 -
# 5  Extended offline	Completed without error	   00%	 16150		 -
# 6  Short offline	   Completed without error	   00%	 16039		 -
# 7  Short offline	   Completed without error	   00%	 15797		 -
# 8  Extended offline	Completed: read failure	   70%	 15703		 880016000
# 9  Short offline	   Completed without error	   00%	 15629		 -
#10  Short offline	   Completed without error	   00%	 15464		 -
#11  Extended offline	Completed: read failure	   70%	 15369		 880016000
#12  Short offline	   Completed without error	   00%	 15296		 -
#13  Short offline	   Completed without error	   00%	 15078		 -
#14  Extended offline	Completed: read failure	   60%	 14984		 880016000
#15  Short offline	   Completed without error	   00%	 14910		 -
#16  Short offline	   Completed without error	   00%	 14745		 -
#17  Extended offline	Completed: read failure	   70%	 14650		 880016000
#18  Short offline	   Completed without error	   00%	 14577		 -
4 of 4 failed self-tests are outdated by newer successful extended offline self-test # 2

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
	1		0		0  Not_testing
	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.

SCT Status Version:				  3
SCT Version (vendor specific):	   258 (0x0102)
SCT Support Level:				   1
Device State:						Active (0)
Current Temperature:					36 Celsius
Power Cycle Min/Max Temperature:	 33/42 Celsius
Lifetime	Min/Max Temperature:	  3/45 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:	 2
Temperature Sampling Period:		 1 minute
Temperature Logging Interval:		1 minute
Min/Max recommended Temperature:	  0/60 Celsius
Min/Max Temperature Limit:		   -41/85 Celsius
Temperature History Size (Index):	478 (229)

Index	Estimated Time   Temperature Celsius
 230	2018-02-04 15:13	36  *****************
 ...	..( 20 skipped).	..  *****************
 251	2018-02-04 15:34	36  *****************
 252	2018-02-04 15:35	35  ****************
 253	2018-02-04 15:36	35  ****************
 254	2018-02-04 15:37	36  *****************
 ...	..(279 skipped).	..  *****************
  56	2018-02-04 20:17	36  *****************
  57	2018-02-04 20:18	37  ******************
 ...	..( 30 skipped).	..  ******************
  88	2018-02-04 20:49	37  ******************
  89	2018-02-04 20:50	36  *****************
 ...	..( 29 skipped).	..  *****************
 119	2018-02-04 21:20	36  *****************
 120	2018-02-04 21:21	35  ****************
 ...	..(  6 skipped).	..  ****************
 127	2018-02-04 21:28	35  ****************
 128	2018-02-04 21:29	34  ***************
 ...	..( 10 skipped).	..  ***************
 139	2018-02-04 21:40	34  ***************
 140	2018-02-04 21:41	33  **************
 ...	..( 19 skipped).	..  **************
 160	2018-02-04 22:01	33  **************
 161	2018-02-04 22:02	34  ***************
 ...	..(  6 skipped).	..  ***************
 168	2018-02-04 22:09	34  ***************
 169	2018-02-04 22:10	35  ****************
 ...	..( 11 skipped).	..  ****************
 181	2018-02-04 22:22	35  ****************
 182	2018-02-04 22:23	36  *****************
 ...	..( 46 skipped).	..  *****************
 229	2018-02-04 23:10	36  *****************

SCT Error Recovery Control:
		   Read:	 70 (7.0 seconds)
		  Write:	 70 (7.0 seconds)

Device Statistics (GP Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID	  Size	 Value  Description
0x0001  2			0  Command failed due to ICRC error
0x0002  2			0  R_ERR response for data FIS
0x0003  2			0  R_ERR response for device-to-host data FIS
0x0004  2			0  R_ERR response for host-to-device data FIS
0x0005  2			0  R_ERR response for non-data FIS
0x0006  2			0  R_ERR response for device-to-host non-data FIS
0x0007  2			0  R_ERR response for host-to-device non-data FIS
0x0008  2			0  Device-to-host non-data FIS retries
0x0009  2			3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2			3  Device-to-host register FISes sent due to a COMRESET
0x000b  2			0  CRC errors within host-to-device FIS
0x000f  2			0  R_ERR response for host-to-device data FIS, CRC
0x0012  2			0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4	  1986384  Vendor specific
 

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
Will WD accept the extended test from the past?
Any idea why the test is able to jump all the way to 100%? It is a little strange, isn't it?
 
Joined
May 10, 2017
Messages
838
I would keep it for now, all attributes look good and you're likely to get a refurbished drive back, and those are a crap shoot, just keep an eye on it.
 

Bidule0hm

Server Electronics Sorcerer
Joined
Aug 5, 2013
Messages
3,710
Seems to be a flaky sector, nothing to worry too much, just keep a eye on it :)
 

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
Thanks. Created an RMA and going to cancel now. Scrubs and SMART tests run (not as many as cyber jock recommends) periodically.
Just 1 doubt, another hdd ‘ada2’ in my system had 1 unreadable (pending) sector and it was failing the long SMART tests as well. I recently replaced the disk and resilvered the system and the problem with ‘ada4’ also disappeared. Not sure how FreeNAS handles disk but my limited knowledge says one disk shouldn’t effect others’ test results.
Any comments?
 

Bidule0hm

Server Electronics Sorcerer
Joined
Aug 5, 2013
Messages
3,710
The resilvering of ada2 has probably triggered a read on the flaky sector of ada4 and as it succeeded the sector has been marked good (until the next time a read fails and the error reappears, etc...).
 
Status
Not open for further replies.
Top