Failing Hard Drive? Data Scrub Stuck?

Status
Not open for further replies.

NightNetworks

Explorer
Joined
Sep 6, 2015
Messages
61
So I received an e-mail alert from FreeNAS Indicating the following...

"Device: /dev/ada1, 1 Currently unreadable (pending) sectors"

Connected to the FreeNAS and found that of course it was alerting to what appears to be a single bad sector on one of the hard disks? I went ahead and kicked off a data scrub for that volume (which was around 12 noon today and 9 hours later it is still running... Is it possible that the scrub is stuck? Do I need to do something about the scrub or can I just let it ride?

Connected to the FreeNAS via SSH and ran the following CMD "smartctl -a /dev/ada1" here is the output of that...

Code:
=== START OF INFORMATION SECTION ===
Model Family:	 Western Digital Red
Device Model:	 WDC WD30EFRX-68EUZN0
Serial Number:	WD-WCC4N3SRE9CH
LU WWN Device Id: 5 0014ee 20bdcac3e
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 Dec 15 21:03:05 2016 CST
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:				(39840) 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:		( 399) 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	   -	   22
  3 Spin_Up_Time			0x0027   180   179   021	Pre-fail  Always	   -	   5966
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   38
  5 Reallocated_Sector_Ct   0x0033   200   200   140	Pre-fail  Always	   -	   0
  7 Seek_Error_Rate		 0x002e   100   253   000	Old_age   Always	   -	   0
  9 Power_On_Hours		  0x0032   085   085   000	Old_age   Always	   -	   11166
 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	   -	   38
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   21
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   90
194 Temperature_Celsius	 0x0022   123   117   000	Old_age   Always	   -	   27
196 Reallocated_Event_Count 0x0032   200   200   000	Old_age   Always	   -	   0
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -	   1
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	  -	   0

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  Short offline	   Completed without error	   00%	 11121		 -
# 2  Extended offline	Completed without error	   00%	 11080		 -
# 3  Short offline	   Completed without error	   00%	 10953		 -
# 4  Short offline	   Completed without error	   00%	 10737		 -
# 5  Extended offline	Completed without error	   00%	 10649		 -
# 6  Short offline	   Completed without error	   00%	 10569		 -
# 7  Short offline	   Completed without error	   00%	 10402		 -
# 8  Extended offline	Completed without error	   00%	 10361		 -
# 9  Short offline	   Completed without error	   00%	 10234		 -
#10  Short offline	   Completed without error	   00%	  9993		 -
#11  Extended offline	Completed without error	   00%	  9905		 -
#12  Short offline	   Completed without error	   00%	  9825		 -
#13  Short offline	   Completed without error	   00%	  9658		 -
#14  Extended offline	Completed without error	   00%	  9618		 -
#15  Short offline	   Completed without error	   00%	  9490		 -
#16  Short offline	   Completed: read failure	   10%	  9274		 18207624
#17  Extended offline	Completed: read failure	   90%	  9178		 18207624
#18  Short offline	   Completed: read failure	   10%	  9106		 18207624
#19  Short offline	   Completed: read failure	   10%	  8938		 18207624
#20  Extended offline	Completed: read failure	   90%	  8890		 18207624
#21  Extended offline	Completed: read failure	   90%	  8790		 18207624
6 of 6 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.

[root@freenas] ~#



Looks like the drive has failed SMART testing 6 of the 21 times that are listed in the log.... I also ran "smartctl _H /dev/ada1" and that indicated that the SMART overall-healh self-assessment test result was PASSED.

Also the console view from the GUI has this same line repeated a lot...

Code:
Dec 15 18:03:46 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 18:33:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 18:33:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 19:03:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 19:03:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 19:33:46 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 19:33:46 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 20:03:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 20:03:46 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 20:33:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 20:33:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 21:03:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Dec 15 21:03:45 freenas smartd[81640]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors


It would appear that the drive has unreadable sectors that are making it fail SMART quick and long tests, but that the overall health of the drive is listed as PASSED.... Drive is still under warranty and its a WD RED drive so I am going to RMA it, but did find the above kinda odd. This is actually the 2nd drive WD RED Drive (1st one was in an ESXi Host) that I have had with unreadable sectors that still passed SMART health readings. Anyone else find this issue? Also what about this scrub that appears to be stuck?

Thanks!
 

NightNetworks

Explorer
Joined
Sep 6, 2015
Messages
61
Also I was checking the other drives they all look good except for one that is displaying the following...

Code:
SMART Error Log Version: 1
ATA Error Count: 1
		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 1 occurred at disk power-on lifetime: 5 hours (0 days + 5 hours)
  When the command that caused the error occurred, the device was active or idle																													 .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 01 00 00 00 a0  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d6 01 e0 4f c2 a0 00	  05:15:45.046  SMART WRITE LOG
  b0 d5 01 e0 4f c2 a0 00	  05:15:45.045  SMART READ LOG



What does that mean?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Get a new drive, burn that drive in and replace your failing drive. Your drive isn't completely dead yet since your pool isn't degraded but it's probably on its way out so I would be ready to replace it when it dies.

Sent from my Nexus 5X using Tapatalk
 

NightNetworks

Explorer
Joined
Sep 6, 2015
Messages
61
Thanks, I figured as much.

What about the hard drive that is displaying this error... (this is not the same drive that has the SMART error above) Does this drive need to be replaced as well or can this be ignored?

Code:
SMART Error Log Version: 1
ATA Error Count: 1
		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 1 occurred at disk power-on lifetime: 5 hours (0 days + 5 hours)
  When the command that caused the error occurred, the device was active or idle																													 .

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 01 00 00 00 a0  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d6 01 e0 4f c2 a0 00	  05:15:45.046  SMART WRITE LOG
  b0 d5 01 e0 4f c2 a0 00	  05:15:45.045  SMART READ LOG


Also what do I do about the data scrub? Do I need to stop it before replacing the drive?
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
This is actually the 2nd drive WD RED Drive (1st one was in an ESXi Host) that I have had with unreadable sectors that still passed SMART health readings. Anyone else find this issue?
Yes. I returned mine, because repeated writes to the bad sector succeeded, while reads continued to fail. I don't consider a sector that can be written to but not read from to be much use.

SMART checks report OK as long as no attribute has reached its threshold. SMART tests either pass or fail, and a single unreadable sector is enough for a test to fail.
 
Status
Not open for further replies.
Top