Is this hard drive dying? SmartCtl Extended test also not progressing

Status
Not open for further replies.

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
Hi All,

I have finally started to make my NAS Server and before I got a chance to set the pool up FreeNAS gave me a warning telling me that one of my drives had issues.

When I checked the issues there are around 3543 Uncorrectable Sectors / Pending Sectors does this mean that they are all marked as bad?

What makes me question this that if I read the SMART info below the errors were detected when the drive was 77 hours old it is now nearly 4000 hours old and not had any errors since then or issues. The drive was being used as Media Storage and was nearly at capacity most of the time when it was in my old server.

Now I ran the extended test on SMART and it says it is going to take 15 hours to complete which I guess is fair enough as its a big drive however what is concerning me more is that 5 hours in and it still says there is 90% remaining and the progress hasnt increased at all.. Is this normal? The disk is idle as I havent created a pool yet so I know it is not usage that is causing the extra delay. If there is a read error does the SMART test just fail or will it run for ever more?

If it makes any difference the drive is a Seagate SMR Drive,.

I have attached my hardware and the extended results below:


Hardware:

FreeNAS 9.10 U2
ESXi Whitebox running on Asus P87QM-E Motherboard
LSI 9211-8i Running in pass through
16GB DDR3 RAM
Not Set Up A Pool yet



Code:
=== 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:	  ( 249) Self-test routine in progress...
										90% of test remaining.
Total time to complete Offline
data collection:				(	0) seconds.
Offline data collection
capabilities:					(0x7b) SMART execute Offline immediate.
										Auto Offline data collection on/off supp																																																											 ort.
										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:		(   1) minutes.
Extended self-test routine
recommended polling time:		( 932) minutes.
Conveyance self-test routine
recommended polling time:		(   2) minutes.
SCT capabilities:			  (0x30a5) SCT Status supported.
										SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x000f   119   099   006	Pre-fail  Always	   -	   231011232
  3 Spin_Up_Time			0x0003   092   091   000	Pre-fail  Always	   -	   0
  4 Start_Stop_Count		0x0032   100   100   020	Old_age   Always	   -	   236
  5 Reallocated_Sector_Ct   0x0033   100   100   010	Pre-fail  Always	   -	   1
  7 Seek_Error_Rate		 0x000f   081   060   030	Pre-fail  Always	   -	   4436110005
  9 Power_On_Hours		  0x0032   096   096   000	Old_age   Always	   -	   3852
 10 Spin_Retry_Count		0x0013   100   100   097	Pre-fail  Always	   -	   0
 12 Power_Cycle_Count	   0x0032   100   100   020	Old_age   Always	   -	   214
183 Runtime_Bad_Block	   0x0032   100   100   000	Old_age   Always	   -	   0
184 End-to-End_Error		0x0032   100   100   099	Old_age   Always	   -	   0
187 Reported_Uncorrect	  0x0032   089   089   000	Old_age   Always	   -	   11
188 Command_Timeout		 0x0032   100   098   000	Old_age   Always	   -	   8590065666
189 High_Fly_Writes		 0x003a   100   100   000	Old_age   Always	   -	   0
190 Airflow_Temperature_Cel 0x0022   060   052   045	Old_age   Always	   -	   40 (Min/Max 37/40)
191 G-Sense_Error_Rate	  0x0032   100   100   000	Old_age   Always	   -	   0
192 Power-Off_Retract_Count 0x0032   100   100   000	Old_age   Always	   -	   323
193 Load_Cycle_Count		0x0032   099   099   000	Old_age   Always	   -	   2965
194 Temperature_Celsius	 0x0022   040   048   000	Old_age   Always	   -	   40 (0 21 0 0 0)
195 Hardware_ECC_Recovered  0x001a   119   099   000	Old_age   Always	   -	   231011232
197 Current_Pending_Sector  0x0012   090   090   000	Old_age   Always	   -	   3543
198 Offline_Uncorrectable   0x0010   090   090   000	Old_age   Offline	  -	   3543
199 UDMA_CRC_Error_Count	0x003e   200   200   000	Old_age   Always	   -	   0
240 Head_Flying_Hours	   0x0000   100   253   000	Old_age   Offline	  -	   3795 (49 124 0)
241 Total_LBAs_Written	  0x0000   100   253   000	Old_age   Offline	  -	   39614232638
242 Total_LBAs_Read		 0x0000   100   253   000	Old_age   Offline	  -	   34401743240


