Disk Failure?

Status
Not open for further replies.

nick3333

Cadet
Joined
Dec 16, 2018
Messages
3
Been using Freenas for over a year never had a errors. Just got new hardware and it has been running for about three weeks.
These are two Seagate IronWolf 3TB in Raid 0. all the data is back up on other computers because of the new setup
one started throwing errors. Dont have a replacement disk. after finishing writing this pretty sure its a failure, just looking look for someone to to decode the error.

Thanks,

Code:
Dec 16 08:28:57 freenas2 smartd[3053]: Device: /dev/da3 [SAT], 1400 Currently unreadable (pending) sectors

Dec 16 08:28:57 freenas2 smartd[3053]: Device: /dev/da3 [SAT], 1400 Offline uncorrectable sectors





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 ===
Model Family:     Seagate IronWolf
Device Model:     ST3000VN007-2E4166
LU WWN Device Id: 5 000c50 0b395b99f

Firmware Version: SC60
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5900 rpm
Form Factor:      3.5 inches
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:    Sun Dec 16 08:35:02 2018 PST
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:                (  107) 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:        ( 388) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x10bd) 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   094   094   006    Pre-fail  Always       -       56282806
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       85517
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       367
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   030   030   000    Old_age   Always       -       70
188 Command_Timeout         0x0032   093   093   000    Old_age   Always       -       7
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       205
190 Airflow_Temperature_Cel 0x0022   072   069   045    Old_age   Always       -       28 (Min/Max 20/31)
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       -       1
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   028   040   000    Old_age   Always       -       28 (0 20 0 0 0)
197 Current_Pending_Sector  0x0012   092   092   000    Old_age   Always       -       1400
198 Offline_Uncorrectable   0x0010   092   092   000    Old_age   Offline      -       1400
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 70 (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 70 occurred at disk power-on lifetime: 359 hours (14 days + 23 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 98 ff ff ff 4f 00  14d+23:00:46.483  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:46.483  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:46.483  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:46.483  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:46.483  WRITE FPDMA QUEUED

Error 69 occurred at disk power-on lifetime: 359 hours (14 days + 23 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  14d+23:00:36.972  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:36.972  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:36.972  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:36.972  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  14d+23:00:36.972  WRITE FPDMA QUEUED

Error 68 occurred at disk power-on lifetime: 359 hours (14 days + 23 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  14d+23:00:30.770  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00  14d+23:00:30.769  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00  14d+23:00:30.765  WRITE FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:30.745  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:30.745  READ FPDMA QUEUED

Error 67 occurred at disk power-on lifetime: 359 hours (14 days + 23 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 98 ff ff ff 4f 00  14d+23:00:19.746  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:19.746  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:19.746  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:19.746  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:19.746  READ FPDMA QUEUED

Error 66 occurred at disk power-on lifetime: 359 hours (14 days + 23 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 90 02 40 40 00  14d+23:00:14.457  WRITE FPDMA QUEUED
  60 00 10 ff ff ff 4f 00  14d+23:00:14.456  READ FPDMA QUEUED
  60 00 10 ff ff ff 4f 00  14d+23:00:14.455  READ FPDMA QUEUED
  60 00 10 90 02 40 40 00  14d+23:00:14.455  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  14d+23:00:14.455  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
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.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
in Raid 0.
We don't use that terminology. You should review the following documentation to understand the technology and words that describe it:

Updated Forum Rules 12/5/18
https://forums.freenas.org/index.php?threads/updated-forum-rules-12-5-18.45124/

Slideshow explaining VDev, zpool, ZIL and L2ARC
https://forums.freenas.org/index.ph...ning-vdev-zpool-zil-and-l2arc-for-noobs.7775/

Terminology and Abbreviations Primer
https://forums.freenas.org/index.php?threads/terminology-and-abbreviations-primer.28174/

Why not to use RAID-5 or RAIDz1
https://www.zdnet.com/article/why-raid-5-stops-working-in-2009/
Device: /dev/da3
This is one of the drives in your system.
1400 Offline uncorrectable sectors
This is the number of bad sectors it had when the error was generated.

You need to get any data that you can out of this system as soon as possible and remove the defective drive. Send it back for warranty replacement. Hopefully, your system is still within the burn-in process and you have not loaded data onto it yet. I don't get the impression that you did that though. Here is a setup guide that will explain how you should commission a new server:

Uncle Fester's Basic FreeNAS Configuration Guide
https://www.familybrown.org/dokuwiki/doku.php?id=fester:intro
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
That drive is toast. You also don't have periodic smart tests enabled which you should have.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
periodic smart tests ? I have long and short self SMART test setup.
From the output you posted:
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
 
Status
Not open for further replies.
Top