Drive Replaced - marked as bad almost immediately

[Micheal Shallop]

Hey all,

I'm still figuring out stuffs here... basically, for about the last two months, I've been getting warnings about a imminent drive failure. The day finally arrived where the drive failed completely following an OS update, and I replaced the physical drive with a identical (make/model) replacement unit.

Within 24-hours, this drive was flagged as bad, removed from the pool, and the state downrev'd to degraded.

These are 3TB Seagate drives. The failing drive physically is located at the bottom of a 4-drive stack in the case.

zpool and smartctl output follows.

I am wondering if I have larger issues - such as bad DMA controller, cable, poor ventilation, that's causing the same drive to fail... or was this just dumb luck?

Also, I updated (the OS) and rebooted and the drive is still marked as offline.

Is there a way to "replace" it without removing it a forcing a resilver? Or was there something in the below output that says: this drive is toast.

Thanks!

--mike

Code:

# zpool status -v
  pool: cmv1
state: DEGRADED
status: One or more devices could not be opened.  Sufficient replicas exist for
    the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://illumos.org/msg/ZFS-8000-2Q
  scan: scrub repaired 0 in 5h52m with 0 errors on Mon Nov  2 13:31:21 2015
config:

    NAME                                            STATE     READ WRITE CKSUM
    cmv1                                            DEGRADED     0     0     0
      raidz2-0                                      DEGRADED     0     0     0
        gptid/e8edd6b3-c76f-11e3-9218-e03f49abb2ba  ONLINE       0     0     0
        13440795819143157447                        UNAVAIL      0     0     0  was /dev/gptid/e3cb7441-7f4f-11e5-b243-e03f49abb2ba
        gptid/e9f806f3-c76f-11e3-9218-e03f49abb2ba  ONLINE       0     0     0
        gptid/ea7c6e25-c76f-11e3-9218-e03f49abb2ba  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Thu Oct 29 03:45:28 2015
config:

    NAME        STATE     READ WRITE CKSUM
    freenas-boot  ONLINE       0     0     0
      ada0p2    ONLINE       0     0     0

errors: No known data errors

Code:

# smartctl -x /dev/ada2
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p29 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    Z1F49BDW
LU WWN Device Id: 5 000c50 065710cd3
Firmware Version: CC29
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 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:    Tue Nov  3 07:21:42 2015 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Unavailable

=== 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:         (  575) 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:      ( 334) 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--   114   099   006    -    60364008
  3 Spin_Up_Time            PO----   095   095   000    -    0
  4 Start_Stop_Count        -O--CK   100   100   020    -    31
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  7 Seek_Error_Rate         POSR--   078   060   030    -    60937646
  9 Power_On_Hours          -O--CK   085   085   000    -    13372
10 Spin_Retry_Count        PO--C-   100   100   097    -    0
12 Power_Cycle_Count       -O--CK   100   100   020    -    31
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   099   000    -    0 0 1
189 High_Fly_Writes         -O-RCK   099   099   000    -    1
190 Airflow_Temperature_Cel -O---K   062   051   045    -    38 (Min/Max 29/44)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    0
192 Power-Off_Retract_Count -O--CK   100   100   000    -    25
193 Load_Cycle_Count        -O--CK   100   100   000    -    57
194 Temperature_Celsius     -O---K   038   049   000    -    38 (0 18 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    -    13372h+28m+23.086s
241 Total_LBAs_Written      ------   100   253   000    -    17839686132
242 Total_LBAs_Read         ------   100   253   000    -    60259271841
                            ||||||_ 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]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      5  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1       GPL,SL  VS      20  Device vendor specific log
0xa2       GPL     VS    4496  Device vendor specific log
0xa8       GPL,SL  VS     129  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xab       GPL     VS       1  Device vendor specific log
0xb0       GPL     VS    5176  Device vendor specific log
0xbe-0xbf  GPL     VS   65535  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL,SL  VS      10  Device vendor specific log
0xc4       GPL,SL  VS       5  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  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  Conveyance offline  Completed without error       00%     13368         -
# 2  Short offline       Completed without error       00%     13367         -
# 3  Conveyance offline  Completed without error       00%     13344         -
# 4  Short offline       Completed without error       00%     13343         -
# 5  Conveyance offline  Completed without error       00%     13320         -
# 6  Short offline       Completed without error       00%     13319         -
# 7  Conveyance offline  Completed without error       00%     13295         -
# 8  Short offline       Completed without error       00%     13294         -
# 9  Conveyance offline  Completed without error       00%     13274         -
#10  Short offline       Completed without error       00%     13273         -
#11  Conveyance offline  Completed without error       00%     13251         -
#12  Short offline       Completed without error       00%     13250         -
#13  Conveyance offline  Completed without error       00%     13227         -
#14  Short offline       Completed without error       00%     13226         -
#15  Conveyance offline  Completed without error       00%     13203         -
#16  Short offline       Completed without error       00%     13202         -
#17  Conveyance offline  Completed without error       00%     13179         -
#18  Short offline       Completed without error       00%     13178         -
#19  Conveyance offline  Completed without error       00%     13154         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    38 Celsius
Power Cycle Min/Max Temperature:     29/44 Celsius
Lifetime    Min/Max Temperature:     18/49 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Data Table command not supported

SCT Error Recovery Control command not supported

Device Statistics (GP Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2            7  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

 

[Bidule0hm]

This drive run too hot (and the others too, probably), you should take care of that first ;)

 

[danb35]

The SMART data you provided is not from a new drive--this one's been powered on over 13,000 hours. It's running warm, but within tolerance at the moment--though it's been warmer than it should be (44 C this power cycle, 49 in its lifetime).

 

[Micheal Shallop]

