UI indicates bad blocks, but smartctl doesn't...?

Status
Not open for further replies.

digity

Contributor
Joined
Apr 24, 2016
Messages
156
The following errors are popping up in the FreeNAS UI:

CRITICAL: Dec. 30, 2017, 10:18 p.m. - Device: /dev/da2 [SAT], 1 Currently unreadable (pending) sectors
CRITICAL: Dec. 31, 2017, 5:21 a.m. - Device: /dev/da2 [SAT], ATA error count increased from 16 to 17

But after running a long SMART test (smartctl -t long /dev/da2), it passes, there's no bad blocks listed under LBA_of_first_error (nor Current_Pending_Sector) despite the results indicating 17 ATA errors like the UI did. I'd like to try resolving this and extend the life of this drive/pool by zeroing out the bad sector(s) - I'm experimenting here, the data isn't important. But is there really a critical error here? If so, how do I find the true bad sector(s) to zero out (or fix the true issue)??


Below is the output/results of the long SMART test.

Code:
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:	 Hitachi Ultrastar 7K3000
Device Model:	 Hitachi HUA723020ALA641
Serial Number:	XxXxXxXx
LU WWN Device Id: 5 000cca 223c47a86
Firmware Version: MK7OA840
User Capacity:	2,000,398,934,016 bytes [2.00 TB]
Sector Size:	  512 bytes logical/physical
Rotation Rate:	7200 rpm
Form Factor:	  3.5 inches
Device is:		In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Mon Jan  1 10:32:13 2018 PST
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:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
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:		 (20116) seconds.
Offline data collection
capabilities:			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No 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:	 (   1) minutes.
Extended self-test routine
recommended polling time:	 ( 336) minutes.
SCT capabilities:			(0x003d)	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	 0x000b   100   100   016	Pre-fail  Always	   -	   0
  2 Throughput_Performance  0x0005   132   132   054	Pre-fail  Offline	  -	   95
  3 Spin_Up_Time			0x0007   125   125   024	Pre-fail  Always	   -	   498 (Average 501)
  4 Start_Stop_Count		0x0012   100   100   000	Old_age   Always	   -	   120
  5 Reallocated_Sector_Ct   0x0033   100   100   005	Pre-fail  Always	   -	   0
  7 Seek_Error_Rate		 0x000b   100   100   067	Pre-fail  Always	   -	   0
  8 Seek_Time_Performance   0x0005   135   135   020	Pre-fail  Offline	  -	   26
  9 Power_On_Hours		  0x0012   100   100   000	Old_age   Always	   -	   5109
 10 Spin_Retry_Count		0x0013   100   100   060	Pre-fail  Always	   -	   0
 12 Power_Cycle_Count	   0x0032   100   100   000	Old_age   Always	   -	   120
192 Power-Off_Retract_Count 0x0032   100   100   000	Old_age   Always	   -	   146
193 Load_Cycle_Count		0x0012   100   100   000	Old_age   Always	   -	   146
194 Temperature_Celsius	 0x0002   171   171   000	Old_age   Always	   -	   35 (Min/Max 20/47)
196 Reallocated_Event_Count 0x0032   100   100   000	Old_age   Always	   -	   0
197 Current_Pending_Sector  0x0022   100   100   000	Old_age   Always	   -	   0
198 Offline_Uncorrectable   0x0008   100   100   000	Old_age   Offline	  -	   0
199 UDMA_CRC_Error_Count	0x000a   200   200   000	Old_age   Always	   -	   0

