Trouble in River City

Status
Not open for further replies.

Mike Zahorik

Explorer
Joined
Mar 14, 2013
Messages
62
Code:
[root@freenas ~]# smartctl -x/dev/ada0										 
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p5 amd64] (local build)	 
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net	 
																				
=======> UNRECOGNIZED OPTION: /												 
																				
Use smartctl -h to get a usage summary										 
																				
[root@freenas ~]#


IS this what you asked for?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
I'm sorry, but I'm lost. Where is the reply window?
At the bottom of the page, where you're typing your text to reply. Immediately above the field where you're typing, there are a number of formatting controls--bold, italic, underline, etc. In about the middle, there are three labeled, respectively, cmd, code, and file.

Click the code button, and you'll see opening and closing code tags inserted. Paste your smartctl output in between them.
Code:
It will look like this

upload_2017-5-29_15-58-47.png
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Code:
[root@freenas ~]# smartctl -x/dev/ada0										
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p5 amd64] (local build)	
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net	
																				
=======> UNRECOGNIZED OPTION: /												
																				
Use smartctl -h to get a usage summary										
																				
[root@freenas ~]#


IS this what you asked for?
No, you're missing a space (between the x and the first /). smartctl -x /dev/ada0.

But yes, you found and used the code tags correctly.
 

Mike Zahorik

Explorer
Joined
Mar 14, 2013
Messages
62
Code:
																				
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.	 
																				
Warning: device does not support SCT Data Table command						 
Warning: device does not support SCT Error Recovery Control command			 
SATA Phy Event Counters (GP Log 0x11)										   
ID	  Size	 Value  Description											 
0x000a  2			3  Device-to-host register FISes sent due to a COMRESET	
0x0001  2			0  Command failed due to ICRC error						
0x0003  2			0  R_ERR response for device-to-host data FIS			 
0x0004  2			0  R_ERR response for host-to-device 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		 
																		


There is more to the output, but it flashed past. This is the last of it. Is there a pause flag that can be used?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Is there a pause flag that can be used?
A better option would be to use ssh to connect to your server--PuTTY and Bitvise are popular Windows SSH clients; MacOS and Linux will typically ship with ssh installed. This will let you scroll back, and grab the whole output at once.

But failing that, yes, there are a number of ways to pause the output. Probably the most common and simplest is to use more. smartctl -x /dev/ada0 | more, and then repeat for ada1.
 

Mike Zahorik

Explorer
Joined
Mar 14, 2013
Messages
62
Code:
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p5 amd64] (local build)	 
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net	 
																				
=== START OF INFORMATION SECTION ===											
Model Family:	 Seagate Barracuda (SATA 3Gb/s, 4K Sectors)					
Device Model:	 ST1000DM003-1CH162											
Serial Number:	S1D8L4P1													 
LU WWN Device Id: 5 000c50 05c1cd806											
Firmware Version: CC46														 
User Capacity:	1,000,204,886,016 bytes [1.00 TB]							 
Sector Sizes:	 512 bytes logical, 4096 bytes physical						
Device is:		In smartctl database [for details use: -P show]			   
ATA Version is:   8															 
ATA Standard is:  ATA-8-ACS revision 4										 
Local Time is:	Mon May 29 15:08:50 2017 CDT								 
SMART support is: Available - device has SMART capability.					 
SMART support is: Enabled													   
AAM feature is:   Unavailable												   
APM level is:	 1 (minimum power consumption with standby)					
Rd look-ahead is: Enabled													   
Write cache is:   Enabled													   
ATA Security is:  Disabled, NOT FROZEN [SEC1]								   
																				
--More--(byte 930)  
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net	 
																				
