Disk has 6 currently unreadable (pending) sectors

[marcevan]

After booting up my FreeNAS about 2 weeks after a house move I find this:

Code:

CRITICAL: Nov. 20, 2017, 8:07 p.m. - Device: /dev/ada4, 6 Currently unreadable (pending) sectors

Tracing an earlier thread I did a long test on ada4 then issuing smartctl -A /dev/ada4:

Code:

Extended self-test routine																										 
recommended polling time:		( 417) 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	   -	   90										   
  3 Spin_Up_Time			0x0027   196   174   021	Pre-fail  Always	   -	   5200										 
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   22										   
  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   056   056   000	Old_age   Always	   -	   32787										
 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	   -	   22										   
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   17										   
193 Load_Cycle_Count		0x0032   001   001   000	Old_age   Always	   -	   1001282									 
194 Temperature_Celsius	 0x0022   113   105   000	Old_age   Always	   -	   37										   
196 Reallocated_Event_Count 0x0032   200   200   000	Old_age   Always	   -	   0											
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -	   6											
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	  -	   6											
																																   
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%	 32460		 -													 
																																   
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.

But in that thread about doing a DD to force write to those sectors, there is an omitted 'X' of where to find it.

 

[rs225]

This may be a little more than just some pending sectors. You also have raw read error rate, and multi-zone error rate.

Run a SMART short test and see if it passes.

 

[joeschmuck]

First I will tell you not to worry about this yet. Just let your system run normally. I suspect that you have routine SMART tests running.

You just moved this system and had it down for about 2 weeks. This in itself isn't an issue however if your system was running a scrub and a long test at the same time that could cause an issue like this. I speak from personal experience.

What I'd do it let it run for 1 week and then power off the machine and power it back on. I want your hard drives to have power removed from them, that is the goal. Next look at the SMART data and see if the multizone and pending sector errors start to drop away or if they start going up. The big warning is if you start getting ID 5 Reallocated Sectors popping up. Under 5 is okay in my book for this problem but if they continue to grow then I'd replace the hard drive.

Keep in mind that ID 197 and 200 can clear back to a zero value so I wouldn't recommend an RMA at this point. If you are close to the warranty expiring then I'd run a scrub and long test several times or you could run badblocks in the non-destructive mode. You got a RAIDZ2 so that should give you some confidence as well.

EDIT: Yowser! Did you see ID 193, over one million cycles! If this is a WD drive then I'd recommend changing the head parking timer to 5 minutes. I'm impressed.

 

[Jailer]

I'm a bit more skeptical. You have 6 pending sectors, you're not running regular smart tests and your head park's are off the chart. I'd have a replacement drive at the ready if it were me.

Get regular smart tests running on all your drives and keep a real close eye on ada4.

 

[rs225]

Good catch on the head parking, but I think we've seen one at 2.5 million (at least over 2) before. :)

 

[joeschmuck]

you're not running regular smart tests

Dang, I missed that. Only one SMART test, when it failed. But I'll still stick with my advice for now. If you find out the drive is faulty then you can shut the system down and wait on a new drive fi you like.

Get regular smart tests running on all your drives and keep a real close eye on ada4.

Agreed.

 

[marcevan]

Thanks gents. Now for the age old question... how do I know which drive (e.g., ada4) corresponds to which physical drive on the FreeNAS?

I rackmounted the FreeNAS so will have to power down, remove and replace one drive at a time. I have mostly 3TB drives and 1 4TB drive, so serially replacing one 3TB with a 4TB shouldn't be that painful since I can offline one, remove it, plug in new one, and online replace and resilver each 4TB 1 at a time.

 

[danb35]

how do I know which drive (e.g., ada4) corresponds to which physical drive on the FreeNAS?

https://forums.freenas.org/index.php?resources/identify-your-drives-by-serial-number.64/

Edit: Or, alternatively: https://forums.freenas.org/index.ph...ktype-serial-num-multipath.59319/#post-420401

 

[marcevan]

Damn wish the plugin updates didn't stick at 50% for 10 minutes and are modal. Plugin updates should be moved to background tasks so I can do something else while they work. Waiting for latest Plex update to complete so I can even open a window

 

[marcevan]

Can I get some commands to do smartctl tests or adjust line 193? Not a good coder so freenas is rough on me.

 

[danb35]

For the load cycle count, Google WDIDLE3.EXE. For the SMART tests, smartctl -t long /dev/whatever (or -t short, if you prefer).

 

[captclearleft]

I know this is old, but...
I have the same issue. Thinking it's time I change out this drive.
If someone can read this short test, and tell me their thoughts - I'de greatly appreciate it.

 

[danb35]

Your disk is failing SMART tests. Time to replace it.

 

[danb35]

@joeschmuck, I was looking for your disk troubleshooting guide to link here--isn't it in the Resources section?

 

[joeschmuck]

@danb35, yes it's on the bottom of the second page of the resources right now. It seems to move around. I haven't updated it in a long time but I think it still holds it's own, but I'm open to review any updates someone wants to send me. I it linked in my signature. Thanks or thinking about it.