SMART Error Log Version: 1
ATA Error Count: 17 (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 17 occurred at disk power-on lifetime: 5080 hours (211 days + 16 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 01 9f aa 13 04  Error: UNC at LBA = 0x0413aa9f = 68397727

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 c0 08 00 ac 13 40 00	  06:34:44.262  READ FPDMA QUEUED
  60 00 00 00 ab 13 40 00	  06:34:44.262  READ FPDMA QUEUED
  60 e0 18 c0 a9 13 40 00	  06:34:44.259  READ FPDMA QUEUED
  60 a0 10 00 a7 13 40 00	  06:34:44.258  READ FPDMA QUEUED
  60 00 08 00 a6 13 40 00	  06:34:44.258  READ FPDMA QUEUED

Error 16 occurred at disk power-on lifetime: 31565 hours (1315 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
  -- -- -- -- -- -- --
  40 51 01 9f aa 13 04  Error: UNC at LBA = 0x0413aa9f = 68397727

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 01 9f aa 13 40 08	  00:00:44.037  READ VERIFY SECTOR(S) EXT
  ec 00 01 00 00 00 00 08	  00:00:44.034  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 08	  00:00:44.031  IDENTIFY DEVICE
  42 00 60 3f a2 13 40 08	  00:00:43.971  READ VERIFY SECTOR(S) EXT
  42 00 20 1f 54 13 40 08	  00:00:43.895  READ VERIFY SECTOR(S) EXT

Error 15 occurred at disk power-on lifetime: 31348 hours (1306 days + 4 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 51 9f aa 13 04  Error: UNC 81 sectors at LBA = 0x0413aa9f = 68397727

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 f0 a7 13 e0 08   1d+15:58:39.300  READ DMA EXT
  35 00 e0 30 36 e5 e0 08   1d+15:58:38.940  WRITE DMA EXT
  25 00 00 f0 a3 13 e0 08   1d+15:58:38.190  READ DMA EXT
  25 00 00 80 6f b2 e0 08   1d+15:58:38.166  READ DMA EXT
  25 00 00 80 6b b2 e0 08   1d+15:58:38.164  READ DMA EXT

Error 14 occurred at disk power-on lifetime: 29067 hours (1211 days + 3 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 01 9f aa 13 04  Error: UNC at LBA = 0x0413aa9f = 68397727

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 01 9f aa 13 40 08	  00:00:43.586  READ VERIFY SECTOR(S) EXT
  ec 00 01 00 00 00 00 08	  00:00:43.583  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 08	  00:00:43.580  IDENTIFY DEVICE
  42 00 60 3f a2 13 40 08	  00:00:43.538  READ VERIFY SECTOR(S) EXT
  42 00 20 1f 54 13 40 08	  00:00:43.462  READ VERIFY SECTOR(S) EXT

Error 13 occurred at disk power-on lifetime: 28991 hours (1207 days + 23 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 99 9f aa 13 04  Error: UNC 153 sectors at LBA = 0x0413aa9f = 68397727

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 38 aa 13 e0 08   3d+09:20:46.223  READ DMA EXT
  25 00 d8 50 d3 8f e0 08   3d+09:20:46.217  READ DMA EXT
  25 00 00 50 cf 8f e0 08   3d+09:20:46.199  READ DMA EXT
  25 00 10 a0 67 b3 e0 08   3d+09:20:46.184  READ DMA EXT
  25 00 08 10 b8 09 e0 08   3d+09:20:46.180  READ DMA EXT

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%	  5094		 -
# 2  Short offline	   Completed without error	   00%		 0		 -
# 3  Short offline	   Completed without error	   00%		 0		 -
# 4  Short offline	   Completed without error	   00%	 31749		 -
# 5  Short offline	   Completed without error	   00%	 31568		 -
# 6  Short offline	   Completed without error	   00%	 31565		 -
# 7  Short offline	   Completed without error	   00%	 29982		 -
# 8  Short offline	   Completed without error	   00%	 29067		 -
# 9  Short offline	   Completed without error	   00%	 25825		 -
#10  Short offline	   Completed without error	   00%	 25094		 -
#11  Short offline	   Completed without error	   00%	 24413		 -
#12  Short offline	   Completed without error	   00%	  9943		 -
#13  Short offline	   Completed without error	   00%		 8		 -

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.



P.S. - FreeNAS 11.1, 5x2x2TB mirror pool, 16GB USB boot, Supermicro X8DTL-i, dual XEON X5650 CPU, 48 GB DDR3 ECC registered RAM, LSI 9211-8i, Intel SAS Expander, Norco RPC-4224 24 bay 4U rackmount server case, Seasonic SSR-750FX 750W 80+ Gold PSU
 

garm

Wizard
Joined
Aug 19, 2017
Messages
1,556
It quite clearly states
Code:
Error 17 occurred at disk power-on lifetime: 5080 hours (211 days + 16 hours)
 


Those are read errors and should be corrected by ZFS for now. Do you have any error count on the drives in the storage view? Sins you run mirrors it could become an issue if you start having problems with it’s twin.

Also, you should schedule long smart tests as well
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
Can one of the SMART test-knowledgeable explain to me the LifeTime(hours) "reset" above #4 of the info below copied from the OP's test results?

I believe I have always seen an ascending column of increasing numbers - never one like this.

Code:
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%	  5094		 -
# 2  Short offline	   Completed without error	   00%		 0		 -
# 3  Short offline	   Completed without error	   00%		 0		 -
# 4  Short offline	   Completed without error	   00%	 31749		 -
# 5  Short offline	   Completed without error	   00%	 31568		 -
# 6  Short offline	   Completed without error	   00%	 31565		 -
# 7  Short offline	   Completed without error	   00%	 29982		 -
# 8  Short offline	   Completed without error	   00%	 29067		 -
# 9  Short offline	   Completed without error	   00%	 25825		 -
#10  Short offline	   Completed without error	   00%	 25094		 -
#11  Short offline	   Completed without error	   00%	 24413		 -
#12  Short offline	   Completed without error	   00%	  9943		 -
#13  Short offline	   Completed without error	   00%		 8		 -
 

digity

Contributor
Joined
Apr 24, 2016
Messages
156
It quite clearly states
Code:
Error 17 occurred at disk power-on lifetime: 5080 hours (211 days + 16 hours)
 


Those are read errors and should be corrected by ZFS for now. Do you have any error count on the drives in the storage view? Sins you run mirrors it could become an issue if you start having problems with it’s twin.

Also, you should schedule long smart tests as well
No errors reported in Storage View. How do I correct this issue in ZFS?

Sent from my SM-G955U using Tapatalk
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977

garm

Wizard
Joined
Aug 19, 2017
Messages
1,556
No, you don’t do anything to correct it. ZFS should see that the wrong value is being read and correct it. You just replace the drive
 

rs225

Guru
Joined
Jun 28, 2014
Messages
878
It almost looks like the power-on hours did a 15/16-bit wrap-around after 32767.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Yeah that drive clearly has issues.
 

digity

Contributor
Joined
Apr 24, 2016
Messages
156
It almost looks like the power-on hours did a 15/16-bit wrap-around after 32767.
So it improperly reset the count? Jumped the track? I'm curious, can you explain?

Sent from my SM-G955U using Tapatalk
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
I seem to vaguely recall some old drives doing the stupid hour counter overflow routine. Definitely not the kind of drive I'd have much faith in, even by HDD standards.
 
Status
Not open for further replies.
Top