Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Scrub not finding SCSI Status Error???

Status
Not open for further replies.

mbalsam

Member
Joined
Oct 9, 2015
Messages
85
Yesterday, i had my drive pool configured as a set of mirrored drives.

While copying some large files and i looked at the console to see errors. Did a zpool status and found 175 write errors on my da1 drive.

Today i reformatted disks a raidz3 pool. After doing a zpool status, i dont see any write errors. But when i look in dmesg.today i see messages like this:

(da1:mps0:0:9:0): CAM status: CCB request completed with an error
(da1:mps0:0:9:0): Retrying command
(da1:mps0:0:9:0): WRITE(10). CDB: 2a 00 00 40 75 b8 00 00 20 00
(da1:mps0:0:9:0): CAM status: SCSI Status Error

So i enabled the scrub to run. I wait a few hours. I do a zpool status and see this:

pool: pool
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Wed Oct 4 20:49:34 2017
config:

So now i'm really confused.

1) I no longer see write errors now that zfs is reconfigured as raidz3.
2) I expected to see more write errors now that im scrubbing the drives every hour, but i dont.

Yesterday i thought i should return the da1 drive to Amazon. But now i cant get the evidence i need to do it. Whats up??
 

mbalsam

Member
Joined
Oct 9, 2015
Messages
85
In looking at the logs i see that there are two types of errors:


(da1:mps0:0:9:0): SCSI status: Check Condition
(da1:mps0:0:9:0): SCSI sense: NOT READY asc:4,0 (Logical unit not ready, cause not reportable)
(da1:mps0:0:9:0): Retrying command (per sense data)
(da1:mps0:0:9:0): READ(16). CDB: 88 00 00 00 00 01 d1 c0 be 49 00 00 00 04 00 00
(da1:mps0:0:9:0): CAM status: SCSI Status Error
(da1:mps0:0:9:0): SCSI status: Check Condition
(da1:mps0:0:9:0): SCSI sense: NOT READY asc:4,0 (Logical unit not ready, cause not reportable)
(da1:mps0:0:9:0): Error 5, Retries exhausted

Not sure if this matters.. But why is scrub not picking this up?
 

Ericloewe

Not-very-passive-but-aggressive
Moderator
Joined
Feb 15, 2014
Messages
17,019
But why is scrub not picking this up?
Because it hasn't caused data corruption.

scrubbing the drives every hour,
Wait, what? Scrubbing every hour?

But now i cant get the evidence i need to do it.
What's up is that you need to acquaint yourself with SMART. If you're not running regular SMART tests, set them up now and manually run a long test.
Post the output of smartctl -a /dev/ada1. Don't forget the CODE tags when pasting it here.
 

mbalsam

Member
Joined
Oct 9, 2015
Messages
85
Code:
root@freenas:/var/log # smartctl -a /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-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 WD40EFRX-68N32N0
Serial Number:	WD-WCC7K4SP45X2
LU WWN Device Id: 5 0014ee 26400c60e
Firmware Version: 82.00A82
User Capacity:	4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:	 512 bytes logical, 4096 bytes physical
Rotation Rate:	5400 rpm
Form Factor:	  3.5 inches
Device is:		In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Thu Oct  5 22:07:00 2017 EDT
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:				(44700) 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:		( 474) 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		  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   168   168   021	Pre-fail  Always	   -	   6591
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   11
  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   100   100   000	Old_age   Always	   -	   108
 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	   -	   11
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   9
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   70
194 Temperature_Celsius	 0x0022   123   115   000	Old_age   Always	   -	   27
196 Reallocated_Event_Count 0x0032   200   200   000	Old_age   Always	   -	   0
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -	   0
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   100   253   000	Old_age   Offline	  -	   0

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%	   108		 -
# 2  Short offline	   Completed without error	   00%	   107		 -
# 3  Short offline	   Completed without error	   00%	   106		 -
# 4  Short offline	   Completed without error	   00%	   105		 -
# 5  Short offline	   Completed without error	   00%	   104		 -
# 6  Short offline	   Completed without error	   00%	   103		 -
# 7  Short offline	   Completed without error	   00%	   102		 -
# 8  Short offline	   Completed without error	   00%	   101		 -
# 9  Short offline	   Completed without error	   00%	   100		 -
#10  Short offline	   Interrupted (host reset)	  90%	   100		 -
#11  Short offline	   Completed without error	   00%		99		 -
#12  Short offline	   Completed without error	   00%		98		 -
#13  Short offline	   Completed without error	   00%		97		 -
#14  Short offline	   Completed without error	   00%		96		 -
#15  Short offline	   Completed without error	   00%		95		 -
#16  Short offline	   Completed without error	   00%		94		 -
#17  Short offline	   Completed without error	   00%		93		 -
#18  Short offline	   Completed without error	   00%		92		 -
#19  Short offline	   Completed without error	   00%		91		 -
#20  Short offline	   Completed without error	   00%		90		 -
#21  Short offline	   Completed without error	   00%		89		 -

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.

 

mbalsam

Member
Joined
Oct 9, 2015
Messages
85
Your right, scrubbing ever hour is too aggressive. There is nothing on the NAS box so its not an issue, but thanks for the suggestion.
 

mbalsam

Member
Joined
Oct 9, 2015
Messages
85
I think i found what i need when running the smartctl -x

Code:
SATA Phy Event Counters (GP Log 0x11)
ID	  Size	 Value  Description
0x0001  2			0  Command failed due to ICRC error
0x0002  2		  637  R_ERR response for data FIS
0x0003  2			0  R_ERR response for device-to-host data FIS
0x0004  2		  637  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		  661  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2		  676  Device-to-host register FISes sent due to a COMRESET
0x000b  2		  270  CRC errors within host-to-device FIS
0x000d  2		  367  Non-CRC errors within host-to-device FIS
0x000f  2		  270  R_ERR response for host-to-device data FIS, CRC
0x0012  2			0  R_ERR response for host-to-device non-data FIS, CRC


On other drives is much different
Code:
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			9  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2		   18  Device-to-host register FISes sent due to a COMRESET
0x000b  2			0  CRC errors within host-to-device FIS
0x000d  2			0  Non-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	   373513  Vendor specific

 

mbalsam

Member
Joined
Oct 9, 2015
Messages
85
Note: This is an old back-plane that i'm not going to run in production. My production system is still running my old nexenta configuration. I plan on swapping them over a weekend once i get freenas under my belt. Is it possible the drive is good and the backplane is to blame? i guess a test would be to move the drive to a different slot??
 

Chris Moore

Wizened Sage
Joined
May 2, 2015
Messages
10,062
i guess a test would be to move the drive to a different slot??
Yes, I had a drive that was throwing errors and worked fine when I moved it to a different drive bay. I think the cable is damaged in my case.
 

Ericloewe

Not-very-passive-but-aggressive
Moderator
Joined
Feb 15, 2014
Messages
17,019
That drive is apparently fine (it hasn't been properly tested, though). Your problem is almost certainly cabling or the backplane.
 
Status
Not open for further replies.
Top