SOLVED Unreadable pending sectors on both drives in a mirror?

Status
Not open for further replies.

SRSR333

Dabbler
Joined
Aug 17, 2016
Messages
38
Hello everyone...

I recently noticed that one of my drives, /dev/ada1, has been compromised with a bad block, and the console is emitting 1 Currently unreadable (pending) sectors messages every half an hour. Reading through, I ran smartctl -t long /dev/ada1. Following is the output of smartctl -a /dev/ada1:

Code:
root@freenas:~ # smartctl -a /dev/ada1
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:	***REDACTED***
LU WWN Device Id: 5 0014ee 20d75626d
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:	Tue Jul  4 17:20:01 2017 +08
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:				(39900) 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:		( 400) 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	   -	   132
  3 Spin_Up_Time			0x0027   192   180   021	Pre-fail  Always	   -	   5400
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   134
  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   092   092   000	Old_age   Always	   -	   6315
 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	   -	   134
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   121
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   717
194 Temperature_Celsius	 0x0022   115   104   000	Old_age   Always	   -	   35
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   100   253   000	Old_age   Offline	  -	   0

SMART Error Log Version: 1
ATA Error Count: 21 (device log contains only the most recent five errors)
		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 21 occurred at disk power-on lifetime: 6294 hours (262 days + 6 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
  -- -- -- -- -- -- --
  40 51 00 70 0c 04 46  Error: UNC at LBA = 0x06040c70 = 100928624

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 b8 0b 04 46 08	  04:31:07.269  READ DMA
  c8 00 00 b8 0b 04 46 08	  04:31:03.274  READ DMA

Error 20 occurred at disk power-on lifetime: 6294 hours (262 days + 6 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
  -- -- -- -- -- -- --
  40 51 00 70 0c 04 46  Error: UNC at LBA = 0x06040c70 = 100928624

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 b8 0b 04 46 08	  04:31:03.274  READ DMA

Error 19 occurred at disk power-on lifetime: 6251 hours (260 days + 11 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
  -- -- -- -- -- -- --
  40 51 00 70 0c 04 46  Error: UNC at LBA = 0x06040c70 = 100928624

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 b8 0b 04 46 08  14d+00:28:29.348  READ DMA
  c8 00 00 b8 0b 04 46 08  14d+00:28:25.341  READ DMA
  c8 00 00 b8 0b 04 46 08  14d+00:28:21.356  READ DMA
  c8 00 00 b8 0b 04 46 08  14d+00:28:17.348  READ DMA

Error 18 occurred at disk power-on lifetime: 6251 hours (260 days + 11 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
  -- -- -- -- -- -- --
  40 51 00 70 0c 04 46  Error: UNC at LBA = 0x06040c70 = 100928624

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 b8 0b 04 46 08  14d+00:28:25.341  READ DMA
  c8 00 00 b8 0b 04 46 08  14d+00:28:21.356  READ DMA
  c8 00 00 b8 0b 04 46 08  14d+00:28:17.348  READ DMA

Error 17 occurred at disk power-on lifetime: 6251 hours (260 days + 11 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
  -- -- -- -- -- -- --
  40 51 00 70 0c 04 46  Error: UNC at LBA = 0x06040c70 = 100928624

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 b8 0b 04 46 08  14d+00:28:21.356  READ DMA
  c8 00 00 b8 0b 04 46 08  14d+00:28:17.348  READ DMA

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%	  6311		 100928624
# 2  Extended offline	Completed: read failure	   90%	  6273		 100928625
# 3  Conveyance offline  Completed without error	   00%		31		 -
# 4  Conveyance offline  Completed without error	   00%		 4		 -
# 5  Short offline	   Completed without error	   00%		 4		 -

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.


The odd thing is that the other disk in the mirrored vdev, /dev/ada0, is perfectly fine (i.e. no errors logged) after also having run the SMART long test, and yet also has a pending sector:
Code:
root@freenas:~ # smartctl -a /dev/ada0										  
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:	***REDACTED***
LU WWN Device Id: 5 0014ee 262cad5a5
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:	Tue Jul  4 17:25:20 2017 +08
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:				(38940) 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:		( 391) 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	   -	   24
  3 Spin_Up_Time			0x0027   190   178   021	Pre-fail  Always	   -	   5458
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   134
  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   092   092   000	Old_age   Always	   -	   6315
 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	   -	   134
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   121
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   716
194 Temperature_Celsius	 0x0022   114   104   000	Old_age   Always	   -	   36
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	  -	   15

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%	  6308		 -
# 2  Extended offline	Completed without error	   00%	  6280		 -
# 3  Short offline	   Completed without error	   00%		31		 -
# 4  Conveyance offline  Completed without error	   00%		31		 -
# 5  Short offline	   Completed without error	   00%		 4		 -
# 6  Conveyance offline  Completed without error	   00%		 4		 -
# 7  Short offline	   Completed without error	   00%		 4		 -

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.


What gives? By most measures, these drives are very new—I've got a seven-year-old Seagate 1 TB HDD in an old desktop that's still whirring along perfectly fine, and that desktop has been switched on nearly every day. RMAs will also likely be a pain in the neck for me given that I bought the drives on Amazon, but don't live in the US. Speaking of which—could the high temperatures in my tropical country have contributed to this (the drives rarely, but do hit 40–45 degrees C)? How do I know my drives are truly failing, and it isn't just a bit of corrupt data?

Thanks in advance.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Couple issues here. ada1 needs to be replaced ASAP. That drive is in bad shape and can't even complete a smart test. ada0 also needs to be replaced but you need to address ada1 first.

Next you don't have periodic smart tests running. If you had you would have been warned much sooner that something is amiss. I hope you have a backup of your data.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
The single pending sector on each disk is, in each case, the least of your problems. ada1, especially, has lots of stuff going on and should be RMA'd.
 

SRSR333

Dabbler
Joined
Aug 17, 2016
Messages
38
ada1, especially, has lots of stuff going on and should be RMA'd.
Darn... What do you mean by 'has lots of stuff going on'? Furthermore, if I RMA either (or both) drives, would I get a brand new one, or a refurb one that has possibly already been used?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
# 1 Extended offline Completed: read failure 90% 6311 100928624
# 2 Extended offline Completed: read failure 90% 6273 100928625
It's easy to see things are wrong. Check it the smart tests that are failing.

Sent from my Nexus 5X using Tapatalk
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Darn... What do you mean by 'has lots of stuff going on'?
Raw read error rate, lots of SMART errors, failing SMART self-tests. A single pending sector wouldn't worry me much, but that disk needs replacement.
Furthermore, if I RMA either (or both) drives, would I get a brand new one, or a refurb one that has possibly already been used?
In the US, you'd likely get a refurbished drive. Might be different in .sg.
 

SRSR333

Dabbler
Joined
Aug 17, 2016
Messages
38
Alright—let's say I replace ada1 with a new drive; would the bad bit be copied over from ada0 during resilvering? Or not, and I can go ahead and replace the drive as usual?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Alright—let's say I replace ada1 with a new drive; would the bad bit be copied over from ada0 during resilvering? Or not, and I can go ahead and replace the drive as usual?
No bad bits exist yet and if they did you could not copy them over, your missing some understanding of how things work but that's ok for now. But there is a good chance ada0 will fail during the resilver. Make sure your backup is up to date.

Sent from my Nexus 5X using Tapatalk
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
would the bad bit be copied over from ada0 during resilvering? Or not, and I can go ahead and replace the drive as usual?
Go ahead and replace the drive as usual. The fact that there's a bad sector doesn't mean that there's data on that sector.

Edit: If you can "advance exchange" the drive (i.e., get the replacement drive before returning your old drive), you can replace the failing drive without removing it. That will keep the failing drive online until the replacement process is finished, so you'll never lose redundancy.

Edit 2: Be sure to thoroughly burn in and test the replacement drive before adding it to your pool.
 

SRSR333

Dabbler
Joined
Aug 17, 2016
Messages
38
@Jailer, @danb35 and @SweetAndLow, thank you for your replies. I've shut down the NAS for now so that neither drive goes through more stress. Meanwhile, I've asked WD to convert my American warranty to a Singapore one, so that I can get an advance replacement, like @danb35 suggested, and so that my RMA is processed faster. Hopefully I get a new drive.
 

SRSR333

Dabbler
Joined
Aug 17, 2016
Messages
38
I thought I ought to wrap up this thread...

I RMAed the questionable drive, got a recertified one in return, and it's now whirring away happily in my NAS. Hopefully nothing else suspect appears.
 
Status
Not open for further replies.
Top