Write errors on two different drives BUT both were da5 at the time

[Z300M]

I have had two identical drives (Seagate ST32000641AS) with write errors as reported by

Code:

zpool status

and it strikes me as odd that each was at the time identified as da5.

They were not in the same bay of the drive cage at the times the errors occurred, so not connected to the same SATA port.

Is it merely coincidence that the errors were on drives shown as da5? Any other explanation?

 

[warri]

The assignments are not fixed and may change. That's why FreeNAS uses the GUID of the partitions to create ZFS volumes and keep track of everything.

Can you post the complete output of zpool status?

 

[Z300M]

The assignments are not fixed and may change. That's why FreeNAS uses the GUID of the partitions to create ZFS volumes and keep track of everything.

Can you post the complete output of zpool status?

Sorry if the following looks a mess: everything is showing up on one line in Preview, and I can't seem to fix it.
OK. I recaptured the info using SSH:

Code:

[root@freenas] ~# zpool status
  pool: Pool1
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://illumos.org/msg/ZFS-8000-9P
  scan: resilvered 60K in 0h0m with 0 errors on Sun Apr 13 02:29:46 2014
config:

        NAME                                            STATE     READ WRITE CKSUM
        Pool1                                           ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/7bc9fb7b-14c5-11e3-b6d4-001b21c4dc34  ONLINE       0     0     0
            gptid/7c972217-14c5-11e3-b6d4-001b21c4dc34  ONLINE       0     0     0
            gptid/34a0d18f-b2f0-11e3-bc9a-002590f06338  ONLINE       0     0     0
            gptid/7e979187-14c5-11e3-b6d4-001b21c4dc34  ONLINE       0   119     0
            gptid/7f8bd18b-14c5-11e3-b6d4-001b21c4dc34  ONLINE       0     0     0
            gptid/80a62fee-14c5-11e3-b6d4-001b21c4dc34  ONLINE       0     0     0

errors: No known data errors
[root@freenas] ~#

Then

Code:

[root@freenas] ~# glabel status
                                      Name  Status  Components
gptid/34a0d18f-b2f0-11e3-bc9a-002590f06338     N/A  da0p2
gptid/80a62fee-14c5-11e3-b6d4-001b21c4dc34     N/A  da1p2
gptid/6430c91f-8966-11e3-908b-001b21c4dc34     N/A  da2p2
gptid/7bc9fb7b-14c5-11e3-b6d4-001b21c4dc34     N/A  da3p2
gptid/7c972217-14c5-11e3-b6d4-001b21c4dc34     N/A  da4p2
gptid/7e979187-14c5-11e3-b6d4-001b21c4dc34     N/A  da5p2
gptid/7f8bd18b-14c5-11e3-b6d4-001b21c4dc34     N/A  da6p2
gptid/104faef2-c1a8-11e3-93f2-002590f06338     N/A  da7p2
gptid/63dd44ce-8966-11e3-908b-001b21c4dc34     N/A  da8p2
gptid/668b81be-8966-11e3-908b-001b21c4dc34     N/A  da9p2
                             ufs/FreeNASs3     N/A  ada0s3
                             ufs/FreeNASs4     N/A  ada0s4
                            ufs/FreeNASs1a     N/A  ada0s1a
                    ufsid/53123e1a9e0f089c     N/A  ada0s2a
                            ufs/FreeNASs2a     N/A  ada0s2a
[root@freenas] ~#

tells me that the drive with the write errors is at da5.

The drive that previously gave the write errors while at da5 has been replaced and is not even installed in the machine at present.

 

[warri]

Yes, that output is really bad. You should use SSH to extract that information, the WebGUI sometimes tends to destroy the formatting.

For me it looks like only one disk is affected, the one which you identified as ad5. Whats the output of

Code:

smartctl -a -q noserial /dev/da5

Here formatting is quite important, again ;)

 

[Z300M]

NOTE: I recaptured the earlier information using SSH and edited my previous post.

Now here is the new information you requested:

Code:

