2 Currently unreadable (pending) sectors

[Woscostametaxa]

Hi, I was trying to completely wipe my 4 x 3 tb raidz2, installed 4 more disks, and wanted to make a 8x3tb raidz2 volume.
but ada1 has unreadable sectors.

Code:

ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x002f   100   253   051	Pre-fail  Always	   -	   0		
  3 Spin_Up_Time			0x0027   187   183   021	Pre-fail  Always	   -	   5608	
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   24	  
  5 Reallocated_Sector_Ct   0x0033   200   200   140	Pre-fail  Always	   -	   0		
  7 Seek_Error_Rate		 0x002e   001   001   000	Old_age   Always	   -	   65535	
  9 Power_On_Hours		  0x0032   100   100   000	Old_age   Always	   -	   38	  
 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	   -	   24	  
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   18	  
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   10	  
194 Temperature_Celsius	 0x0022   115   113   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	   -	   2		
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 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%		 0		 96													

so for what I have already gathered sector 96 is the first erroneous sector; https://dekoder.wordpress.com/2014/10/08/fixing-freenas-currently-unreadable-pending-sectors-error/ shows me which command i should use, but I think that may be faulty?

Code:

dd if=/dev/zero of=/dev/ada1 bs=96 count=1 seek= conv=noerror,sync

shouldn't seek be 96 in my regard, and bs probably 512?

Any help greatly appreciated, I did search around the forums, but other than "do a full wipe" or "rewrite that sector" without the commands - if I didn't see something blatantly obvious, I apologize in advance.

kind regards

 

[melloa]

If you are wiping the pool and adding 4 new HDs, why not just remove that HD from the mix? Do you trust it to continue using for your data?

 

[Woscostametaxa]

Thanks for the response: my question is: should i already send it back to WD before building the new pool?

I do not know if 2 non readable sectors would warrant RMA with WD?

From what I've read here on the forums the chance of failure would be statistically higher if I keep it, although because i plan on building a raid z2 i thought it would be ok as long as i keep smart testing.

From https://forums.freenas.org/index.php?threads/1-currently-unreadable-pending-sectors.10213/ : "IMHO 1 unreadable sector is not a reason to replace a HDD, if you are running with double redundancy I would just fix the problem wthout even effecting uptime. I fixed this problem without having to replace the HDD (though I did order a spare immediately cause I was scared of the unknown), and the HDD runs just fine now."

 

[danb35]

You have a brand new drive that's already failing SMART tests. One or two pending sectors isn't (IMO) grounds to replace a drive, but failing SMART tests are. Return it to the vendor for a new replacement.

 

[Woscostametaxa]

Sorry i forgot to clarify: the erroneous drive is one of my older ones, not one of the newly bought WDs.

Excerpt from log:

Code:

=== START OF READ SMART DATA SECTION ===																							
SMART overall-health self-assessment test result: PASSED																			

I'll attach the whole log to clarify

 

[joeschmuck]

You have 38 hours on this hard drive and have failed the Extended Test. I would first try to swap this out with whomever you purchased this drive with prior to doing an RMA, since it appears you just bought it. If that can't be done, RMA the drive. Remember, an RMA drive isn't always a new drive, it could be just re-certified.

 

[joeschmuck]

Another thought, if you can't swap it for another drive wherever you purchased it from, run badblocks on the drive a few times and see what happens. The drive may remap the failed sectors and you may be good to go, then just keep an eye on the drive by running routine SMART tests (once a week Long Test) and if anything changes like Pending Sector Count (refer to the Hard Drive Troubleshooting Guide in my signature) or any other values, then RMA the drive. With WD you can do an Advance RMA where they will ship you a replacement drive in advance of you shipping the failed drive back to them.

 

[melloa]

With WD you can do an Advance RMA where they will ship you a replacement drive in advance of you shipping the failed drive back to them.

Good to know. Thanks for the tip!

 