SMART Error Log Version: 1
ATA Error Count: 11 (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 11 occurred at disk power-on lifetime: 77 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 01 ff ff ff 4f 00	  00:39:52.100  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.100  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.099  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.099  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.099  READ FPDMA QUEUED

Error 10 occurred at disk power-on lifetime: 77 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 3f ff ff ff 4f 00	  00:39:49.294  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.293  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.293  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.293  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.292  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:25.359  READ DMA EXT
  ef 10 02 00 00 00 a0 00	  00:07:25.358  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00	  00:07:25.358  READ NATIVE MAX ADDRESS EXT [OBS-AC																																																											 S-3]
  ec 00 00 00 00 00 a0 00	  00:07:25.357  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00	  00:07:25.357  SET FEATURES [Set transfer mode]

Error 8 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:22.576  READ DMA EXT
  ef 10 02 00 00 00 a0 00	  00:07:22.575  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00	  00:07:22.575  READ NATIVE MAX ADDRESS EXT [OBS-AC																																																											 S-3]
  ec 00 00 00 00 00 a0 00	  00:07:22.574  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00	  00:07:22.574  SET FEATURES [Set transfer mode]

Error 7 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:19.752  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.750  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	Self-test routine in progress 90%	  3852		 -
# 2  Short offline	   Completed: read failure	   90%		78		 -
# 3  Short offline	   Completed: read failure	   90%		78		 -
# 4  Short offline	   Completed: read failure	   90%		78		 -
# 5  Short offline	   Completed: read failure	   90%		77		 -
# 6  Short offline	   Completed: read failure	   10%		76		 -
# 7  Extended offline	Completed: read failure	   90%		76		 -
# 8  Short offline	   Completed: read failure	   90%		76		 -

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] ~#


 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Yeah, doesn't look good at all. It's dead, Jim.
 

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
Yeah, doesn't look good at all. It's dead, Jim.
I hope not, But I think you are right, There is no warranty left on the drive either annoyingly.

Weird thing is the estimation for the long test was 15 hours and now 15 hours has passed and its still showing 90% Remaining how can I tell if it is actually doing anything at all?

Code:
[root@freenas] ~# smartctl -a /dev/da2 | grep remaining
										90% of test remaining
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
It's going nowhere, it's failed every SMART test, long and short.
 

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
Most of them in the first 3 days of runtime :eek:

And yet bizzarrely its been running a media share for months and months with transcoding and plex on it haha so no idea what that is all about, I think I am going to play it safe and swap it out but I am not going to bin it I think I will re-use it as scratch / Temporary storage. I always wondered if it was perhaps just buggy firmware as there was a power failure at some point when the drive was being filled in the first instance which makes me wonder if that caused the SMART stats and whether it can be fixed. Hangs during both SMART tests but I still cant get over how it still works 100% lol its a bloody oddity thats for sure lol
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
its been running a media share for months
Just because a drive has bad sectors, doesn't mean it can't store and retrieve data from the good sectors. Even on this drive, the bad sectors probably represent a tiny fraction of the total.

Did you burn it in with badblocks?
 

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
Just because a drive has bad sectors, doesn't mean it can't store and retrieve data from the good sectors. Even on this drive, the bad sectors probably represent a tiny fraction of the total.

Did you burn it in with badblocks?


Hi Robert, No didn't burn it in total Newbie mistake back when I got the drive still in a bit of a quandry what to do with the disk, Would bad blocks running on it now force it to reallocate the bad sectors or mark them as bad for good or is it past that?

