Faulted disk but no smart errors

[pechkin000]

I have a question in regards to the situation I am experiencing. I got an email notification: " Critical Alert - the volume backups (ZFS) state is DEGRADED: One or more devices are faulted in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state."

So as expected my zpool status output looks like this:

Code:

[root@replicator] ~# zpool status
  pool: backups
state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
  scan: scrub repaired 0 in 2h49m with 0 errors on Sun Nov 30 02:49:34 2014
config:

        NAME                                            STATE     READ WRITE CKSUM
        backups                                         DEGRADED     0     0     0
          raidz3-0                                      DEGRADED     0     0     0
            gptid/7e0742c8-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0
            gptid/7e8abe61-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0
            gptid/7effff0d-5557-11e4-a84e-ac220b8c944c  FAULTED      7 14.6K     2  too many errors
            gptid/7f8d5bca-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0
            gptid/8016f0cf-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0
            gptid/8083abb3-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0
            gptid/80f31598-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0
            gptid/8163ab25-5557-11e4-a84e-ac220b8c944c  ONLINE       0     0     0

errors: No known data errors

I wanted to see what the errors were and when they happened so I ran the short and the conveyance tests
but when i checked it showed no errors at all:

Code:

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

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (AF, SATA 6Gb/s)
Device Model:     WDC WD40EZRX-00SPEB0
Serial Number:    WD-WCC4EFFJNHVE
LU WWN Device Id: 5 0014ee 20aa1b763
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:    Tue Dec  9 00:32:22 2014 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:                (54600) 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:        ( 546) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x7035) SCT Status 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       -       0
  3 Spin_Up_Time            0x0027   175   175   021    Pre-fail  Always       -       8216
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       6
  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       -       2603
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       -       6
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       5
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   120   116   000    Old_age   Always       -       32
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   200   200   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  Conveyance offline  Completed without error       00%      2603         -
# 2  Short offline       Completed without error       00%      2603         -
# 3  Short offline       Completed without error       00%      1262         -
# 4  Short offline       Completed without error       00%      1238         -
# 5  Short offline       Completed without error       00%      1166         -
# 6  Short offline       Completed without error       00%      1142         -
# 7  Short offline       Completed without error       00%      1118         -
# 8  Short offline       Completed without error       00%      1095         -
# 9  Short offline       Completed without error       00%      1071         -
#10  Short offline       Completed without error       00%       998         -
#11  Short offline       Completed without error       00%       975         -
#12  Short offline       Completed without error       00%       950         -
#13  Short offline       Completed without error       00%       927         -
#14  Short offline       Completed without error       00%       903         -
#15  Short offline       Completed without error       00%       831         -
#16  Short offline       Completed without error       00%       807         -
#17  Short offline       Completed without error       00%       783         -
#18  Short offline       Completed without error       00%       759         -
#19  Short offline       Completed without error       00%       735         -
#20  Short offline       Completed without error       00%       663         -
#21  Short offline       Completed without error       00%       639         -

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.

At that point the rebooted the server and when it came back up, zpool status showed no errors, the disk was back online and part of the pool. All of this happened right after the upgrade to 9.3. This EXACT thing happened two days ago with that same drive pack on 9.2. I have no problem replacing the drive, actually got the replacement ready to be swapped out tomorrow when I get back to the office, but I am just trying to understand what this means and if it is indeed the drive and not something else. As in why I am not getting any errors at all out of smartctl tests. I run regular scrubs and long tests alternating weekly and not a peep from any of them until this alert two days ago, then back to the pool and then faulted again after upgrade.
Could anyone shed some light on this? Is there another test I can run to verify there is actually something wrong with the drive and not a sata cord or anything of that nature? I have a pretty standard LSI MegaRAID SAS 9240-8Gi controller flashed to IT mode so I doubt its the card...

On a separate note I took a chance and set up this server with greens instead of reds as it is supposed to be a target for the replications tasks from the main freenas server, to save a bit when i was buying all 8 drives at once, but i figured if they die I will replace them with reds one at a time, any word of caution against mixing reds and greens in the same pool?

Thanks a lot for any help!
EDIT:
I remebered to do smartctl -x so the bottom part of the output showed this:

Code:

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2          837  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2          837  R_ERR response for host-to-device data FIS
0x0005  2            8  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            8  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2          369  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2          370  Device-to-host register FISes sent due to a COMRESET
0x000b  2          199  CRC errors within host-to-device FIS
0x000f  2          194  R_ERR response for host-to-device data FIS, CRC
0x0012  2            5  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4      4812775  Vendor specific