Thanks for the quick replies...

I have this as my current pool state:

And this is the current disk view:

My /dev listing for the devices:

Code:

rw-r-----  1 root  operator  0x58 Nov  3 07:19 /dev/ada0
crw-r-----  1 root  operator  0x5a Nov  3 07:19 /dev/ada0p1
crw-r-----  1 root  operator  0x5c Nov  3 07:19 /dev/ada0p2
crw-r-----  1 root  operator  0x5e Nov  3 07:19 /dev/ada1
crw-r-----  1 root  operator  0x66 Nov  3 07:19 /dev/ada1p1
crw-r-----  1 root  operator  0x88 Nov  3 07:20 /dev/ada1p1.eli
crw-r-----  1 root  operator  0x68 Nov  3 07:19 /dev/ada1p2
crw-r-----  1 root  operator  0x60 Nov  3 07:19 /dev/ada2
crw-r-----  1 root  operator  0x6a Nov  3 07:19 /dev/ada2p1
crw-r-----  1 root  operator  0x72 Nov  3 07:20 /dev/ada2p1.eli
crw-r-----  1 root  operator  0x6c Nov  3 07:19 /dev/ada2p2
crw-r-----  1 root  operator  0x62 Nov  3 07:19 /dev/ada3
crw-r-----  1 root  operator  0x6e Nov  3 07:19 /dev/ada3p1
crw-r-----  1 root  operator  0x74 Nov  3 07:20 /dev/ada3p1.eli
crw-r-----  1 root  operator  0x70 Nov  3 07:19 /dev/ada3p2

When the previous drive failed, it was /dev/ada2 -- looking at the available serial numbers I was able to deduce that the failed drive (Z501GKFS) was the new drive as I both recorded it's SN prior to replacement and noted its absence from the pool state list.

smartctl is showing these drives as currently available:

Code:

# smartctl --scan
/dev/ada0 -d atacam # /dev/ada0, ATA device
/dev/ada1 -d atacam # /dev/ada1, ATA device
/dev/ada2 -d atacam # /dev/ada2, ATA device
/dev/ada3 -d atacam # /dev/ada3, ATA device
/dev/cd0 -d atacam # /dev/cd0, ATA device

Where /dev/ada0 is my SSD boot...

So, again, newb here -- is there a way I can get a smartcrl scan on the defunct drive?

Any other helpful hints for diagnosing why a new drive immediately failed? I can re-position drives to help with heat dissipation but what I'm looking for are conclusive diagnostics that identify the point of failure. Or at least something more substantial that what I am currently seeing.

Thanks!

 

[Bidule0hm]

Any other helpful hints for diagnosing why a new drive immediately failed?

Temperature and/or infant mortality. Did you burn-in this drive?

 

[Micheal Shallop]

if, by burn-in, you mean re-silvered, then yes.

 

[danb35]

No, burn in--extended testing at fairly high load to detect infant mortality. Here are a couple of resources:
https://forums.freenas.org/index.php?threads/building-burn-in-and-testing-your-freenas-system.17750/
https://forums.freenas.org/index.php?threads/how-to-hard-drive-burn-in-testing.21451/

 

[Micheal Shallop]

ok - so, if I wanted to do this, what purpose would it serve now?
Would the burn-in testing eventually allow me to recover and re-use the new drive?
Is there a way to recover the drive or is it forever marked as bad by freenas?
(somewhat related to the above) Is there a way to spoof the replacement? (re-silvering took like a dozen hours which, to me, seems comparable to a burn-in as it completed successfully...)

The easy fix is to just return and re-order a replacement - I'm not rushing to this as a solution b/c I'm wondering if the drive failure was symptomatic of a larger (hardware) problem.

Thanks for your patience!

--mike

 

[danb35]

It would serve no purpose now. Now, your disk has (apparently) failed catastrophically, to the point where your system doesn't even see that it exists. I disagree with @Bidule0hm that temperature would have been a factor--your disks are too hot (and you should do something about that sooner rather than later), but not hot enough that I'd expect them to fail within days.

It's possible, I suppose, that you have a bad SATA port on your motherboard, a bad SATA cable, and/or bad power to that drive. You can certainly try changing those around (plug it into a different port, use a different cable, use a different power connection) and seeing if the drive becomes visible again.

 

[Bidule0hm]

I agree, but it can't have helped :)

 

[Robert Trevellyan]

ST3000DM001

Unfortunately this model is known for early failures. If you have more on the shelf, burn them in now before you need them.

 

[DrKK]

Unfortunately this model is known for early failures. If you have more on the shelf, burn them in now before you need them.

I'd like to second that. ST3000DM001 is one of the least reliable drives of the past decade. We have hundreds of users dropping pools left and right who are on this particular Seagate. I think it was also very reasonably priced, which means a lot of people bought it.

 

[tvsjr]

I'd like to second that. ST3000DM001 is one of the least reliable drives of the past decade. We have hundreds of users dropping pools left and right who are on this particular Seagate. I think it was also very reasonably priced, which means a lot of people bought it.

Sadly, it's not even just the 3TB version. I bought 5 of the ST2000DM001 2TB models a while back for a Synology DS1512+. All dead within a year, including one that died during the recovery of another drive... causing complete loss of the array. I didn't even worry about warranty claims... after swapping to HGST drives and recovering the array, the 5 Seagates became very expensive targets for the range. Numerous 5.56mm and 7.62mm holes ensued.

I also noticed that the Seagate drives always underreported their temperature by about 5 degrees compared to the HGST drives. Not really sure why, as the drives were very comparable specs.

 

[DrKK]

I bought 5 of the ST2000DM001 2TB

That one is an even worse piece of shit than the 3TB.