BUILD How bad is it, doc?

Freenas User 2525 · Jun 5, 2016

Got a weird error and started looking into it, only to realize I don't know what I'm doing. I guess that's a good thing though, since I've been using it for years with almost no effort required to maintain it.

I know I need to rebuild since it was slapped together with spare parts to begin with, but what I'm looking for here is whether I should be sacrificing my rent to pay for it, or can it wait another month or so?

Here's the error I got:

> (ada2:ahcich2:0:0:0): Retrying command
> (ada2:ahcich2:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 a0 6a 70 40 74 00 00 00 00 00
> (ada2:ahcich2:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich2:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
> (ada2:ahcich2:0:0:0): RES: 41 40 68 6b 70 00 74 00 00 e0 00
> (ada2:ahcich2:0:0:0): Retrying command

Digging around I found a script to run a health check, but I'm not really sure how to interpret it. Help?

joeschmuck · Jun 5, 2016

Doesn't look bad at the moment but you haven't done any SMART tests on this drive in over 10000 hours. Run a Long test and get back to us. Also, have you looked at the Troubleshooting Guides section, I have a simple guide to help out users to diagnose the problem.

Freenas User 2525 · Jun 5, 2016

I did `smartctl -t long /dev/ada2` and it told me to wait 181 minutes. I did, and it still says PASSED, but there's a whole lot of information here. I was on my phone earlier so I didn't think to run tests on my other drives. I've started that and can check back tomorrow. I thought freenas ran scrubs and smart tests automatically? [edit: ohh, you have to specifically schedule them. doh.]

What specifically should I be looking at?

Code:

smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p15 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST31000528AS
Serial Number:    5Vxxxxxx
LU WWN Device Id: 5 000c50 0249f108c
Firmware Version: CC38
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sun Jun  5 16:10:39 2016 EDT

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213891en

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:      ( 121) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (  609) 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:        ( 181) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control 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   114   099   006    Pre-fail  Always       -       66631322
  3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1139
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       27
  7 Seek_Error_Rate         0x000f   077   063   030    Pre-fail  Always       -       56362198
  9 Power_On_Hours          0x0032   065   065   000    Old_age   Always       -       31053
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       60
183 Runtime_Bad_Block       0x0032   089   089   000    Old_age   Always       -       11
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   046   046   000    Old_age   Always       -       54
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       4295032833
189 High_Fly_Writes         0x003a   091   091   000    Old_age   Always       -       9
190 Airflow_Temperature_Cel 0x0022   060   048   045    Old_age   Always       -       40 (Min/Max 25/46)
194 Temperature_Celsius     0x0022   040   052   000    Old_age   Always       -       40 (0 22 0 0 0)
195 Hardware_ECC_Recovered  0x001a   039   019   000    Old_age   Always       -       66631322
197 Current_Pending_Sector  0x0012   099   099   000    Old_age   Always       -       69
198 Offline_Uncorrectable   0x0010   099   099   000    Old_age   Offline      -       69
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       192788197031801
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       415139417
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1460604520

SMART Error Log Version: 1
ATA Error Count: 10 (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 10 occurred at disk power-on lifetime: 31037 hours (1293 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      06:21:15.007  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:15.007  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      06:21:14.922  READ LOG EXT
  60 00 01 ff ff ff 4f 00      06:21:11.894  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:11.894  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 31037 hours (1293 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      06:21:11.894  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:11.894  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      06:21:11.800  READ LOG EXT
  60 00 01 ff ff ff 4f 00      06:21:08.787  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:08.786  READ FPDMA QUEUED

Error 8 occurred at disk power-on lifetime: 31037 hours (1293 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      06:21:08.787  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:08.786  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      06:21:08.778  READ LOG EXT
  60 00 01 ff ff ff 4f 00      06:21:05.761  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:05.761  READ FPDMA QUEUED

Error 7 occurred at disk power-on lifetime: 31037 hours (1293 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      06:21:05.761  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:05.761  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00      06:21:05.639  READ LOG EXT
  60 00 01 ff ff ff 4f 00      06:21:02.624  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00      06:21:02.624  READ FPDMA QUEUED

Error 6 occurred at disk power-on lifetime: 31037 hours (1293 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      06:21:02.624  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00      06:21:02.624  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      06:21:02.618  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00      06:21:02.608  READ FPDMA QUEUED
  60 00 01 ff ff ff 4f 00      06:21:02.607  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     31048         1953524891
# 2  Extended offline    Completed: read failure       90%     30599         1953524584
# 3  Short offline       Completed without error       00%     20207         -
# 4  Extended offline    Completed without error       00%     20186         -
# 5  Short offline       Completed without error       00%     20159         -
# 6  Short offline       Completed without error       00%     20111         -
# 7  Short offline       Completed without error       00%     20024         -
# 8  Short offline       Completed without error       00%     19976         -
# 9  Short offline       Completed without error       00%     19928         -
#10  Short offline       Completed without error       00%     19880         -
#11  Extended offline    Completed without error       00%     19860         -
#12  Short offline       Completed without error       00%     19832         -
#13  Short offline       Completed without error       00%     19784         -
#14  Short offline       Completed without error       00%     19736         -
#15  Short offline       Completed without error       00%     19688         -
#16  Short offline       Completed without error       00%     19664         -
#17  Short offline       Completed without error       00%     19616         -
#18  Short offline       Completed without error       00%     19568         -
#19  Short offline       Completed without error       00%     19520         -
#20  Short offline       Completed without error       00%     19472         -
#21  Extended offline    Completed without error       00%     19452         -

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.

danb35 · Jun 5, 2016

Your last two long SMART tests on this drive have failed, and the stats are showing dozens of bad sectors. You should plan on replacing the drive very soon.

Mirfster · Jun 5, 2016

I vote to change the suggestion of "You should plan on replacing the drive very soon." to "Now"... if said drive is a part of either vDev in Pool "Vault":

pool: Vault
state: ONLINE
scan: scrub repaired 0 in 1h29m with 0 errors on Sun Jun 5 01:29:53 2016
config:

NAME STATE READ WRITE CKSUM
Vault ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/1d3fac9c-bed9-11e4-9e11-1c6f654928ce ONLINE 0 0 0
gptid/1d921bb0-bed9-11e4-9e11-1c6f654928ce ONLINE 0 0 0
gptid/1de2e8ad-bed9-11e4-9e11-1c6f654928ce ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
gptid/1e4484e4-bed9-11e4-9e11-1c6f654928ce ONLINE 0 0 0
gptid/1ea40ee1-bed9-11e4-9e11-1c6f654928ce ONLINE 0 0 0

Mirfster · Jun 5, 2016

Freenas User 2525 said:
Digging around I found a script to run a health check, but I'm not really sure how to interpret it. Help?

Here is a start: https://en.wikipedia.org/wiki/S.M.A.R.T.
Reference section "Known ATA S.M.A.R.T. attributes" primarily those highlighted

danb35 · Jun 6, 2016

Mirfster said:
I vote to change the suggestion of "You should plan on replacing the drive very soon." to "Now"... if said drive is a part of either vDev in Pool "Vault":

Agreed. I'd further vote to migrate the data off Vault and rebuild it properly, but that doesn't need to be immediate.

Jailer · Jun 6, 2016

Mirfster said:
I vote to change the suggestion of "You should plan on replacing the drive very soon." to "Now"... if said drive is a part of either vDev in Pool "Vault":

You should see the smart log from the Seagate drive in my pfsense rig. :D

Mirfster · Jun 6, 2016

Jailer said:
You should see the smart log from the Seagate drive in my pfsense rig. :D

Hah, go ahead post it. I'm sure we will all get a kick out of it. ;)

joeschmuck · Jun 6, 2016

ID's 5, 197, and 198 along with the fact that your SMART long test failed are very clear indications that your drive is bad. You really need to setup routine SMART testing or you are looking for real problems. Run a SMART long test on all your other drives as well, you can start them all at the same time and then just wait for the tests to complete.

If you are running anything less than a RAIDZ2 then backup any data you want to keep right now. If you have a RAIDZ2 then you can just replace the failed drive using the user guide instructions. If you run the long tests and fine similar issues, again, save off your data now.

I can't stress enough how important routine SMART testing is.

Jailer · Jun 6, 2016

Mirfster said:
Hah, go ahead post it. I'm sure we will all get a kick out of it. ;)

Code:

smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.3-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.8
Device Model: ST3250823AS
Serial Number: 3ND01VNZ
Firmware Version: 3.01
User Capacity: 250,058,268,160 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Mon Jun 6 17:58:20 2016 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: ( 430) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 84) minutes.
SCT capabilities: (0x0001) SCT Status 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 051 045 006 Pre-fail Always - 172956950
3 Spin_Up_Time 0x0003 098 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 093 093 020 Old_age Always - 7169
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 75243848
9 Power_On_Hours 0x0032 026 026 000 Old_age Always - 65330
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 094 094 020 Old_age Always - 7016
194 Temperature_Celsius 0x0022 031 055 000 Old_age Always - 31 (0 14 0 0 0)
195 Hardware_ECC_Recovered 0x001a 051 045 000 Old_age Always - 172956950
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 835 (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 835 occurred at disk power-on lifetime: 31001 hours (1291 days + 17 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
-- -- -- -- -- -- --
10 51 01 2e 51 1c ed

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 00 01 2e 51 1c ed 00 20:04:23.699 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 00 2e 51 1c e0 00 20:04:23.572 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 00 2e 51 1c ed 00 20:04:23.572 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 01 2e 51 1c e0 00 20:04:21.433 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 01 2e 51 1c ed 00 20:04:21.433 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 834 occurred at disk power-on lifetime: 31001 hours (1291 days + 17 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
-- -- -- -- -- -- --
10 51 01 2e 51 1c ed

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 00 01 2e 51 1c ed 00 20:04:18.465 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 00 2e 51 1c e0 00 20:04:18.464 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 00 2e 51 1c ed 00 20:04:18.464 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 01 6f 59 1c e0 00 20:04:21.433 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
29 00 01 6f 59 1c e0 00 20:04:21.433 READ MULTIPLE EXT

Error 833 occurred at disk power-on lifetime: 30994 hours (1291 days + 10 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
-- -- -- -- -- -- --
10 51 01 2e 51 1c ed

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 00 01 2e 51 1c ed 00 12:54:15.930 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 00 2e 51 1c e0 00 12:54:15.930 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 00 2e 51 1c ed 00 12:54:20.716 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 01 2e 51 1c e0 00 12:54:20.716 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 01 2e 51 1c ed 00 12:54:20.589 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 832 occurred at disk power-on lifetime: 30994 hours (1291 days + 10 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
-- -- -- -- -- -- --
10 51 01 2e 51 1c ed

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 00 01 2e 51 1c ed 00 12:54:15.930 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 00 2e 51 1c e0 00 12:54:15.930 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 00 2e 51 1c ed 00 12:54:15.930 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 01 6f 59 1c e0 00 12:54:15.483 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
29 00 01 6f 59 1c e0 00 12:54:15.483 READ MULTIPLE EXT

Error 831 occurred at disk power-on lifetime: 30994 hours (1291 days + 10 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
-- -- -- -- -- -- --
10 51 01 2e 51 1c ed

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 00 01 2e 51 1c ed 00 12:50:41.622 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 00 2e 51 1c e0 00 12:50:41.622 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 00 2e 51 1c ed 00 12:50:39.483 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 00 01 2e 51 1c e0 00 12:50:39.483 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 00 01 2e 51 1c ed 00 12:50:39.357 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]

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% 65278 -
# 2 Extended offline Completed without error 00% 63303 -
# 3 Short offline Completed without error 00% 63301 -

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.

:D

joeschmuck · Jun 6, 2016

No Way, almost 7 1/2 years run time!

Jailer · Jun 6, 2016

And hasn't had an error in over 30K hours. :D

Mirfster · Jun 6, 2016

joeschmuck said:
No Way, almost 7 1/2 years run time!

That little 250 GB drive just won't die. ;)

Jailer · Jun 6, 2016

Don't let @DrKK know a Seagate drive has lasted this long.

joeschmuck · Jun 7, 2016

Jailer said:
Don't let @DrKK know a Seagate drive has lasted this long.

Seagate use to be a good drive, apparently 7.5 years ago they were making a few good drives.

Important Announcement for the TrueNAS Community.

BUILD How bad is it, doc?

Freenas User 2525

Cadet

Attachments

joeschmuck

Old Man

Freenas User 2525

Cadet

danb35

Hall of Famer

Mirfster

Doesn't know what he's talking about

Mirfster

Doesn't know what he's talking about

danb35

Hall of Famer

Jailer

Not strong, but bad

Mirfster

Doesn't know what he's talking about

joeschmuck

Old Man

Jailer

Not strong, but bad

joeschmuck

Old Man

Jailer

Not strong, but bad

Mirfster

Doesn't know what he's talking about

Jailer

Not strong, but bad

joeschmuck

Old Man

Similar threads