I couldnt put it in the RaidZ if I tried anyway as FreeNAS would just throw it out and would be pretty silly anyway as SMART cant be wrong can it ??
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
When SMART tests fail consistently, it's generally hopeless.
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
The drive is out the pool anyway but I think I am going to run BadBlocks on it to see what happens, I had a look online against it and some people say it is a waste of time and just to run e2fsck instead, What is the generally best method to try here more for my curiosity than anything else I dont plan to redeploy is back into the pool
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
e2fsck would be completely useless here--it's a filesystem check tool for ext2fs, which is (well, was) used by many flavors of Linux. Nothing in FreeNAS uses, or has ever used, ext2fs. badblocks is going to be the best tool for this, at least among widely-available Unix-y tools.
 

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
e2fsck would be completely useless here--it's a filesystem check tool for ext2fs, which is (well, was) used by many flavors of Linux. Nothing in FreeNAS uses, or has ever used, ext2fs. badblocks is going to be the best tool for this, at least among widely-available Unix-y tools.
Thanks for this I never even made the connection that there would need to be a file system on this drive first!! Bad Blocks it is then!
 

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
How is this for totally bizarre and odd, Its Fixed!!!

This makes it even more confusing and more likely to be a firmware bug due to a power outage mid write.

I thought I would come back here after running the following processes that CyberJock mentioned on another post:

Code:
1.  dd if=/dev/zero of=/dev/da2 bs=1M
2.  badblocks -svw -t 0xFE /dev/da2
3. smartctl -t long /dev/da2
4. smartctl -a /dev/da2).


Now the smart results show:

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

Device is:		In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Thu Apr 27 01:56:36 2017 PDT
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:				(	0) 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:		(   1) minutes.
Extended self-test routine
recommended polling time:		( 932) minutes.
Conveyance self-test routine
recommended polling time:		(   2) minutes.
SCT capabilities:			  (0x30a5) SCT Status supported.
										SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x000f   110   099   006	Pre-fail  Always	   -	   27485488
  3 Spin_Up_Time			0x0003   092   091   000	Pre-fail  Always	   -	   0
  4 Start_Stop_Count		0x0032   100   100   020	Old_age   Always	   -	   236
  5 Reallocated_Sector_Ct   0x0033   100   100   010	Pre-fail  Always	   -	   8
  7 Seek_Error_Rate		 0x000f   081   060   030	Pre-fail  Always	   -	   4447700574
  9 Power_On_Hours		  0x0032   096   096   000	Old_age   Always	   -	   4044
 10 Spin_Retry_Count		0x0013   100   100   097	Pre-fail  Always	   -	   0
 12 Power_Cycle_Count	   0x0032   100   100   020	Old_age   Always	   -	   214
183 Runtime_Bad_Block	   0x0032   100   100   000	Old_age   Always	   -	   0
184 End-to-End_Error		0x0032   100   100   099	Old_age   Always	   -	   0
187 Reported_Uncorrect	  0x0032   089   089   000	Old_age   Always	   -	   11
188 Command_Timeout		 0x0032   100   098   000	Old_age   Always	   -	   12885098499
189 High_Fly_Writes		 0x003a   100   100   000	Old_age   Always	   -	   0
190 Airflow_Temperature_Cel 0x0022   063   052   045	Old_age   Always	   -	   37 (Min/Max 37/41)
191 G-Sense_Error_Rate	  0x0032   100   100   000	Old_age   Always	   -	   0
192 Power-Off_Retract_Count 0x0032   100   100   000	Old_age   Always	   -	   324
193 Load_Cycle_Count		0x0032   099   099   000	Old_age   Always	   -	   2979
194 Temperature_Celsius	 0x0022   037   048   000	Old_age   Always	   -	   37 (0 21 0 0 0)
195 Hardware_ECC_Recovered  0x001a   110   099   000	Old_age   Always	   -	   27485488
197 Current_Pending_Sector  0x0012   100   090   000	Old_age   Always	   -	   0
198 Offline_Uncorrectable   0x0010   100   090   000	Old_age   Offline	  -	   0
199 UDMA_CRC_Error_Count	0x003e   200   200   000	Old_age   Always	   -	   0
240 Head_Flying_Hours	   0x0000   100   253   000	Old_age   Offline	  -	   3848 (60 145 0)
241 Total_LBAs_Written	  0x0000   100   253   000	Old_age   Offline	  -	   64013360110
242 Total_LBAs_Read		 0x0000   100   253   000	Old_age   Offline	  -	   50029806627