=== START OF INFORMATION SECTION ===											
Model Family:	 Seagate Barracuda (SATA 3Gb/s, 4K Sectors)					
Device Model:	 ST1000DM003-1CH162											
Serial Number:	S1D8L4P1													 
LU WWN Device Id: 5 000c50 05c1cd806											
Firmware Version: CC46														 
User Capacity:	1,000,204,886,016 bytes [1.00 TB]							 
Sector Sizes:	 512 bytes logical, 4096 bytes physical						
Device is:		In smartctl database [for details use: -P show]			   
ATA Version is:   8															 
ATA Standard is:  ATA-8-ACS revision 4										 
Local Time is:	Mon May 29 15:08:50 2017 CDT								 
SMART support is: Available - device has SMART capability.					 
SMART support is: Enabled													   
AAM feature is:   Unavailable												   
APM level is:	 1 (minimum power consumption with standby)					
Rd look-ahead is: Enabled													   
Write cache is:   Enabled													   
ATA Security is:  Disabled, NOT FROZEN [SEC1]								   
																				
=== 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:				(  584) seconds.								
Offline data collection														 
capabilities:					(0x73) SMART execute Offline immediate.		
										Auto Offline data collection on/off supp
ort.																			
										
										Suspend Offline collection upon new	 
										command.								
										No 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:		(   1) minutes.								
Extended self-test routine													 
recommended polling time:		( 122) minutes.								
Conveyance self-test routine													
recommended polling time:		(   2) minutes.								
SCT capabilities:			  (0x3085) SCT Status supported.				   
																				
SMART Attributes Data Structure revision number: 10							 
Vendor Specific SMART Attributes with Thresholds:							   
ID# ATTRIBUTE_NAME		  FLAGS	VALUE WORST THRESH FAIL RAW_VALUE		 
  1 Raw_Read_Error_Rate	 POSR--   103   091   006	-	176668968		 
  3 Spin_Up_Time			PO----   097   097   000	-	0				 
  4 Start_Stop_Count		-O--CK   038   038   020	-	64221			 
  5 Reallocated_Sector_Ct   PO--CK   100   100   010	-	0				 
  7 Seek_Error_Rate		 POSR--   066   060   030	-	4136301			
  9 Power_On_Hours		  -O--CK   084   084   000	-	14887			 
10 Spin_Retry_Count		PO--C-   100   100   097	-	0				 
12 Power_Cycle_Count	   -O--CK   099   099   020	-	1625			   
183 Runtime_Bad_Block	   -O--CK   100   100   000	-	0				 
184 End-to-End_Error		-O--CK   100   100   099	-	0				 
187 Reported_Uncorrect	  -O--CK   001   001   000	-	890				
188 Command_Timeout		 -O--CK   100   100   000	-	0				 
189 High_Fly_Writes		 -O-RCK   100   100   000	-	0				 
190 Airflow_Temperature_Cel -O---K   069   064   045	-	31 (0 182 34 28 0)
191 G-Sense_Error_Rate	  -O--CK   100   100   000	-	0				 
192 Power-Off_Retract_Count -O--CK   100   100   000	-	69				 
193 Load_Cycle_Count		-O--CK   055   055   000	-	91650			 
194 Temperature_Celsius	 -O---K   031   040   000	-	31 (128 0 0 0 0)   
197 Current_Pending_Sector  -O--C-   099   099   000	-	216
198 Offline_Uncorrectable   ----C-   099   099   000	-	216				
199 UDMA_CRC_Error_Count	-OSRCK   200   200   000	-	0				 
240 Head_Flying_Hours	   ------   100   253   000	-	199569950388230	
241 Total_LBAs_Written	  ------   100   253   000	-	547747932		 
242 Total_LBAs_Read		 ------   100   253   000	-	1707817687		 
							||||||_ 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]			 
