SMART error, what do I need to do

[zella]

Hi guys,

I got this critical alert email 8 days ago (it got lost in my inbox, shame on me for not dealing with it sooner):

"Device: /dev/ada3, Self-Test Log error count increased from 0 to 1"

smartctl -a /dev/ada3

gives the following:

Code:

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 WD30EFRX-68EUZN0
Serial Number:    WD-WMC4N0D3J014
LU WWN Device Id: 5 0014ee 6af6e7f66
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.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: 3.0 Gb/s)
Local Time is:    Sat Apr 30 05:14:41 2016 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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                (40680) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 408) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       1
  3 Spin_Up_Time            0x0027   178   178   021    Pre-fail  Always       -       6058
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       9
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2773
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       9
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       3
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       103
194 Temperature_Celsius     0x0022   117   112   000    Old_age   Always       -       33
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       1

SMART Error Log Version: 1
No Errors Logged

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%      2675         -
# 2  Extended offline    Completed: read failure       90%      2579         95164392
# 3  Short offline       Completed without error       00%      2507         -
# 4  Short offline       Completed without error       00%      2340         -
# 5  Extended offline    Completed without error       00%      2251         -
# 6  Short offline       Completed without error       00%      2172         -
# 7  Short offline       Completed without error       00%      1932         -
# 8  Extended offline    Completed without error       00%      1844         -
# 9  Short offline       Completed without error       00%      1764         -
#10  Short offline       Completed without error       00%      1597         -
#11  Extended offline    Completed without error       00%      1509         -
#12  Short offline       Completed without error       00%      1430         -
#13  Short offline       Completed without error       00%      1238         -
#14  Extended offline    Completed without error       00%      1149         -
#15  Short offline       Completed without error       00%      1070         -
#16  Short offline       Completed without error       00%       902         -
#17  Extended offline    Completed without error       00%       814         -
#18  Short offline       Completed without error       00%       734         -
#19  Short offline       Completed without error       00%       494         -
#20  Extended offline    Interrupted (host reset)      80%       400         -
#21  Short offline       Completed without error       00%       326         -

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.

zpool status gives:

Code:

  pool: Drive
state: ONLINE
  scan: scrub repaired 0 in 14h36m with 0 errors on Fri Apr  1 18:36:24 2016
config:

        NAME                                                STATE     READ WRITE CKSUM
        Drive                                             ONLINE       0     0     0
          mirror-0                                          ONLINE       0     0     0
            gptid/f5250822-7611-11e3-9f06-002590d492b9.eli  ONLINE       0     0     0
            gptid/f571671d-7611-11e3-9f06-002590d492b9.eli  ONLINE       0     0     0
          mirror-1                                          ONLINE       0     0     0
            gptid/f3b1d464-b453-11e5-b4b0-002590d492b9.eli  ONLINE       0     0     0
            gptid/f4dbe7c3-b453-11e5-b4b0-002590d492b9.eli  ONLINE       0     0     0

I'm sure what I need to do is painfully obvious to the well informed but I didn't even know what a SMART test was until I read Cyberjock's guide and I certainly wouldn't have had test scheduled if it wasn't for it.

From reading other threads I know IDs 5, 197 and 198 are thing to look out for, they all look good, but my understanding is the read failure is not good.

I have backed up all my data and if someone could help me decrypt this log and tell me the next best course of action it would be most appreciated.

Thanks in advance,

Z

 

[danb35]

The drive failed the last long SMART test and should be replaced. It only has about four months in service, so it should be well within warranty. As long as you have a place to temporarily put the replacement drive, you can do the replacement without having to take the old drive offline, so you never have to lose redundancy.

 

[joeschmuck]

I would run the SMART long test again and see if it passes. If it fails again then RMA the drive. You can do what is called an Advanced Replacement where WD ships you a replacement drive and then you ship them back the failed drive in the same box, and the last time I did this, WD paid for the return shipping costs.

ID 200 Multizone Error can also be a failure indicator although I have never seen it written from a manufacturer that it is an indication of a hardware failure. Did you use the hard drive troubleshooting guide? It tells you how to go about testing your drives manually and diagnosing the failure. It also mentions ID 200 in Appendix B.

 