I dont really know what those error codes are I had no errors like that on other drives so obvious something is wrong but can someone interpret what this means and if it is indeed the drive not something else?

 

[Z300M]

Bad data or power cable? I had similar errors on a couple of drives until I replaced the data cables -- and disconnected and reconnected all the power cables.

 

[joeschmuck]

I too agree that the first thing I would do is replace the SATA cable for that drive or something better since you do have a RAIDZ3 setup, try is to swap the SATA cable with another drive just on the drive side (if possible or drive location) within your pool and then see if the problem, assuming it shows up again, stays with ada2 or moves with the drive. For something which may be that intermittent, it would be a good troubleshooting tool. Just write down what you did in case it shows up a month from now, I know my memory isn't that great at times.

 

[pechkin000]

Great advice, thanks guys!

 

[cyberjock]

I doubt it's the SATA cable, but as it's cheap and easy there's no reason not to do it "just in case".

It's possible the drive is power cycled because of a poor connection or poor power, but there's no way to really know for sure. ZFS can rack up errors and give the "too many errors" message if a hard drive is power cycled while the system is in use. Some hardware will also show the disk as "REMOVED" or "UNAVAIL" too. So there's no smoking gun with the info you provided.

So how did you get to da2 as being the same as the disk as the gpt-id that is the problem? Is it possible you are looking at the wrong disk? I'm asking because we've had many people not get this right and they go looking at the wrong disk (and have even replaced good disks with good disks) because of this.

 

[danb35]

Is there a particular reason you're not running long SMART tests on the drive?

 

[bestboy]

Maybe this is due to the MegaRAID controller propagating a disk read error to the zpool which responds with removing the disk? Your WD Greens do not have TLER and are not supposed to be used with a RAID controller.

 

[pechkin000]

@cyberjock I used glabel status to identify the disk.
So here is the latest development that leads me to believe that it is the cable. I swapped the connections between da1 and da2 and now da1 is giving me the same errors:

Code:

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2          837  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2          837  R_ERR response for host-to-device data FIS
0x0005  2            8  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            8  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2          369  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2          370  Device-to-host register FISes sent due to a COMRESET
0x000b  2          199  CRC errors within host-to-device FIS
0x000f  2          194  R_ERR response for host-to-device data FIS, CRC
0x0012  2            5  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4      4812775  Vendor specific

@danb35 I actually just realized that I forgot to set the long smart test opposite to scrub week on this server, i did it on the main onem and forgot this one. So i just corrected that. I ordered new sas to sata cables gonna get them tomorrow and see what happens after i replace it.

@bestboy I thought this would not be an issue if its flashed to IT mode...

 

[bestboy]

I thought this would not be an issue if its flashed to IT mode...

Well, yes, but if ZFS as your software raid controller were handling the read errors bubbling up from the hardware, then I'd expect to see some errors in syslog (example).

 

[pechkin000]

@bestboy : But don't you think that now that I have switched cables and the same error is on a different drive that has the same cable the original drive with errors was connected to it indicates that its my SAS to Sata adapter that's generating it? I am expecting the new adapter to arrive today - I guess that will answer the question definitively.

 

[onekanoobie]

i don't mean to jack this thread, but I am experiencing a similar issue. I am not sure where to look to see what may be actually happening. I have 2 Raidz2 vdevs striped together for one pool. I would say every 24 to 48 hours one of my disks gets reported as "offline" and i get an email saying that the disk has been "removed". When I go to the interface the volume status will show "degraded" but when I check the disks they are all there. I can even poll the smart data on the disk that shows offline and it comes back with no errors. If I reboot, everything comes up fine.

I just found the information about the zpool status and clearing the results if the disk appears to be healthy which it does.

I am not quite sure what I should be looking for as a possible cause. I have a suspicion that it is either my power supply or my SATA cables. It does not happen on the same drive every time. last night it was ada7, the night before was ada9, I have also had it happen on ada6. The current cables I am using are just your generic cables that come with your MB and they barely reach from the ports to some of the drives. I was considering buying new cables with the locking catch on them in a longer length and replacing my power supply. I have a 450 watt power supply that seems to work fine but is several years old.

Does anyone think I am barking up the wrong tree? Is there another place I should be checking which would help track it down?