GP/S  Log at address 0x00 has	1 sectors [Log Directory]					 
SMART Log at address 0x01 has	1 sectors [Summary SMART error log]			
SMART Log at address 0x02 has	5 sectors [Comprehensive SMART error log]	 
GP	Log at address 0x03 has	5 sectors [Ext. Comprehensive SMART error log]
SMART Log at address 0x06 has	1 sectors [SMART self-test log]				
GP	Log at address 0x07 has	1 sectors [Extended self-test log]			 
SMART Log at address 0x09 has	1 sectors [Selective self-test log]			
GP	Log at address 0x10 has	1 sectors [NCQ Command Error log]			 
GP	Log at address 0x11 has	1 sectors [SATA Phy Event Counters]
GP	Log at address 0x21 has	1 sectors [Write stream error log]			 
GP	Log at address 0x22 has	1 sectors [Read stream error log]			 
GP/S  Log at address 0x80 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x81 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x82 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x83 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x84 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x85 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x86 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x87 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x88 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x89 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x8a has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x8b has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x8c has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x8d has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x8e has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x8f has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x90 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x91 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x92 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x93 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x94 has   16 sectors [Host vendor specific log] 
GP/S  Log at address 0x95 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x96 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x97 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x98 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x99 has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x9a has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x9b has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x9c has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x9d has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x9e has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0x9f has   16 sectors [Host vendor specific log]		   
GP/S  Log at address 0xa1 has   20 sectors [Device vendor specific log]		 
GP	Log at address 0xa2 has 4496 sectors [Device vendor specific log]		 
GP/S  Log at address 0xa8 has  129 sectors [Device vendor specific log]		 
GP/S  Log at address 0xa9 has	1 sectors [Device vendor specific log]		 
GP	Log at address 0xab has	1 sectors [Device vendor specific log]		 
GP	Log at address 0xb0 has 5176 sectors [Device vendor specific log]		 
GP	Log at address 0xbe has 65535 sectors [Device vendor specific log]		
GP	Log at address 0xbf has 65535 sectors [Device vendor specific log]		
GP/S  Log at address 0xc0 has	1 sectors [Device vendor specific log]		 
GP/S  Log at address 0xc1 has   10 sectors [Device vendor specific log]		 
GP/S  Log at address 0xc4 has	5 sectors [Device vendor specific log]		 
GP/S  Log at address 0xe0 has	1 sectors [SCT Command/Status]   
GP/S  Log at address 0xe1 has	1 sectors [SCT Data Transfer]				 
																				
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)				   
Device Error Count: 3256 (device log contains only the most recent 20 errors)   
		CR	 = Command Register											   
		FEATR  = Features Register											 
		COUNT  = Count (was: Sector Count) Register							 
		LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8			 
		LH	 = LBA High (was: Cylinder High) Register	]   LBA			 
		LM	 = LBA Mid (was: Cylinder Low) Register	  ] Register		   
		LL	 = LBA Low (was: Sector Number) Register	 ]					
		DV	 = Device (was: Device/Head) Register							 
		DC	 = Device Control Register										
		ER	 = Error register												 
		ST	 = Status register												
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 3256 [15] occurred at disk power-on lifetime: 14887 hours (620 days + 7 ho
urs)																			
  When the command that caused the error occurred, the device was active or idle
.										   
																			   
  After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: UNC at LBA = 0x13942b58 = 32847
7528																			
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:20.438  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:20.400  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:17.567  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:17.521  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:14.678  READ FPDMA QUEUED	
																				
Error 3255 [14] occurred at disk power-on lifetime: 14887 hours (620 days + 7 ho
urs)																			
  When the command that caused the error occurred, the device was active or idle
.																			   
																				
 
After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: UNC at LBA = 0x13942b58 = 32847
7528																			
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:20.438  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:20.400  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:17.567  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:17.521  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:14.678  READ FPDMA QUEUED	
																				
Error 3254 [13] occurred at disk power-on lifetime: 14887 hours (620 days + 7 ho
urs)																			
  When the command that caused the error occurred, the device was active or idle
.																			   
																				
  After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: UNC at LBA = 0x13942b58 = 32847
7528																			
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:17.567  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:17.521  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:14.678  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:14.616  READ LOG EXT		 
  61 00 00 00 40 00 00 13 8e 91 80 40 00	 00:56:11.783  WRITE FPDMA QUEUED   
																				
Error 3253 [12] occurred at disk power-on lifetime: 14887 hours (620 days + 7 ho
urs)																			
  When the command that caused the error occurred, the device was active or idle
.																			   
																				
  After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: UNC at LBA = 0x13942b58 = 32847
7528																			
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:17.567  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:17.521  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:14.678  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:14.616  READ LOG EXT		 
  61 00 00 00 40 00 00 13 8e 91 80 40 00	 00:56:11.783  WRITE FPDMA QUEUED   
																				
