Do I have a SATA problem or a drive problem or did things repair themselves.

[NASbox]

I am in the process of upgrading (from 8.3.1 to 11U4) and rebuilding my FreeNAS (New CPU/MB/LSI LBA and SSD boot device). I installed FreeNAS v11-U3 to an SSD drive, then later upgraded to U4, played around with the GUI and networking configuration. I then attached my pools, and did some more networking changes.

Somewhere during the process an error alert relating to gptid/73fc17c0 popped up on the GUI - since I was working at the console I didn't notice it immediately.

I cleared the error with zpool clear TANK , and immediately ran zpool scrub TANK.

After the scrub completed zpool status TANK returns the following output:

Code:

freenas# zpool status TANK
pool: TANK
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: http://illumos.org/msg/ZFS-8000-9P
scan: scrub repaired 52K in 9h30m with 0 errors on Tue Oct 10 13:02:16 2017
config:

NAME											STATE	 READ WRITE CKSUM
TANK											ONLINE	 0	 0	 0
raidz2-0									 ONLINE	 0	 0	 0
	gptid/73fc17c0-1916-11e5-b2b5-c----------b ONLINE	 0	 0	13
	gptid/bcd021f7-dbd8-11e4-adc9-c----------b ONLINE	 0	 0	 0
	gptid/fcd3d3cb-f747-11e4-95cc-c----------b ONLINE	 0	 0	 0
	gptid/76e6e5f1-0f39-11e5-8bc3-c----------b ONLINE	 0	 0	 0

errors: No known data errors

Does this mean that disk gptid/73fc17c0 still has errors, or does it simply mean that the scrub fixed 13 errors?

What should I do now?

I am currently running a long test on /dev/da3 to see if it reveals anything-that will take about 12 hours to finish since it's a 6TB drive.

glabel status shows that this drive is /dev/da3, but smartctl -a /dev/da3 shows no indication of any pending or reallocated sectors.

Background:
Prior to installing the pool I gave the system extensive memory tests for about 48 hours and there was no sign of problems. I used 2 ports on the LBA to test 2 brand new drives (not in use yet) for about a week with badblocks, so the system seems to be good after a decent burnin. The SATA port used for /dev/da3 has not been tested.

My plan is to check the results of the test, if that's OK, clear the error again, reboot, and rescrub to see what happens.

Any Advice / comments / suggestions are much appreciated.

 

[Bostjan]

it seems you are on top of this. Do your plan. We'll see the result of new scrub.


Sent from my iPhone using Tapatalk

 

[rs225]

Look at your SMART for any UDMA errors. If checksum errors keep showing up, but with no particular cause, it is often a cable issue, but can also be the port or the drive controller.

The 13 is a counter; it has experienced 13 since last clearing, which should include those corrected during the scrub. If it picks up more during another scrub, you can assume that the errors are in your electronics at the time of the read, not on the disk.

 

[NASbox]

Just a couple of points of clarification (with reference to the zpool status above):

state: ONLINE
Does this mean that all the errors were corrected and that FreeNAS thinks the pool is error free? Am I correct that if there were uncorrected errors would it say state: DEGRADED?

scan: scrub repaired 52K in 9h30m with 0 errors on Tue Oct 10 13:02:16 2017
Means that all errors were corrected successfully.

errors: No known data errors
Second conformation that the pool is error free and that all errors were corrected successfully.

Look at your SMART for any UDMA errors. If checksum errors keep showing up, but with no particular cause, it is often a cable issue, but can also be the port or the drive controller.

The 13 is a counter; it has experienced 13 since last clearing, which should include those corrected during the scrub. If it picks up more during another scrub, you can assume that the errors are in your electronics at the time of the read, not on the disk.

Here's the extended info from smartctl -x. The drive is still doing a long test, but this seems pretty clean.

Code:

=== 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:  ( 247)   Self-test routine in progress...
		   70% of test remaining.
Total time to complete Offline
data collection:	  ( 1904) 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:	 ( 673) minutes.
Conveyance self-test routine
recommended polling time:	 (  5) minutes.
SCT capabilities:	 (0x303d)   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  FLAGS  VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate  POSR-K  200  200  051  -  0
  3 Spin_Up_Time  POS--K  229  198  021  -  7541
  4 Start_Stop_Count  -O--CK  100  100  000  -  211
  5 Reallocated_Sector_Ct  PO--CK  200  200  140  -  0
  7 Seek_Error_Rate  -OSR-K  200  200  000  -  0
  9 Power_On_Hours  -O--CK  077  077  000  -  17056
10 Spin_Retry_Count  -O--CK  100  100  000  -  0
11 Calibration_Retry_Count -O--CK  100  253  000  -  0
12 Power_Cycle_Count  -O--CK  100  100  000  -  38
192 Power-Off_Retract_Count -O--CK  200  200  000  -  10
193 Load_Cycle_Count  -O--CK  194  194  000  -  19280
194 Temperature_Celsius  -O---K  114  101  000  -  38
196 Reallocated_Event_Count -O--CK  200  200  000  -  0
197 Current_Pending_Sector  -O--CK  200  200  000  -  0
198 Offline_Uncorrectable  ----CK  100  253  000  -  0
199 UDMA_CRC_Error_Count  -O--CK  200  200  000  -  0
200 Multi_Zone_Error_Rate  ---R--  200  200  000  -  0
  ||||||_ K auto-keep
  |||||__ C event count
  ||||___ R error rate
  |||____ S speed/performance
  ||_____ O updated online
  |______ P prefailure warning