[danb35]

the erroneous drive is one of my older ones, not one of the newly bought WDs.

I can't say how long ago you bought it, but per the data you posted in your OP, that drive has only been powered on for 38 hours. If you bought it and just kept it in a box, that would explain it, but it is effectively a brand new drive.

 

[danb35]

With WD you can do an Advance RMA where they will ship you a replacement drive in advance of you shipping the failed drive back to them.

Well, with WD in America, anyway. @Woscostametaxa is in Austria, so things might be different there.

 

[joeschmuck]

Well, with WD in America, anyway. @Woscostametaxa is in Austria, so things might be different there.

I didn't notice it. Thanks for noticing it.

 

[danb35]

What I remember hearing (mostly here) about European consumer protection laws is that the retailer is on the hook for any warranty needs, which could well get OP a new drive rather than a refurb.

 

[Chris Moore]

Good to know. Thanks for the tip!

They want your credit card info to do that, so you do need to ship the bad drive back quickly or risk getting a charge.

 

[Chris Moore]

Hi, I was trying to completely wipe my 4 x 3 tb raidz2, installed 4 more disks, and wanted to make a 8x3tb raidz2 volume.
but ada1 has unreadable sectors.

Code:

ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x002f   100   253   051	Pre-fail  Always	   -	   0		
  3 Spin_Up_Time			0x0027   187   183   021	Pre-fail  Always	   -	   5608	
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   24	 
  5 Reallocated_Sector_Ct   0x0033   200   200   140	Pre-fail  Always	   -	   0		
  7 Seek_Error_Rate		 0x002e   001   001   000	Old_age   Always	   -	   65535	
  9 Power_On_Hours		  0x0032   100   100   000	Old_age   Always	   -	   38	 
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	   -	   24	 
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   18	 
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   10	 
194 Temperature_Celsius	 0x0022   115   113   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	   -	   2		
198 Offline_Uncorrectable   0x0030   100   253   000	Old_age   Offline	  -	   0		
200 Multi_Zone_Error_Rate   0x0008   200   200   000	Old_age   Offline	  -	   1		

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%		 0		 96													

Any help greatly appreciated, I did search around the forums, but other than "do a full wipe" or "rewrite that sector" without the commands - if I didn't see something blatantly obvious, I apologize in advance.

kind regards

I would like to point you at the attributes (copied above for reference) you posted.
See the one called, " 9 Power_On_Hours"; that tells you that the drive has only been in service for 38 hours. That is less than a week.
See the one called, " 12 Power_Cycle_Count"; that tells you that the drive has only been powered off and on again 24 times. Reboots don't normally count as a power cycle.
Both of these are VERY low numbers for a drive to be exhibiting errors of any kind. Normally, when you write to a pending sector, it gets reallocated. That would increase the count on the reallocated sectors and reduce the count on the pending sectors. The problem is, for a drive this young, you shouldn't have any. It is my experience that a drive that begins exhibiting errors at this early stage is doomed to die of what I call SIDS. It would be my suggestion that you follow the advice of the other posters and get this drive replaced by what ever means possible.

The most important 5 of those stats to look at when determining drive health are as follows:
5 – Reallocated_Sector_Count.
187 – Reported_Uncorrectable_Errors.
188 – Command_Timeout.
197 – Current_Pending_Sector_Count.
198 – Offline_Uncorrectable.

As a side note, I sold it on eBay, but I did have a Western Digital drive with 38000 hours that had 0, absolutely no, errors.

 

[melloa]

They want your credit card info to do that, so you do need to ship the bad drive back quickly or risk getting a charge.

That's normal. When you get a replacement from, let's say Amazon, they put a pending change on your credit card in case you won't return the defective item. Thanks for the tip!

 

[Chris Moore]

Just for reference, I will put up the stats from one of my drives.

Code:

########## SMART status report for da10 drive ( Seagate Barracuda 7200.14 ) ##########
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)