Error 3252 [11] occurred at disk power-on lifetime: 14887 hours (620 days + 7 ho
urs)																			
  When the command that caused the error occurred, the device was active or idle
.																			   
																	
After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: UNC at LBA = 0x13942b58 = 32847
7528																			
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:14.678  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:14.616  READ LOG EXT		 
  61 00 00 00 40 00 00 13 8e 91 80 40 00	 00:56:11.783  WRITE FPDMA QUEUED   
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:11.782  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:11.701  READ LOG EXT		 
																				
Error 3251 [10] occurred at disk power-on lifetime: 14887 hours (620 days + 7 ho
urs)																			
  When the command that caused the error occurred, the device was active or idle
.																			
  After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: UNC at LBA = 0x13942b58 = 32847
7528																			
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:14.678  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:14.616  READ LOG EXT		 
  61 00 00 00 40 00 00 13 8e 91 80 40 00	 00:56:11.783  WRITE FPDMA QUEUED   
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:11.782  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:11.701  READ LOG EXT		 
																				
Error 3250 [9] occurred at disk power-on lifetime: 14887 hours (620 days + 7 hou
rs)																			 
  When the command that caused the error occurred, the device was active or idle
.																		 
  After command completion occurred, registers were:							
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: WP at LBA = 0x13942b58 = 328477
528																			 
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 40 00 00 13 8e 91 80 40 00	 00:56:11.783  WRITE FPDMA QUEUED   
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:11.782  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:11.701  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:08.632  READ FPDMA QUEUED	
  25 00 00 00 40 00 00 13 94 2b 00 40 00	 00:56:05.751  READ DMA EXT		 
																				
Error 3249 [8] occurred at disk power-on lifetime: 14887 hours (620 days + 7 hou
rs)																			 
  When the command that caused the error occurred, the device was active or idle
.																			
  ER -- ST COUNT  LBA_48  LH LM LL DV DC										
  -- -- -- == -- == == == -- -- -- -- --										
  40 -- 51 00 00 00 00 13 94 2b 58 00 00  Error: WP at LBA = 0x13942b58 = 328477
528																			 
																				
  Commands leading to the command that caused the error were:				   
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 40 00 00 13 8e 91 80 40 00	 00:56:11.783  WRITE FPDMA QUEUED   
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:11.782  READ FPDMA QUEUED	
  2f 00 00 00 01 00 00 00 00 00 10 00 00	 00:56:11.701  READ LOG EXT		 
  60 00 00 00 30 00 00 13 94 2b 40 40 00	 00:56:08.632  READ FPDMA QUEUED	
  25 00 00 00 40 00 00 13 94 2b 00 40 00	 00:56:05.751  READ DMA EXT		 
																				
SMART Extended Self-test Log Version: 1 (1 sectors)							 
No self-tests have been logged.  [To run self-tests, use: smartctl -t]		 
																				
																				
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.	 
																				
Warning: device does not support SCT Data Table command						 
Warning: device does not support SCT Error Recovery Control command			 
SATA Phy Event Counters (GP Log 0x11)										   
ID	  Size	 Value  Description											 
0x000a  2			3  Device-to-host register FISes sent due to a COMRESET	
0x0001  2			0  Command failed due to ICRC error						
0x0003  2			0  R_ERR response for device-to-host data FIS			 
0x0004  2			0  R_ERR response for host-to-device 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 
 


Quite a bit of stuff! Mike
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Indeed, quite a bit of stuff. And it's showing some problems. This disk has never run a SMART self-test, and it's showing hundreds of bad blocks (see fields 187, 197, and 198). That's probably the cause of the "error=5" messages you're seeing. Running badblocks on the disk might force it to remap some (perhaps all) of the bad blocks, but that's destructive, so probably not what you want to do.

Let's kick off SMART tests on both disks. smartctl -t long /dev/ada0, and then do the same with ada1. They'll run completely in the background and won't produce any output, but when you run the command, it should give you an indication of when the test will be complete.

Edit: It's normal for long SMART tests (which is what the command above calls for) to take several hours to complete. You'll need to leave the machine running during that time, but they won't interfere with anything else you'd be doing with it.
 