[root@freenas] ~# smartctl -a -q noserial /dev/da5
smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Barracuda XT
Device Model:    ST32000641AS
Firmware Version: CC13
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:  ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s
Local Time is:    Sun Apr 13 18:17:52 2014 EDT
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:                (  609) 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:        ( 344) minutes.
Conveyance self-test routine
recommended polling time:        (  2) minutes.
 
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  115  099  006    Pre-fail  Always      -      97744262
  3 Spin_Up_Time            0x0003  100  100  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      281
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  075  060  030    Pre-fail  Always      -      39075230
  9 Power_On_Hours          0x0032  076  076  000    Old_age  Always      -      21212
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      281
183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0
188 Command_Timeout        0x0032  100  099  000    Old_age  Always      -      1
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  068  058  045    Old_age  Always      -      32 (Min/Max 31/32)
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      -      211
193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      281
194 Temperature_Celsius    0x0022  032  042  000    Old_age  Always      -      32 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a  022  016  000    Old_age  Always      -      97744262
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      4
240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      6691559069129
241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      3885322297
242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      800572105
 
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%    21211        -
# 2  Short offline      Completed without error      00%    21210        -
# 3  Short offline      Completed without error      00%    21209        -
# 4  Short offline      Completed without error      00%    21208        -
# 5  Short offline      Completed without error      00%    21207        -
# 6  Short offline      Completed without error      00%    21206        -
# 7  Short offline      Completed without error      00%    21205        -
# 8  Short offline      Completed without error      00%    21204        -
# 9  Short offline      Completed without error      00%    21203        -
#10  Short offline      Completed without error      00%    21202        -
#11  Short offline      Completed without error      00%    21201        -
#12  Short offline      Completed without error      00%    21200        -
#13  Short offline      Completed without error      00%    21199        -
#14  Short offline      Completed without error      00%    21198        -
#15  Short offline      Completed without error      00%    21197        -
#16  Extended offline    Interrupted (host reset)      00%    21196        -
#17  Short offline      Completed without error      00%    21195        -
#18  Short offline      Completed without error      00%    21194        -
#19  Short offline      Completed without error      00%    21193        -
#20  Short offline      Completed without error      00%    21192        -
#21  Short offline      Completed without error      00%    21191        -
 
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.
 
[root@freenas] ~#

 

[warri]

Nothing out of the ordinary in there. I'd do a zpool clear and keep an eye open for more errors, and if they creep up again consider replacing the drive. Since you are running a Raid-Z2 anyway you are pretty safe at the moment.

I guess it was just a coincidence that both Seagates produced errors at the same time. Btw, what is the purpose of the extra four drives in there? Running another pool?

EDIT: Additionally you could do a long smart test on da5.

 

[cyberjock]

I will say that hourly short tests are absurdly frequent. Even daily is quite frequent. Your disk's log only keeps 21 entries, so you don't even have a day's worth of history....

 

[Z300M]

I will say that hourly short tests are absurdly frequent. Even daily is quite frequent. Your disk's log only keeps 21 entries, so you don't even have a day's worth of history....

A while back when I was having problems (e.g., green Alert button, but errors reported when I clicked on it) I reported that I was doing S.M.A.R.T. tests every 12 hours, and I understood you to be telling me that that was far too infrequent and that I should be doing them every 30 minutes -- but I couldn't find a way of setting the frequency at less than an hour. What did one or both of us misunderstand about what the other was saying?

And how come the default interval for S.M.A.R.T. on the Services tab is 30 minutes?

 

[Z300M]

Nothing out of the ordinary in there. I'd do a zpool clear and keep an eye open for more errors, and if they creep up again consider replacing the drive. Since you are running a Raid-Z2 anyway you are pretty safe at the moment.

I guess it was just a coincidence that both Seagates produced errors at the same time. Btw, what is the purpose of the extra four drives in there? Running another pool?

EDIT: Additionally you could do a long smart test on da5.

Yes, the other four drives are a second pool -- and it was while it was part of that second pool and was da5 that the other drive (no longer installed) was showing write errors.

I just started a long test on the current da5. It's going to take 344 minutes, but I may not be home when it finishes.

The other problem is: how come there are write errors on drives that pass all the S.M.A.R.T. tests and SeaTools diagnostics? -- as was the case with the previous one.

 

[ser_rhaegar]

A while back when I was having problems (e.g., green Alert button, but errors reported when I clicked on it) I reported that I was doing S.M.A.R.T. tests every 12 hours, and I understood you to be telling me that that was far too infrequent and that I should be doing them every 30 minutes -- but I couldn't find a way of setting the frequency at less than an hour. What did one or both of us misunderstand about what the other was saying?

And how come the default interval for S.M.A.R.T. on the Services tab is 30 minutes?

Check out:
http://forums.freenas.org/index.php?threads/scrub-and-smart-testing-schedules.20108/
http://doc.freenas.org/index.php/S.M.A.R.T._Tests
http://doc.freenas.org/index.php/S.M.A.R.T.

Note the service is not the same as the tests. The service should run every 30 minutes. The testing schedule is different and CJ has a nice guide on that portion in the first link.

 

[Z300M]

Check out:
http://forums.freenas.org/index.php?threads/scrub-and-smart-testing-schedules.20108/
http://doc.freenas.org/index.php/S.M.A.R.T._Tests
http://doc.freenas.org/index.php/S.M.A.R.T.

