Degraded Volume, not sure which drive

[g4m3r7ag]

I got an alert that my volume was in a degraded status. I checked the volume it shows it is resilvering with my hot spare. The volume status shows two degraded drives though, da11 and spare-0? Am I correct in assuming that spare-0 is showing faulted because it is still resilvering and that my actual faulted drive is da11? I have my drive trays labeled with S/N so SMART output of 11 will tell me which drive needs replacing. That's my confusion though, SMART shows no real problems with the drive. I have been getting some random ATA error count increases and posted a previous thread and it is believed that my HBA is just not getting enough air flow as the ambient temp has been rather warm lately. Could the drive be fine and the HBA errors just caused it to think the drive was faulted and removed it from the pool? How should I go about testing the drive then?

zpool status

Code:

root@freenas:~ # zpool status
  pool: Media
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
		continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Fri Sep 21 00:46:31 2018
		22.0T scanned at 3.27G/s, 16.7T issued at 573M/s, 22.2T total
		208G resilvered, 75.13% done, 0 days 02:48:27 to go
config:

		NAME											  STATE	 READ WRITE CKSUM
		Media											 DEGRADED	 0	 0	 0
		  mirror-0										ONLINE	   0	 0	 0
			gptid/3e730f1a-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
			gptid/3fda3caa-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
		  mirror-1										DEGRADED	 0	 0	 0
			spare-0									   FAULTED	  0	 0	 0
			  gptid/413d518d-2fb5-11e8-b89e-d4ae52805daa  FAULTED	  6   230	 0  too many errors
			  gptid/49b536ed-2fb5-11e8-b89e-d4ae52805daa  ONLINE	   0	 0	 0  (resilvering)
			gptid/42a1b153-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
		  mirror-2										ONLINE	   0	 0	 0
			gptid/4407b94c-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
			gptid/457be9ff-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
		  mirror-3										ONLINE	   0	 0	 0
			gptid/46edc9ba-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
			gptid/4845c8bc-2fb5-11e8-b89e-d4ae52805daa	ONLINE	   0	 0	 0
		spares
		  13635575311792425251							INUSE	 was /dev/gptid/49b536ed-2fb5-11e8-b89e-d4ae52805daa

errors: No known data errors

  pool: VMWare
 state: ONLINE
  scan: scrub repaired 0 in 0 days 01:03:16 with 0 errors on Sun Sep 16 06:03:16 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		VMWare										  ONLINE	   0	 0	 0
		  mirror-0									  ONLINE	   0	 0	 0
			gptid/9bfcecf3-37e4-11e8-8a42-d4ae52805daa  ONLINE	   0	 0	 0
			gptid/9d4f42cc-37e4-11e8-8a42-d4ae52805daa  ONLINE	   0	 0	 0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:07 with 0 errors on Fri Sep 14 03:45:07 2018
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  ONLINE	   0	 0	 0
		  mirror-0  ONLINE	   0	 0	 0
			da0p2   ONLINE	   0	 0	 0
			da1p2   ONLINE	   0	 0	 0

errors: No known data errors
root@freenas:~ #

Edit: here is the SMART for da11

Code:

root@freenas:~ # smartctl -a /dev/da11
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:	 WDC WD80EMAZ-00WJTA0
Serial Number:	XXXXXXXX
LU WWN Device Id: 5 000cca 252c6e75d
Firmware Version: 83.H0A83
User Capacity:	8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:	 512 bytes logical, 4096 bytes physical
Rotation Rate:	5400 rpm
Form Factor:	  3.5 inches
Device is:		Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Fri Sep 21 01:23:01 2018 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:  (0x82) Offline data collection activity
										was completed without error.
										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:				(   93) 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:		(   2) minutes.
Extended self-test routine
recommended polling time:		( 968) 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  0x0004   129   129   054	Old_age   Offline	  -	   112
  3 Spin_Up_Time			0x0007   157   157   024	Pre-fail  Always	   -	   398 (Average 439)
  4 Start_Stop_Count		0x0012   100   100   000	Old_age   Always	   -	   20
  5 Reallocated_Sector_Ct   0x0033   100   100   005	Pre-fail  Always	   -	   0
  7 Seek_Error_Rate		 0x000a   100   100   067	Old_age   Always	   -	   0
  8 Seek_Time_Performance   0x0004   128   128   020	Old_age   Offline	  -	   18
  9 Power_On_Hours		  0x0012   100   100   000	Old_age   Always	   -	   4408
 10 Spin_Retry_Count		0x0012   100   100   060	Old_age   Always	   -	   0
 12 Power_Cycle_Count	   0x0032   100   100   000	Old_age   Always	   -	   20
 22 Unknown_Attribute	   0x0023   100   100   025	Pre-fail  Always	   -	   100