SMART Error Log Version: 1
ATA Error Count: 11 (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 11 occurred at disk power-on lifetime: 77 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 01 ff ff ff 4f 00	  00:39:52.100  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.100  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.099  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.099  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00	  00:39:52.099  READ FPDMA QUEUED

Error 10 occurred at disk power-on lifetime: 77 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 3f ff ff ff 4f 00	  00:39:49.294  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.293  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.293  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.293  READ FPDMA QUEUED
  60 00 3f ff ff ff 4f 00	  00:39:49.292  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:25.359  READ DMA EXT
  ef 10 02 00 00 00 a0 00	  00:07:25.358  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00	  00:07:25.358  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00	  00:07:25.357  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00	  00:07:25.357  SET FEATURES [Set transfer mode]

Error 8 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:22.576  READ DMA EXT
  ef 10 02 00 00 00 a0 00	  00:07:22.575  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00	  00:07:22.575  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00	  00:07:22.574  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00	  00:07:22.574  SET FEATURES [Set transfer mode]

Error 7 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:19.752  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.750  READ DMA 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%	  4044		 -
# 2  Extended offline	Completed without error	   00%	  3864		 -
# 3  Extended offline	Aborted by host			   10%	  3863		 -

  ef 10 02 00 00 00 a0 00	  00:07:25.358  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00	  00:07:25.358  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00	  00:07:25.357  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00	  00:07:25.357  SET FEATURES [Set transfer mode]

Error 8 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:22.576  READ DMA EXT
  ef 10 02 00 00 00 a0 00	  00:07:22.575  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00	  00:07:22.575  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00	  00:07:22.574  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00	  00:07:22.574  SET FEATURES [Set transfer mode]

Error 7 occurred at disk power-on lifetime: 75 hours (3 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff ef 00	  00:07:19.752  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.751  READ DMA EXT
  25 00 08 ff ff ff ef 00	  00:07:19.750  READ DMA 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%	  4044		 -
# 2  Extended offline	Completed without error	   00%	  3864		 -
# 3  Extended offline	Aborted by host			   10%	  3863		 -
# 4  Short offline	   Completed: read failure	   90%		78		 -
# 5  Short offline	   Completed: read failure	   90%		78		 -
# 6  Short offline	   Completed: read failure	   90%		78		 -
# 7  Short offline	   Completed: read failure	   90%		77		 -
# 8  Short offline	   Completed: read failure	   10%		76		 -
# 9  Extended offline	Completed: read failure	   90%		76		 -
#10  Short offline	   Completed: read failure	   90%		76		 -


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.

 

nojohnny101

Wizard
Joined
Dec 3, 2015
Messages
1,478
Yea that drive is dead. Replace it.
 

Dice

Wizard
Joined
Dec 11, 2015
Messages
1,410
<was> that a seagate drive?
 

nojohnny101

Wizard
Joined
Dec 3, 2015
Messages
1,478

Crm

Dabbler
Joined
Sep 14, 2015
Messages
27
Well it seems that you are having "pre-fail" on a number of the important parameters to watch on smart test results.

Example, #5, reallocated sectors, shows pre-fail and this usually ends up in an RMA.
See hard drive troubleshooting resource if you want go through it yourself:
https://forums.freenas.org/index.ph...bleshooting-guide-all-versions-of-freenas.17/

What drive are you using again?
Hi there. It's a Seagate Archive SMR hard drive..

I just thought given in had 3000 pending sectors before and I've done a full zero fill and a bad blocks that it has now realised those sectors aren't infact bad and that it's a bug / power outage issue.
 
Status
Not open for further replies.
Top