Last edited:

Mike Zahorik

Explorer
Joined
Mar 14, 2013
Messages
62
OK, they are off and running. The response mentions that this will take 2 hours to complete. Mike
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Yes, but you only gave the output of smartctl -x for one of them. Can you post the output for the other drive? It won't interrupt the self-test.
 

Mike Zahorik

Explorer
Joined
Mar 14, 2013
Messages
62
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p5 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda (SATA 3Gb/s, 4K Sectors)
Device Model: ST1000DM003-1CH162
Serial Number: S1D8K2WJ
LU WWN Device Id: 5 000c50 05c1a95c7
Firmware Version: CC46
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon May 29 15:50:27 2017 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 1 (minimum power consumption with standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
=== 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: ( 248) Self-test routine in progress...
80% of test remaining.
Total time to complete Offline
data collection: ( 584) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off supp
ort.
Suspend Offline collection upon new
command.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 110) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 116 099 006 - 115012288
3 Spin_Up_Time PO---- 097 097 000 - 0
4 Start_Stop_Count -O--CK 041 041 020 - 61015
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 064 060 030 - 3020087
9 Power_On_Hours -O--CK 083 083 000 - 14936
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 099 099 020 - 1628
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
188 Command_Timeout -O--CK 100 100 000 - 0
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 067 063 045 - 33 (0 122 33 26 0)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 100 100 000 - 72
193 Load_Cycle_Count -O--CK 056 056 000 - 88231
194 Temperature_Celsius -O---K 033 040 000 - 33 (128 0 0 0 0)
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 164398463201702
241 Total_LBAs_Written ------ 100 253 000 - 479891446
242 Total_LBAs_Read ------ 100 253 000 - 1710435058
||||||_ 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]
GP/S Log at address 0x00 has 1 sectors [Log Directory]
SMART Log at address 0x01 has 1 sectors [Summary SMART error log]
SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log]
GP Log at address 0x03 has 5 sectors [Ext. Comprehensive SMART error log]
SMART Log at address 0x06 has 1 sectors [SMART self-test log]
GP Log at address 0x07 has 1 sectors [Extended self-test log]
SMART Log at address 0x09 has 1 sectors [Selective self-test log]
GP Log at address 0x10 has 1 sectors [NCQ Command Error log]
GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters]
GP Log at address 0x21 has 1 sectors [Write stream error log]
GP Log at address 0x22 has 1 sectors [Read stream error log]
GP/S Log at address 0x80 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x81 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x82 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x83 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x84 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x85 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x86 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x87 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x88 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x89 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8f has 16 sectors [Host vendor specific log]
GP/S Log at address 0x90 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x91 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x92 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x93 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x94 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x95 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x96 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x97 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x98 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x99 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9f has 16 sectors [Host vendor specific log]
GP/S Log at address 0xa1 has 20 sectors [Device vendor specific log]
GP Log at address 0xa2 has 4496 sectors [Device vendor specific log]
GP/S Log at address 0xa8 has 129 sectors [Device vendor specific log]
GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log]
GP Log at address 0xab has 1 sectors [Device vendor specific log]
GP Log at address 0xb0 has 5176 sectors [Device vendor specific log]
GP Log at address 0xbe has 65535 sectors [Device vendor specific log]
GP Log at address 0xbf has 65535 sectors [Device vendor specific log]
GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log]
GP/S Log at address 0xc1 has 10 sectors [Device vendor specific log]
GP/S Log at address 0xc4 has 5 sectors [Device vendor specific log]
GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status]
GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (5 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 Self-test routine in progress 80% 14936 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
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.

Warning: device does not support SCT Data Table command
Warning: device does not support SCT Error Recovery Control command
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 3 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device 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
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
OK, that one's looking a lot better--no issues I see other than the high load cycle count (which is also high with the other one, but that one has bigger problems). Your data should be fine, though without the data integrity features of ZFS it's impossible to say for sure. Expect that, at a minimum, you're going to need to replace the first disk.

You might want to consider a new system, which you should be able to do for about $500. More details later.
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
How full is your NAS? How much space are you using?
 
Status
Not open for further replies.
Top