SOLVED Pending sector

[Jacopx]

Buongiorno a tutti! ;)

I have a problem with a disk of my RAID-Z2, are some months the there are 5 pending sectors and I have tried to solve this problem in several ways but without success. This are the SMART results:

Code:

smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-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-WCC4N5FYYJZU
LU WWN Device Id: 5 0014ee 2b7e44ae6
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: 3.0 Gb/s)
Local Time is:	Thu Apr 27 13:55:01 2017 CEST
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:		 (39600) 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:	 ( 398) 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   191   191   051	Pre-fail  Always	   -	   107386
  3 Spin_Up_Time			0x0027   178   176   021	Pre-fail  Always	   -	   6066
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   309
  5 Reallocated_Sector_Ct   0x0033   161   161   140	Pre-fail  Always	   -	   1170
  7 Seek_Error_Rate		 0x002e   200   200   000	Old_age   Always	   -	   0
  9 Power_On_Hours		  0x0032   096   096   000	Old_age   Always	   -	   3493
 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	   -	   285
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   35
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   548
194 Temperature_Celsius	 0x0022   123   115   000	Old_age   Always	   -	   27
196 Reallocated_Event_Count 0x0032   170   170   000	Old_age   Always	   -	   30
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -	   5
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   186   180   000	Old_age   Offline	  -	   5730

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%	  3255		 -
# 2  Short offline	   Completed without error	   00%	  3236		 -
# 3  Short offline	   Completed without error	   00%	  3216		 -
# 4  Short offline	   Completed without error	   00%	  3192		 -
# 5  Short offline	   Completed without error	   00%	  3191		 -
# 6  Short offline	   Completed without error	   00%	  3173		 -
# 7  Short offline	   Completed without error	   00%	  3160		 -
# 8  Short offline	   Completed: read failure	   10%	  3144		 1400349888
# 9  Short offline	   Completed: read failure	   10%	  3142		 1400349888
#10  Short offline	   Completed: read failure	   10%	  3127		 1400349888
#11  Short offline	   Completed without error	   00%	  3113		 -
#12  Short offline	   Completed: read failure	   10%	  3098		 1400349888
#13  Short offline	   Completed without error	   00%	  3079		 -
#14  Short offline	   Completed without error	   00%	  3061		 -
#15  Short offline	   Completed: read failure	   10%	  3037		 1400349888
#16  Extended offline	Completed: read failure	   10%	  2938		 1400349888
#17  Extended offline	Completed: read failure	   10%	  2868		 1400349888
#18  Short offline	   Completed: read failure	   10%	  2859		 1400349888
#19  Extended offline	Completed: read failure	   10%	  2850		 1400349888
#20  Short offline	   Interrupted (host reset)	  90%	  2826		 -
#21  Extended offline	Completed: read failure	   10%	  2820		 1400225496

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.

Some one can help me? I already have a new disk for the substitution but I want't to use the one that il already online but with errors.

 

[wblock]

Pending sector is not the real problem there, but #5, the reallocated sector count of 1170. It's amazing that disk works at all. I think that is the highest number I've ever seen there. Please replace it immediately. If you think it can still be used, please don't test that with your NAS data. Replace it and test it separately.

 

[Jacopx]

Pending sector is not the real problem there, but #5, the reallocated sector count of 1170. It's amazing that disk works at all. I think that is the highest number I've ever seen there. Please replace it immediately. If you think it can still be used, please don't test that with your NAS data. Replace it and test it separately.

Owww DAMN... I have only focused my attention on the pending sectors. The Notification Center have only show to me that problem!

 

[Vito Reiter]

The point of redundancy is so when those errors come up you can just replace the disk. There's not much of a reason to sit around and try to see if you can unfail the drive, you have a RaidZ2 for that reason. Make sure if you get a disk to replace it, it's either the same exact WD Red 3TB or a disk greater than 3TB.

 

[Robert Trevellyan]

the same exact WD Red 3TB

Why?

Any 3TB or greater disk will work. It should, of course, be a NAS disk.

 

[Jacopx]

The point of redundancy is so when those errors come up you can just replace the disk. There's not much of a reason to sit around and try to see if you can unfail the drive, you have a RaidZ2 for that reason. Make sure if you get a disk to replace it, it's either the same exact WD Red 3TB or a disk greater than 3TB.

Yeah yeah, of course, I`m using redundancy for that reason, as soon as I can I will replace the disk (I'm away from home)

Is the first disk that I'm replacing, it could be useful to put it offline until I'm back home? When I will be at home must select the disk and click REPLACE I think and the resilvering will automatically start?

 

[Vito Reiter]

Yeah, that's correct, as for offlining it until your home I can't recommend anything. Usually, as soon as I notice a bad disk I replace it. However, it might be a good idea to make sure no data gets corrupted on the disk level of things.

Edit: As for why it should be the same model if a 3TB disk - Just to make sure resilvering doesn't fail if the new disk is somehow too small.

 

[wblock]

A disk that is too small will not be allowed as a replacement. It won't get to the point of resilvering.

 

[danb35]

As for why it should be the same model if a 3TB disk - Just to make sure resilvering doesn't fail if the new disk is somehow too small.

1. As @wblock says, ZFS will refuse the replacement if the replacement disk is too small--it won't try to resilver, and then fail out hours later.
2. If the replacement disk were slightly too small, you could still use it by adjusting the size of the swap partition (which is the main reason that the swap partitions are created in the first place).
3. Disk capacities have been, for some years, standardized across manufacturers. Any manufacturer's 3 TB disk will have exactly the same capacity as any other manufacturer's.

 

[Vito Reiter]

Sorry, to start I didn't mean hours then fail I simply meant not work. The only reason I brought it up is because it happened to me replacing a drive with another 1.0TB drive and it didn't work. It's really not a big deal just a good practice I like to follow now. Thanks for roasting me though, guys! lol

 

[Robert Trevellyan]

Thanks for roasting me though

Just trying to keep questionable advice to a minimum. Oversimplification is ultimately unhelpful. Remember, it's not just the OPs who read these threads.

 

[Jacopx]

yeah yeah, I know what it means if I'm trying to put a smaller this, don't kill each other! :P

 

[Jacopx]

I'm resilvering my Pool ;)

 

[Stux]

And if it's in warranty you can RMA it.

For future reference, there's no point offlining the drive if it's still responsive. It's still providing redundancy to *most* sectors in your pool.

 

[Jacopx]

And if it's in warranty you can RMA it.

For future reference, there's no point offlining the drive if it's still responsive. It's still providing redundancy to *most* sectors in your pool.

Ok, I'll remember it for the next time.

The resilvering is completed without error and my system is back to 100% of power! Thanks everyone.