Crtical Alert - Help Please - V2

[Redcoat]

An all-new experience for me today on my 13-month old FreeNAS Mini - a critical alert message "Device: /dev/ada4, Self Test Log error count increased from 0 to 1".

Can somebody advise me on the content of the results below, please? I am presently assuming I should RMA this drive after swapping it out with my spare. But do the test results suggest otherwise?

Thanks in advance.

Code:

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

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4EE8CZYX2
LU WWN Device Id: 5 0014ee 2b5313b32
Firmware Version: 80.00A80
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Mar  9 19:46:18 2016 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

=== 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:      ( 119) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (53280) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 532) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   177   175   021    -    8133
  4 Start_Stop_Count        -O--CK   100   100   000    -    21
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   088   088   000    -    9096
10 Spin_Retry_Count        -O--CK   100   253   000    -    0
11 Calibration_Retry_Count -O--CK   100   253   000    -    0
12 Power_Cycle_Count       -O--CK   100   100   000    -    21
192 Power-Off_Retract_Count -O--CK   200   200   000    -    7
193 Load_Cycle_Count        -O--CK   200   200   000    -    74
194 Temperature_Celsius     -O---K   119   109   000    -    33
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    1
                            ||||||_ 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      6  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
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  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 (6 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    Completed: read failure       70%      9059         204                  7411176
# 2  Short offline       Completed without error       00%      8984         -
# 3  Short offline       Completed without error       00%      8792         -
# 4  Extended offline    Completed without error       00%      8707         -
# 5  Short offline       Completed without error       00%      8624         -
# 6  Short offline       Completed without error       00%      8456         -
# 7  Extended offline    Completed without error       00%      8371         -
# 8  Short offline       Completed without error       00%      8289         -
# 9  Short offline       Completed without error       00%      8049         -
#10  Extended offline    Completed without error       00%      7963         -
#11  Short offline       Completed without error       00%      7881         -
#12  Short offline       Completed without error       00%      7713         -
#13  Extended offline    Completed without error       00%      7628         -
#14  Short offline       Completed without error       00%      7545         -
#15  Short offline       Completed without error       00%      7305         -
#16  Extended offline    Completed without error       00%      7220         -
#17  Short offline       Completed without error       00%      7138         -
#18  Short offline       Completed without error       00%      6970         -

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):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    33 Celsius
Power Cycle Min/Max Temperature:     22/37 Celsius
Lifetime    Min/Max Temperature:     20/43 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (429)

Index    Estimated Time   Temperature Celsius
430    2016-03-09 11:49    32  *************
...    ..(272 skipped).    ..  *************
225    2016-03-09 16:22    32  *************
226    2016-03-09 16:23    33  **************
...    ..(124 skipped).    ..  **************
351    2016-03-09 18:28    33  **************
352    2016-03-09 18:29    32  *************
...    ..( 76 skipped).    ..  *************
429    2016-03-09 19:46    32  *************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-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
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2           68  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2           69  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4     26349580  Vendor specific

 

[BigDave]

200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 1
||||___ R error rate

Not too sure I would panic just yet, as shown, the failure point is 200 errors!
I've had drives with a handfull of errors last over a year before becoming
a problem, BUT, I would first like to verify your pool's redundancy level.
Please post the results of # zpool status

While we wait for that, I will say that the drive in question could go on working for quite
some time. You should keep an eye on the rate at which it increases (assuming it does).
I would not RMA a drive with one error, and trade it for a refurbished drive that has
gone through only God knows what!

 

[Robert Trevellyan]

Extended offline Completed: read failure 70% 9059 204 7411176

Return it.

 

[Redcoat]

BigDave, thanks, you asked "Please post the results of # zpool status".

Here it is:

Code:

[root@freenasmini] ~# zpool status
  pool: Volume1
state: ONLINE
  scan: scrub repaired 0 in 4h40m with 0 errors on Tue Mar  1 08:40:36 2016
config:

        NAME                                            STATE     READ WRITE CKS                               UM
        Volume1                                         ONLINE       0     0                                    0
          raidz2-0                                      ONLINE       0     0                                    0
            gptid/9be4e735-bd6a-11e4-8c34-d0509946c5e6  ONLINE       0     0                                    0
            gptid/9c5d498b-bd6a-11e4-8c34-d0509946c5e6  ONLINE       0     0                                    0
            gptid/9cd608c6-bd6a-11e4-8c34-d0509946c5e6  ONLINE       0     0                                    0
            gptid/9d534430-bd6a-11e4-8c34-d0509946c5e6  ONLINE       0     0                                    0

errors: No known data errors

  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h1m with 0 errors on Tue Mar  8 03:46:31 2016
config:

        NAME                                          STATE     READ WRITE CKSUM
        freenas-boot                                  ONLINE       0     0     0
          gptid/1ed7c42c-8ec4-11e4-869d-d0509946c5e6  ONLINE       0     0     0

errors: No known data errors

 

[Redcoat]

Return it.

Robert, can you decode that report section "read failure 70% 9059 204 7411176" for me, please? I have not yet found material that explains what it means.

Thanks!

 

[jgreco]

The 70% is how far into that selftest it got.

The 9059 is how many hours the drive has been powered on (think: odometer).

The remaining two numbers are probably due to line wrap, and should be a single number, 2047411176. This is the LBA at which the error was encountered. Your disk is broken up into logical 512 byte blocks, and that's the block number.

 

[Redcoat]

jgreco, got it! Thanks. I had guessed the LBA answer but the other two were until now a mystery.

BiduleOhm has added a bit of confusion for me by liking both of what are not clearly similar views (both support return, one after waiting, the other seemingly immediate).

 

[Bidule0hm]

That's because they are both useful but both incomplete.

TL;DR return it ;)

 

[jgreco]

If it were a new drive, I'd say return it for refund, then buy another new drive (assuring yourself of a new drive).

For an older drive, I'm usually not interested in doing an RMA for a single error. I'll fix the error and then watch for more in the future. The problem with RMA'ing a drive with a teensy problem is that in almost all cases you get a non-new drive back. That non-new drive will have an unknown history. Did someone abuse it? Was it baked to death in an external enclosure? How bad did it have to get for someone else to decide to RMA the disk? Answer: probably much worse than a single bad sector.

It's a problem of exchanging a known quantity of badness (a bad sector) for a total unknown.

 

[Redcoat]

Now that makes perfect sense and clarifies Big Dave's position on returns. These are my first server-class drives and the first on which I've run routine tests - I've just about zero history on electronics returns and so was not focused on the likely "used" status of the pool of drives for return.

I've "fixed" drives in CP/M (DRI's tools), MS-DOS and MS-DOS/Windows (Spinwrite) many times. I'll search for an info source on the tools and process(es) applicable to my situation with this drive from a FreeNAS system.

Thank you again.

 

[rs225]

At your own risk, this is what I do:
zpool offline tank ada4
dd if=/dev/zero of=/dev/ada4 bs=4k count=1 seek=255926397
dd if=/dev/ada4 of=/dev/null bs=4k count=1 skip=255926397
zpool online tank ada4

This assumes you have redundancy in the pool. Then, see where or whether the next long test fails. If you end up with an uncomfortable number of fails, replace the drive. If no more, just keep note of it and carry on.

This is a 4k sector drive, so we divide the LBA by 8(It should be evenly divisible). The write either reallocates the sector, or overwrites the previous data that can no longer be read. The second dd should read without an error.

Your next scrub may register a CRC error and repair for reach block you overwrite.