Note the service is not the same as the tests. The service should run every 30 minutes. The testing schedule is different and CJ has a nice guide on that portion in the first link.

OK. Thanks for that.

 

[Z300M]

Nothing out of the ordinary in there. I'd do a zpool clear and keep an eye open for more errors, and if they creep up again consider replacing the drive. Since you are running a Raid-Z2 anyway you are pretty safe at the moment.

I guess it was just a coincidence that both Seagates produced errors at the same time. Btw, what is the purpose of the extra four drives in there? Running another pool?

EDIT: Additionally you could do a long smart test on da5.

Code:

[root@freenas] ~# smartctl -a -q noserial /dev/da5
smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Barracuda XT
Device Model:    ST32000641AS
Firmware Version: CC13
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:  ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s
Local Time is:    Mon Apr 14 16:01:27 2014 EDT
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:                (  609) 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:        ( 344) minutes.
Conveyance self-test routine
recommended polling time:        (  2) minutes.
 
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  115  099  006    Pre-fail  Always      -      98442120
  3 Spin_Up_Time            0x0003  100  100  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      281
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  075  060  030    Pre-fail  Always      -      39140477
  9 Power_On_Hours          0x0032  076  076  000    Old_age  Always      -      21233
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      281
183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0
188 Command_Timeout        0x0032  100  099  000    Old_age  Always      -      1
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  068  058  045    Old_age  Always      -      32 (Min/Max 31/35)
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      -      211
193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      281
194 Temperature_Celsius    0x0022  032  042  000    Old_age  Always      -      32 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a  021  016  000    Old_age  Always      -      98442120
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      4
240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      40389872473567
241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      3892727563
242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      800512704
 
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%    21231        -
# 2  Short offline      Completed without error      00%    21226        -
# 3  Extended offline    Completed without error      00%    21225        -
# 4  Short offline      Completed without error      00%    21219        -
# 5  Short offline      Completed without error      00%    21218        -
# 6  Short offline      Completed without error      00%    21217        -
# 7  Short offline      Completed without error      00%    21216        -
# 8  Short offline      Completed without error      00%    21215        -
# 9  Short offline      Completed without error      00%    21214        -
#10  Short offline      Completed without error      00%    21213        -
#11  Short offline      Completed without error      00%    21212        -
#12  Short offline      Completed without error      00%    21211        -
#13  Short offline      Completed without error      00%    21210        -
#14  Short offline      Completed without error      00%    21209        -
#15  Short offline      Completed without error      00%    21208        -
#16  Short offline      Completed without error      00%    21207        -
#17  Short offline      Completed without error      00%    21206        -
#18  Short offline      Completed without error      00%    21205        -
#19  Short offline      Completed without error      00%    21204        -
#20  Short offline      Completed without error      00%    21203        -
#21  Short offline      Completed without error      00%    21202        -
 
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.

 

[warri]

Looking good again. Since you've got an UDMA_CRC_Error_Count of 4, the only other possible problem I can think of is the cable, maybe its faulty or not properly plugged in / loose.

But as I said before, otherwise I'd clear the errors and keep checking if new errors come up.

The other problem is: how come there are write errors on drives that pass all the S.M.A.R.T. tests and SeaTools diagnostics? -- as was the case with the previous one.

No idea, but I have seen very unreliable HDDs with SMART tests still passing. It'll just be hard to get an RMA from the vendor without any test failing.

 

[ser_rhaegar]

UDMA_CRC_Error_Count > 0 is a good indicator of a bad cable or port. This could also cause your zpool errors.

 

[Z300M]

UDMA_CRC_Error_Count > 0 is a good indicator of a bad cable or port. This could also cause your zpool errors.

I wondered about that, but the drives were connected to different ports (and thus also with different cables) when the errors occurred.

But maybe I should try some different cables -- maybe try connecting as many as possible to the motherboard ports rather than to the M1015. But I think I did have write errors on one of these Seagate drives way back when connected to the motherboard ports on a different motherboard -- and thus with regular SATA cables rather than breakout cables.

Are there any brands of SFF-8087 breakout cables to prefer or to avoid? The ones I'm using are "MonoPrice," I think -- from (or via) Amazon.

 

[cyberjock]

Yes, a non-zero UDMA_CRC_ERROR is an indicator of possible communication errors, but the drive has over 20,000 poweron hours. Sorry, but I'd call 4 measly errors to be par for the course.

I am actually leaning towards a SATA controller that is starting to intermittently function and may be acting erratically. Not that I think it's particularly likely.. nothing seems "likely" based on the included information.