SMART overall-health self-assessment test result: PASSED

ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x000f   105   099   006	Pre-fail  Always	   -	   8033064
  3 Spin_Up_Time			0x0003   096   096   000	Pre-fail  Always	   -	   0
  4 Start_Stop_Count		0x0032   060   060   020	Old_age   Always	   -	   41249
  5 Reallocated_Sector_Ct   0x0033   100   100   010	Pre-fail  Always	   -	   0
  7 Seek_Error_Rate		 0x000f   081   060   030	Pre-fail  Always	   -	   130073938
  9 Power_On_Hours		  0x0032   085   085   000	Old_age   Always	   -	   13204
10 Spin_Retry_Count		0x0013   100   100   097	Pre-fail  Always	   -	   0
12 Power_Cycle_Count	   0x0032   100   100   020	Old_age   Always	   -	   61
183 Runtime_Bad_Block	   0x0032   100   100   000	Old_age   Always	   -	   0
184 End-to-End_Error		0x0032   100   100   099	Old_age   Always	   -	   0
187 Reported_Uncorrect	  0x0032   100   100   000	Old_age   Always	   -	   0
188 Command_Timeout		 0x0032   100   100   000	Old_age   Always	   -	   0 0 0
189 High_Fly_Writes		 0x003a   094   094   000	Old_age   Always	   -	   6
190 Airflow_Temperature_Cel 0x0022   070   062   045	Old_age   Always	   -	   30 (0 54 32 25 0)
191 G-Sense_Error_Rate	  0x0032   100   100   000	Old_age   Always	   -	   0
192 Power-Off_Retract_Count 0x0032   100   100   000	Old_age   Always	   -	   36
193 Load_Cycle_Count		0x0032   067   067   000	Old_age   Always	   -	   66465
194 Temperature_Celsius	 0x0022   030   040   000	Old_age   Always	   -	   30 (128 0 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000	Old_age   Always	   -	   0
198 Offline_Uncorrectable   0x0010   100   100   000	Old_age   Offline	  -	   0
199 UDMA_CRC_Error_Count	0x003e   200   200   000	Old_age   Always	   -	   0
240 Head_Flying_Hours	   0x0000   100   253   000	Old_age   Offline	  -	   12843h+15m+06.314s
241 Total_LBAs_Written	  0x0000   100   253   000	Old_age   Offline	  -	   15039975021
242 Total_LBAs_Read		 0x0000   100   253   000	Old_age   Offline	  -	   68444692485

No Errors Logged

Test_Description	Status				  Remaining  LifeTime(hours)  LBA_of_first_error
Extended offline	Completed without error	   00%	 13199		 -

 

[Woscostametaxa]

Thank you all for the replies; once again I was fooled by one of the biggest problems in IT; I assumed stuff; my asrock board has 2x sata3, 2x sata3 with some hw-raid chipset and 4 x sata2.

I tried to hook the old drives to what i assumed where the first 4 ports, according to UEFI listing that would have been sata3_1 sata_3_2 sata2_3 sata2_4; appearently probably the sata with the raid chipset are then the first ones; is there a way in the client UI or via command line to get the name of the sata port? because i really want to set them up from top to bottom; or should I always place the Serial on the front (or rather the side) of the plugable bay? Thank god that I didn't cheap out on the case...

Although I have used freenas now for a good two years, with this expansion shows that I still have quite a few things to learn, so again, thanks for all the information and input this far!

 

[melloa]

Although I have used freenas now for a good two years, with this expansion shows that I still have quite a few things to learn, so again, thanks for all the information and input this far!

For future plans, try to do some reading on controllers. I just re-flash some M1015 to stop using the 10 SATA ports on my ASRock and noticed a huge increase in performance. One card can give you 8 SATA ports. There are others as mentioned in the Resources session (see link at header of the page) and some won't even require you play with flashing it.