192 Power-Off_Retract_Count 0x0032   100   100   000	Old_age   Always	   -	   355
193 Load_Cycle_Count		0x0012   100   100   000	Old_age   Always	   -	   355
194 Temperature_Celsius	 0x0002   162   162   000	Old_age   Always	   -	   40 (Min/Max 15/43)
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   199   199   000	Old_age   Always	   -	   2

SMART Error Log Version: 1
ATA Error Count: 2
		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 2 occurred at disk power-on lifetime: 4407 hours (183 days + 15 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
  -- -- -- -- -- -- --
  84 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 40 00 70 35 9d 40 00  42d+11:15:46.134  WRITE FPDMA QUEUED
  61 00 00 20 c1 3f 40 00  42d+11:15:46.132  WRITE FPDMA QUEUED
  61 00 08 20 c0 3f 40 00  42d+11:15:46.131  WRITE FPDMA QUEUED
  61 00 00 20 bf 3f 40 00  42d+11:15:46.131  WRITE FPDMA QUEUED
  61 00 00 20 be 3f 40 00  42d+11:15:46.131  WRITE FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 4405 hours (183 days + 13 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
  -- -- -- -- -- -- --
  84 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 18 58 8a 32 40 00  42d+09:38:02.583  WRITE FPDMA QUEUED
  61 00 10 58 89 32 40 00  42d+09:38:02.580  WRITE FPDMA QUEUED
  61 00 08 58 88 32 40 00  42d+09:38:02.580  WRITE FPDMA QUEUED
  61 00 00 20 0a 32 40 00  42d+09:38:02.580  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 00 00  42d+09:38:02.434  FLUSH CACHE EXT

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%	  4361		 -
# 2  Short offline	   Completed without error	   00%	  4193		 -
# 3  Extended offline	Completed without error	   00%	  4115		 -
# 4  Short offline	   Completed without error	   00%	  4025		 -
# 5  Short offline	   Completed without error	   00%	  3785		 -
# 6  Extended offline	Completed without error	   00%	  3707		 -
# 7  Short offline	   Completed without error	   00%	  3617		 -
# 8  Short offline	   Completed without error	   00%	  3449		 -
# 9  Extended offline	Completed without error	   00%	  3371		 -
#10  Short offline	   Completed without error	   00%	  3282		 -
#11  Short offline	   Completed without error	   00%	  3042		 -
#12  Extended offline	Completed without error	   00%	  2963		 -
#13  Short offline	   Completed without error	   00%	  2874		 -
#14  Short offline	   Completed without error	   00%	  2706		 -
#15  Extended offline	Completed without error	   00%	  2627		 -
#16  Short offline	   Completed without error	   00%	  2538		 -
#17  Short offline	   Completed without error	   00%	  2322		 -
#18  Extended offline	Completed without error	   00%	  2243		 -
#19  Short offline	   Completed without error	   00%	  2154		 -
#20  Short offline	   Completed without error	   00%	  1986		 -
#21  Extended offline	Completed without error	   00%	  1907		 -

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.

root@freenas:~ #

 

[Johnny Fartpants]

What system have you got and how are the drives connected? Give us full specs please so we can at least try and help.

Edit: Just looked at another one of your threads and found this:

It's in a SuperMicro SC847 45 bay JBOD connected to an R710 VIA a 9208e.

Just so everyone knows what we are dealing with.

 

[Johnny Fartpants]

How many drives in your 45 bay JBOD? How many pools? Where is the faulty drive physically located (front or rear)?

 

[g4m3r7ag]

There are 11 drives making up the two Volumes. One volume is 4 striped mirrors with a hot spare. The other volume is a single mirror currently. All drives are in the front of the JBOD. The errors (from the previous thread, ATA error count) occurred during a heavy write operation that lasted 4-5 hours and only began occurring after the first couple of hours. I was getting an email saying random drive x ATA error count increased by one. Then after a few of those I got one that had 3-4 drives listed in it as error count increasing by one as well as the volume degrading and resilvering beginning with the spare. That combined with the SMART data not showing any bad sectors on the drive leads me to believe the writes errors sustained from the HBA overheating caused the drive to drop out of the pool and it's not actually bad. I'm not sure how to go about testing it to verify once the resilver is done with the spare and to be sure of which drive actually dropped out.

 

[Johnny Fartpants]

How long have you had this system? Have you ever had similar issues? Have you carried out drive replacements on the system before?

 

[g4m3r7ag]

System has been in service for 6-7 months and did not have any issues until the ambient temps started going up causing the ATA errors from the previous thread. I have not carried out any drive replacements I did run surface test on all the disks with a separate system before commissioning the system.

 

[Johnny Fartpants]

As the system is still quite new and given the fact you haven't carried out any drive replacements Im a little concerned about the internal wiring. Having errors on one drive is one thing but errors on a few while SMART says they are fine is concerning. The reason I mention internal wiring is because I have been burnt on this before with a 45 Bay Supermicro JBOD. It appeared that FreeBSD (FreeNAS) needed the JBOD wiring differently from other platforms. For example in my case the original wiring method was HBA Input into Pri J0 and Sec J0, the cascade cable to the rear was going out from Pri J1 and Sec J1. After reconfiguring by moving cascade cable from J1 on both Pri and Sec to J2 on both Pri and Sec all worked great.

It might not be this at all but seems a little coincidental. The reason I asked about drive replacements is because this is how I discovered the issue in testing. When I added a drive to the rear of the JOBD (and only the rear) the whole system went crazy and the console was filled with CAM CONTROL errors.

UPDATE: Its worth mentioning that my 45 Bay was using multipath and SAS drives so I could be barking up the wrong tree.

 

[g4m3r7ag]

I'm not sure I follow? I have one connection from my 8e going to the front backplane and the other connection on the 8e going to the rear backplane. I'm only using one of the connectors on each backplane. I feel if I had it connected to the wrong port I wouldn't get any communication at all?

 

[Johnny Fartpants]

You're thinking on the outside and Im talking about the internal wiring. Perhaps take a pic of the rear and lets take a look although naturally this won't tell us if the internal wiring is correct. Regarding your last point then no not necessarily as it depends on how the front and rear backplane are connected via cascade cables.

 

[Johnny Fartpants]

When you tested it did you ever just try connecting one cable to see if you could see all the drives?

 

[Johnny Fartpants]

Take a look at this. Do you know which one you have?

 

[Johnny Fartpants]

Its starting to sound like you might have a JBOD with dual-port expanders that access all the drives and that you have cabled it twice from your HBA. As you are using SATA drives and not SAS they don't support multipath so Im not entirely sure what outcome this would have however its probably not good.

 

[g4m3r7ag]

I have the single port/EL1 configuration. I have one of my 8e ports connected to J0 on the front backplane and the other 8e port connected to J0 on the rear backplane. The two backplanes are not connected/cascaded together. All of my drives are also connected to the front backplane I have none on the rear.

Edit: just saw the above post, I am using SATA drives.

 

[Johnny Fartpants]

"BPN-SAS2-847EL1 backplanes have a single-port expander that access all hard drives and supports cascading."

 

[Johnny Fartpants]

Take a pic of the rear dude and lets have a butchers

 

[g4m3r7ag]

I am only using the top and bottom ports on the JBOD chassis. One port goes to the front backplane, the other goes to the rear back plane. The middle two ports of the chassis are connected to neither backplane and the backplanes are not connected internally.

 

[Johnny Fartpants]

One port goes to the front backplane, the other goes to the rear back plane. The middle two ports of the chassis are connected to neither backplane and the backplanes are not connected internally.

Do you know this for a fact as it doesn't sound quite right to me?

Default config from Supermciro is "BPN-SAS2-847EL1 backplanes have a single-port expander that access all hard drives". Im not entirely sure if what you're saying is even possible with the EL1.

I would suggest you contact Supermicro as I have always found their support brilliant. At least that way you can figure out what it can/can't do and how exactly it should be wired.

 

[g4m3r7ag]

I believe by default I would have only needed for example a 4e with a single connection to the J0 port of the front backplane and then an internal connection from J1 on the front backplane to J0 on the rear backplane if I wanted to cascade the backplanes. I had the 8e so I just connected each backplane independently to the HBA. The built in expander also means for the backplane itself, I can have 24 drives through a single backplane connection to the HBA on the front backplane. If there was no expander in the backplane I would need 6 connections back to an HBA(s) in order to use all 24 drives.

 

[Johnny Fartpants]

I believe by default I would have only needed for example a 4e with a single connection to the J0 port of the front backplane and then an internal connection from J1 on the front backplane to J0 on the rear backplane if I wanted to cascade the backplanes. I had the 8e so I just connected each backplane independently to the HBA. The built in expander also means for the backplane itself, I can have 24 drives through a single backplane connection to the HBA on the front backplane. If there was no expander in the backplane I would need 6 connections back to an HBA(s) in order to use all 24 drives.

I assume when you purchased the JBOD you asked for it to be wired in the fashion you are describing or you did it yourself as I don't think they arrive like that.

What you are saying about 24 drives going via one port and the rest via the other makes complete sense and is a legit config Im just not 100% sure your system is setup correctly for this or even if the EL1 supports this.

 

[g4m3r7ag]

I bought it second hand and yes I wired it like that. Currently it is wired and used just like it would be in any system that has a single front 24 port Supermicro backplane.

Edit: For all intents and purposes, currently it would be as if the rear backplane does not even exist as there are no drives connected to it. And if there were drives connected to it, FreeNAS should see it as a completely separate backplane.