[DrKK]

I would run the SMART long test again and see if it passes. If it fails again then RMA the drive. You can do what is called an Advanced Replacement where WD ships you a replacement drive and then you ship them back the failed drive in the same box, and the last time I did this, WD paid for the return shipping costs.

This is also what I would recommend. Run a LONG test again. If it fails again, do not pass go, do not collect $200, and do a WD advance RMA.

If the drive passes, then it would be reasonable to maintain a rigorous scrubbing/testing schedule for another month or two, and see where you're at.

 

[joeschmuck]

And it does look like you are running an automated Long test roughly every 15 days so that isn't too bad but I would change that to once a week and change the Short test to daily. Scrubs are typically run once a month by default, I typically feel that is sufficient but you can opt to do it more frequently.

Good Luck.

 

[danb35]

Scrubs by default are every 6 weeks. That's probably adequate, but more often would be better.

 

[DrKK]

Scrubs by default are every 6 weeks. That's probably adequate, but more often would be better.

Ugh. I guess opinions vary, but I would recommend that consumer-grade gear in consumer-grade installations have a ZFS scrub 2 times per month, or 30 times per month if Seagate. There is no way I'd sign off on 1 per 6 weeks myself.

 

[rs225]

What I do(Except you probably can't use /dev/ada3.eli, so you'll have to figure out what ZFS calls your ada3 encrypted device):

zpool offline Drive /dev/ada3.eli
dd if=/dev/zero of=/dev/ada3 count=8 seek=95164392
zpool online Drive /dev/ada3.eli

Then see if the next long test fails at the same spot, a different spot, or succeeds.

Unless the problem worsens, this doesn't seem to be a big deal.

 

[joeschmuck]

or 30 times per month if Seagate.

Funny Man

What I do(Except you probably can't use /dev/ada3.eli, so you'll have to figure out what ZFS calls your ada3 encrypted device):

zpool offline Drive /dev/ada3.eli
dd if=/dev/zero of=/dev/ada3 count=8 seek=95164390
zpool online Drive /dev/ada3.eli

I would not recommend doing this without understanding exactly what this does, and right now I don't, and I'll admit it.

Out of curiosity, why would someone want to write a zero value to a drive that contains data, or do I have this wrong? I would think you could do something like this instead...

dd if=/dev/ada3 of=/dev/null count=500 skip=95164300

This should just read the locations from 95164300 through 9516900, which means if the problem is spreading then it will find it.

But for @zella I would just stick with doing another SMART Long test, keep things simple.

 

[danb35]

I would not recommend doing this without understanding exactly what this does, and right now I don't, and I'll admit it.

I believe the idea is that by forcing the drive to write to the bad sector, you'll force it to remap the sector to one that isn't bad. I don't buy it, and figure a bad drive is a bad drive (especially if it's under warranty), but that's the idea. It does, of course, mean temporarily losing your redundancy while you have the drive offline, and the next scrub will have to fix the error you've intentionally created (assuming there was data on that block).

 

[joeschmuck]

I believe the idea is that by forcing the drive to write to the bad sector, you'll force it to remap the sector to one that isn't bad. I don't buy it, and figure a bad drive is a bad drive (especially if it's under warranty), but that's the idea. It does, of course, mean temporarily losing your redundancy while you have the drive offline, and the next scrub will have to fix the error you've intentionally created (assuming there was data on that block).

Thanks for confirming what I was thinking. I for one would not try to induce a failure at all, especially since this is a new drive. If it fails the SMART test, RMA it. If the drive is old and it fails the SMART test, replace it with a new one. But I do understand the thought of trying to force a remapping of the drive but I'm not sure what application I'd use a drive in other than a test bed system once I knew it was now a marginal drive.

 

[zella]

Hi guys,

Thank you all very much for your replies.

@joeschmuck can you please point me in the direction of the troubleshooting guide you mentioned; a search in the main user guide for ID 200 came up with nothing so I assume you are talking about something different.
Also, from the log info how were you able to tell my test schedule? It's about 15 days, I would love to tell you the exact details but I am dealing with another issue at the moment, my web GUI is not showing me anything:

