Another SMART error question

[George51]

Gto a SMART alert today, failed a short test, have run an extended test. Here are the results:

Code:

smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:	 Western Digital Red
Device Model:	 WDC WD30EFRX-68EUZN0
Serial Number:	WD-WCC4N2VH45HY
LU WWN Device Id: 5 0014ee 20ba70481
Firmware Version: 82.00A82
User Capacity:	3,000,592,982,016 bytes [3.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:	Thu Oct 12 21:39:36 2017 BST
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:	  ( 121) The previous self-test completed having
										the read element of the test failed.
Total time to complete Offline
data collection:				(40020) 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:		( 401) 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		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x002f   200   200   051	Pre-fail  Always	   -	   23
  3 Spin_Up_Time			0x0027   178   177   021	Pre-fail  Always	   -	   6083
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   74
  5 Reallocated_Sector_Ct   0x0033   200   200   140	Pre-fail  Always	   -	   1
  7 Seek_Error_Rate		 0x002e   200   200   000	Old_age   Always	   -	   0
  9 Power_On_Hours		  0x0032   072   072   000	Old_age   Always	   -	   20534
 10 Spin_Retry_Count		0x0032   100   253   000	Old_age   Always	   -	   0
 11 Calibration_Retry_Count 0x0032   100   253   000	Old_age   Always	   -	   0
 12 Power_Cycle_Count	   0x0032   100   100   000	Old_age   Always	   -	   74
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   32
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   397
194 Temperature_Celsius	 0x0022   125   114   000	Old_age   Always	   -	   25
196 Reallocated_Event_Count 0x0032   199   199   000	Old_age   Always	   -	   1
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -	   0
198 Offline_Uncorrectable   0x0030   100   253   000	Old_age   Offline	  -	   0
199 UDMA_CRC_Error_Count	0x0032   200   200   000	Old_age   Always	   -	   0
200 Multi_Zone_Error_Rate   0x0008   200   200   000	Old_age   Offline	  -	   1

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: read failure	   90%	 20531		 91958888
# 2  Short offline	   Completed: read failure	   10%	 20523		 91958888
# 3  Short offline	   Completed without error	   00%	 20499		 -
# 4  Short offline	   Completed without error	   00%	 20475		 -
# 5  Short offline	   Completed without error	   00%	 20451		 -
# 6  Short offline	   Completed without error	   00%	 20427		 -
# 7  Extended offline	Completed without error	   00%	 20409		 -
# 8  Short offline	   Completed without error	   00%	 20379		 -
# 9  Short offline	   Completed without error	   00%	 20355		 -
#10  Short offline	   Completed without error	   00%	 20331		 -
#11  Short offline	   Completed without error	   00%	 20307		 -
#12  Short offline	   Completed without error	   00%	 20283		 -
#13  Short offline	   Completed without error	   00%	 20259		 -
#14  Extended offline	Completed without error	   00%	 20245		 -
#15  Short offline	   Completed without error	   00%	 20211		 -
#16  Short offline	   Completed without error	   00%	 20187		 -
#17  Short offline	   Completed without error	   00%	 20163		 -
#18  Short offline	   Completed without error	   00%	 20140		 -
#19  Short offline	   Interrupted (host reset)	  90%	 20140		 -
#20  Short offline	   Completed without error	   00%	 20116		 -
#21  Extended offline	Completed without error	   00%	 20096		 -

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):

Is this drive on it's way out? Or is it just suffering man-flu?

Cheers

 

[danb35]

Gto a SMART alert today, failed a short test, have run an extended test.

...which it also failed. The SMART data doesn't look awful, but persistent SMART self-test failures sound like a dying drive to me.

 

[George51]

...which it also failed. The SMART data doesn't look awful, but persistent SMART self-test failures sound like a dying drive to me.

Okay okay: feel free to shoot this down, but this the zpool status for the pool with the drive

Code:

pool: Family
 state: ONLINE
  scan: scrub repaired 0 in 29h40m with 0 errors on Sun Sep 24 07:10:45 2017
config:

		NAME												STATE	 READ WRITE CKSUM
		Family											  ONLINE	   0	 0	 0
		  raidz2-0										  ONLINE	   0	 0	 0
			gptid/be088ef8-0145-11e5-b445-d050991a0729.eli  ONLINE	   0	 0	 0
			gptid/ed6205d2-0118-11e5-b769-d050991a0729.eli  ONLINE	   0	 0	 0
			gptid/e8d39fbc-0053-11e5-9081-d050991a0729.eli  ONLINE	   0	 0	 0
			gptid/f40f1682-00b3-11e5-9c21-d050991a0729.eli  ONLINE	   0	 0	 0
			gptid/831b1013-0087-11e5-a639-d050991a0729.eli  ONLINE	   0	 0	 0
			gptid/6404b3e6-ffb5-11e4-8a4f-d050991a0729.eli  ONLINE	   0	 0	 0

errors: No known data errors

With no issues there, would it be foolish to wait until the drive starts failing further before replacing? Or is the smart data telling me to replace sooner than that?

 

[danb35]

Or is the smart data telling me to replace sooner than that?

I think so. It isn't affecting the pool status because (apparently) there's no data on the (one, so far) bad sector. Ordinarily, a single bad sector wouldn't result in a failed SMART self-test, though. If you didn't mind reduced redundancy for a while, you could try this:

• Offline the disk
• Run a full badblocks routine on it
• Run another SMART long test

If the reallocated sector/event counts remain low (i.e., low single digits), the raw read error rate doesn't increase, and it passes this SMART test, you could put the disk back into your pool (replace the disk with itself, essentially) and keep an eye on it.

 

[Ericloewe]

Is the drive still in warranty? If so, RMA it while you can.

 

[George51]

Is the drive still in warranty? If so, RMA it while you can.

Didn't think it would be - turns out it is. Just created a RMA request with WD, will take it out and post it off tomorrow. Don't have a spare to put in during the meantime - will I be okay running in a degraded state? Could potentially be some time before they send me a new one I guess.

 

[danb35]

Don't have a spare to put in during the meantime - will I be okay running in a degraded state?

You should, but can't you get WD to advance RMA the drive? Send out the replacement, and you send in the bad one when you get it?

 

[Chris Moore]

will I be okay running in a degraded state?

Since it is RAID-z2, you still have another parity disk. If it were me, I would get a replacement either by advanced RMA like @danb35 suggested, or purchase one. I know that I am overly cautious though. When the warranty replacement gets back, run a burn-in test on it and set it aside as a spare. The hours on this drive make it appear to be about 2.5 years old, and as your array gets older, it will be a good thing to have a spare ready to go. I don't know where in the world you are, here in the US though, WD gets the replacement drive back pretty quick. For me, a little more than a week. Your results may vary.