General Purpose Log Directory Version 1
SMART  Log Directory Version 1 [multi-sector log support]
Address  Access  R/W  Size  Description
0x00  GPL,SL  R/O  1  Log Directory
0x01  SL  R/O  1  Summary SMART error log
0x02  SL  R/O  5  Comprehensive SMART error log
0x03  GPL  R/O  6  Ext. Comprehensive SMART error log
0x06  SL  R/O  1  SMART self-test log
0x07  GPL  R/O  1  Extended self-test log
0x09  SL  R/W  1  Selective self-test log
0x10  GPL  R/O  1  SATA NCQ Queued Error log
0x11  GPL  R/O  1  SATA Phy Event Counters log
0x21  GPL  R/O  1  Write stream error log
0x22  GPL  R/O  1  Read stream error log
0x30  GPL,SL  R/O  9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W  16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS  16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS  1  Device vendor specific log
0xb7  GPL,SL  VS  40  Device vendor specific log
0xbd  GPL,SL  VS  1  Device vendor specific log
0xc0  GPL,SL  VS  1  Device vendor specific log
0xc1  GPL  VS  93  Device vendor specific log
0xe0  GPL,SL  R/W  1  SCT Command/Status
0xe1  GPL,SL  R/W  1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description  Status  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline  Aborted by host  90%  17051  -
# 2  Extended offline  Aborted by host  90%  17051  -
# 3  Extended offline  Completed without error  00%  16961  -
# 4  Short offline  Completed without error  00%  16918  -
# 5  Extended offline  Completed without error  00%  85  -
# 6  Extended offline  Completed without error  00%  51  -
# 7  Extended offline  Completed without error  00%  12  -
# 8  Short offline  Completed without error  00%  0  -
# 9  Short offline  Completed without error  00%  0  -
#10  Conveyance offline  Completed without error  00%  0  -

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.

SCT Status Version:  3
SCT Version (vendor specific):  258 (0x0102)
SCT Support Level:  1
Device State:  DST executing in background (3)
Current Temperature:  38 Celsius
Power Cycle Min/Max Temperature:  28/40 Celsius
Lifetime  Min/Max Temperature:  23/51 Celsius
Under/Over Temperature Limit Count:  0/0
Vendor specific:
00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:  2
Temperature Sampling Period:  1 minute
Temperature Logging Interval:  1 minute
Min/Max recommended Temperature:  0/60 Celsius
Min/Max Temperature Limit:  -41/85 Celsius
Temperature History Size (Index):  478 (49)

Index  Estimated Time  Temperature Celsius
  50  2017-10-10 08:15  38  *******************
...  ..( 85 skipped).  ..  *******************
136  2017-10-10 09:41  38  *******************
137  2017-10-10 09:42  37  ******************
...  ..(  4 skipped).  ..  ******************
142  2017-10-10 09:47  37  ******************
143  2017-10-10 09:48  36  *****************
...  ..(  6 skipped).  ..  *****************
150  2017-10-10 09:55  36  *****************
151  2017-10-10 09:56  35  ****************
...  ..( 10 skipped).  ..  ****************
162  2017-10-10 10:07  35  ****************
163  2017-10-10 10:08  36  *****************
...  ..(  6 skipped).  ..  *****************
170  2017-10-10 10:15  36  *****************
171  2017-10-10 10:16  37  ******************
...  ..(147 skipped).  ..  ******************
319  2017-10-10 12:44  37  ******************
320  2017-10-10 12:45  38  *******************
321  2017-10-10 12:46  38  *******************
322  2017-10-10 12:47  39  ********************
...  ..( 87 skipped).  ..  ********************
410  2017-10-10 14:15  39  ********************
411  2017-10-10 14:16  38  *******************
...  ..(115 skipped).  ..  *******************
  49  2017-10-10 16:12  38  *******************

SCT Error Recovery Control:
  Read:  70 (7.0 seconds)
  Write:  70 (7.0 seconds)

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID  Size  Value  Description
0x0001  2  0  Command failed due to ICRC error
0x0002  2  0  R_ERR response for data FIS
0x0003  2  0  R_ERR response for device-to-host data FIS
0x0004  2  0  R_ERR response for host-to-device data FIS
0x0005  2  0  R_ERR response for non-data FIS
0x0006  2  0  R_ERR response for device-to-host non-data FIS
0x0007  2  0  R_ERR response for host-to-device non-data FIS
0x0008  2  0  Device-to-host non-data FIS retries
0x0009  2  3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2  15  Device-to-host register FISes sent due to a COMRESET
0x000b  2  0  CRC errors within host-to-device FIS
0x000f  2  0  R_ERR response for host-to-device data FIS, CRC
0x0012  2  0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4  65536  Vendor specific

I'm hoping these errors are just artifacts left over from a crash. As I recall the system hung due to a network problem and I had to power off.

I also hot swapped a drive for backup with the old motherboard - Is it possible that might have done the damage?
(Inserted a drive into a hot swap cady which was connected to a vacant sata port that was configured for hot swap and created a single disk pool and performed a backup.)

Does scrub do detailed error logging (i.e. so it would be possible to locate exact sector(s) with damage)?
Given the size of drives these days, it would be good to be able to "spot test"

 

[Stux]

It could've been a transient error. Yes, everything is fine.

Continue with automated scrubs and smart checks. If it happens again, then you probably have a hw issue. Possibly power or cabling.

What brand and model (exactly) are your HDs?

 

[NASbox]

What brand and model (exactly) are your HDs?

Western Digital Red WD60EFRX-68MYMN1

 

[Stux]

Western Digital Red WD60EFRX-68MYMN1

Well the good news is it's not the 68L0BN1 version which has issues

https://forums.freenas.org/index.ph...ors-during-scrubbing.54988/page-5#post-403446

 

[NASbox]

Scrub completed without error and there is no sign of anything on the smart for any of the drives.

Anything left to do, or just consider it a transient issue?