any ideas?

Anyway, back to the initial problem.

I ran the long test again.

Code:

smartctl -t long -C /dev/ada3

It said it would take 6 hrs or so. It has been longer than that now, but the results seem to be the same as before, I hope I've done it right and these are actually a new set of results.

If it is correct then I take it that the drive is a walking dead man. In my current setup each disc has a single mirror. When it comes to replacing the dead drive is it just a simple case of swapping it out (cold obviously).

Would you recommend shutting it down until the new drive gets here? I can definitely survive with it being off for a few days.

Code:

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WMC4N0D3J014
LU WWN Device Id: 5 0014ee 6af6e7f66
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.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: 3.0 Gb/s)
Local Time is:    Sun May  1 12:12:50 2016 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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                (40680) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 408) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       1
  3 Spin_Up_Time            0x0027   178   178   021    Pre-fail  Always       -       6058
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       9
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2804
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       9
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       3
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       103
194 Temperature_Celsius     0x0022   113   111   000    Old_age   Always       -       37
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      2804         -
# 2  Short offline       Completed without error       00%      2675         -
# 3  Extended offline    Completed: read failure       90%      2579         95164392
# 4  Short offline       Completed without error       00%      2507         -
# 5  Short offline       Completed without error       00%      2340         -
# 6  Extended offline    Completed without error       00%      2251         -
# 7  Short offline       Completed without error       00%      2172         -
# 8  Short offline       Completed without error       00%      1932         -
# 9  Extended offline    Completed without error       00%      1844         -
#10  Short offline       Completed without error       00%      1764         -
#11  Short offline       Completed without error       00%      1597         -
#12  Extended offline    Completed without error       00%      1509         -
#13  Short offline       Completed without error       00%      1430         -
#14  Short offline       Completed without error       00%      1238         -
#15  Extended offline    Completed without error       00%      1149         -
#16  Short offline       Completed without error       00%      1070         -
#17  Short offline       Completed without error       00%       902         -
#18  Extended offline    Completed without error       00%       814         -
#19  Short offline       Completed without error       00%       734         -
#20  Short offline       Completed without error       00%       494         -
#21  Extended offline    Interrupted (host reset)      80%       400         -
1 of 1 failed self-tests are outdated by newer successful extended offline self-test # 1

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]

The most important part of those SMART results is on line 80, where it says that the most recent long self-test passed. It further calls out that fact on line 101. The drive has a history of a single read error (which resulted, presumably, in the previous failed SMART self-test), but it has no reallocated sectors, no offline sectors, and no pending sectors. The multi zone error rate has dropped from 1 in your previous results, to 0 in these. In short, the current SMART results look like the drive is fine. Based on that, I'll revise my previous statement that it needs to be replaced now, but I do think you need to keep a close watch on it.

I don't know why your system isn't showing the SMART tests you've scheduled. I'd suggest you add two new ones: a short test daily, and a long test weekly on a day of your choosing. I'd also suggest shortening the threshold for your scrubs to something like 12 days--with the default schedule, IIRC, that will result in scrubs every two weeks.

 

[zella]

Thank you for your reply, I will do as you say RE the schedule.

OK, I now understand the log a bit more. I didn't realise the bit at the bottom was the list of previous tests, I thought it was all data from the last test that was run, so when I saw the read fail again I assumed it was a repeat of the last one, and I now understand how Joe knew the schedule, LifeTime(hours) duh!

The lack of info on the GUI is not limited to smart tests, I can't see any settings anywhere. Gonna reboot and see what happens.

Thanks again guys

UPDATE: it's an issue with Chrome, everything is there in Firefox.

And as far as IE goes, well... I don't know why I even bothered:

 

[joeschmuck]

As for the troubleshooting guide, it's in the forums main page, also linked on my signature.

I agree, your drive looks fine right now and I'd run that SMART long test once a week.

Lastly, I use FireFox most of the time, but especially with FreeNAS.