Unrecoverable error

[wintermute000]

I got an email this morning about an unrecoverable error on my main RAIDZ2 array.

When I check zpool status, the only thing I see is 1 checksum error. Is this a problem or is 1 error (the first I've received in ~18 months) and the minor scrub repair insignificant?

Freenas 9.3, Asrock C2550D4I, 16Gb ECC DDR3, 6x4Tb HGST Deskstar NAS HDD in RAIDZ2, 1x256Gb Sandisk Ultra Plus SSD in ISCSI extent, 1x 256Gb Sandisk Ultra Plus SSD scratch disk, Seasonic SSR-450RM 450W, Fractal Design Define R2



[root@freenas] ~# zpool status -v
pool: bigdisk
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: scrub repaired 32K in 8h54m with 0 errors on Tue Mar 15 09:55:18 2016
config:

NAME STATE READ WRITE CKSUM
bigdisk ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/6f446c94-2f59-11e4-81f2-d05099264f06 ONLINE 0 0 0
gptid/6fbe1f96-2f59-11e4-81f2-d05099264f06 ONLINE 0 0 0
gptid/70290449-2f59-11e4-81f2-d05099264f06 ONLINE 0 0 0
gptid/709666da-2f59-11e4-81f2-d05099264f06 ONLINE 0 0 0
gptid/70f9921f-2f59-11e4-81f2-d05099264f06 ONLINE 0 0 1
gptid/71633243-2f59-11e4-81f2-d05099264f06 ONLINE 0 0 0

errors: No known data errors

Note a few days ago I did get a smart error on this drive (UDMA_CRC_Error_Count), but again, the counter is only 1. I'm thinking this is the culprit of the error and the scrub fixed the corrupted data?

[root@freenas] ~# smartctl -A /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 READ SMART DATA SECTION ===
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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 137 137 054 Pre-fail Offline - 79
3 Spin_Up_Time 0x0007 124 124 024 Pre-fail Always - 621 (Average 621)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 881
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34
9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 13081
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 44
192 Power-Off_Retract_Count 0x0032 093 093 000 Old_age Always - 9109
193 Load_Cycle_Count 0x0012 093 093 000 Old_age Always - 9109
194 Temperature_Celsius 0x0002 171 171 000 Old_age Always - 35 (Min/Max 17/59)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 1

 

[Mirfster]

Are you running SMART Long tests? If not, please perform the long tests for each drive (Example: smartctl -t long /dev/ada1) and then post the output in CODE tags.

 

[wintermute000]

running, now on the drive with the checksum error, report back in 560 minutes LOL

 

[jdong]

I just ran into the exact same issue -- after adding 2 HGST drives to my NAS with the same mobo I started getting 2-3 checksum errors per scrub.

Turned out this was because I was using the Marvell SATA ports. After switching to the Intel SATA ports I was able to scrub twice with no errors. So... Along with the usual checks I would recommend double checking which SATA ports you are using.

 

[Mirfster]

running, now on the drive with the checksum error, report back in 560 minutes LOL

Should already have been running scheduled Long tests. :P

 

[wintermute000]

I'm using all 8 of the built in SATA3 controllers. Nothing on the 4xSATA2.
Zero issues in 18 months so pretty sure its not that.

Code:

[root@freenas] ~# smartctl -a /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:     HGST Deskstar NAS
Device Model:     HGST HDN724040ALE640
Serial Number:    PK2334PBHE63DR
LU WWN Device Id: 5 000cca 23dd41743
Firmware Version: MJAOA5E0
User Capacity:    4,000,787,030,016 bytes [4.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:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Mar 15 23:36:05 2016 AEDT
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:                (   24) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        ( 560) minutes.
SCT capabilities:              (0x003d) 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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   137   137   054    Pre-fail  Offline      -       79
  3 Spin_Up_Time            0x0007   124   124   024    Pre-fail  Always       -       621 (Average 621)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       883
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   121   121   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       13094
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       44
192 Power-Off_Retract_Count 0x0032   093   093   000    Old_age   Always       -       9122
193 Load_Cycle_Count        0x0012   093   093   000    Old_age   Always       -       9122
194 Temperature_Celsius     0x0002   187   187   000    Old_age   Always       -       32 (Min/Max 17/59)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       1

SMART Error Log Version: 1
ATA Error Count: 1
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 occurred at disk power-on lifetime: 12949 hours (539 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 57 4d 07 08  Error: ICRC, ABRT at LBA = 0x08074d57 = 134696279

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 c8 58 4c 07 40 00   2d+00:05:11.703  WRITE FPDMA QUEUED
  61 00 c8 58 4b 07 40 00   2d+00:05:11.702  WRITE FPDMA QUEUED
  61 00 c8 58 4a 07 40 00   2d+00:05:11.701  WRITE FPDMA QUEUED
  61 00 c8 58 49 07 40 00   2d+00:05:11.700  WRITE FPDMA QUEUED
  61 c8 c8 90 48 07 40 00   2d+00:05:11.700  WRITE FPDMA QUEUED

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%     13091         -
# 2  Short offline       Completed without error       00%     13023         -
# 3  Extended offline    Completed without error       00%     12552         -
# 4  Short offline       Completed without error       00%     11367         -
# 5  Extended offline    Completed without error       00%     11256         -
# 6  Short offline       Completed without error       00%     10503         -
# 7  Short offline       Completed without error       00%     10323         -
# 8  Extended offline    Completed without error       00%     10211         -
# 9  Short offline       Completed without error       00%      9783         -
#10  Extended offline    Completed without error       00%      9551         -
#11  Short offline       Completed without error       00%      9122         -
#12  Short offline       Completed without error       00%      9064         -
#13  Short offline       Completed without error       00%      8762         -
#14  Extended offline    Completed without error       00%      8554         -
#15  Short offline       Completed without error       00%      8052         -
#16  Extended offline    Completed without error       00%      7817         -
#17  Extended offline    Completed without error       00%      7225         -
#18  Short offline       Completed without error       00%      6736         -
#19  Extended offline    Completed without error       00%      6505         -
#20  Short offline       Completed without error       00%      6376         -
#21  Short offline       Completed without error       00%      6136         -

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.

 

[Mirfster]

I don't see anything major with ada4; what about the other drives?

 

[joeschmuck]

It is possible you have a SATA cable going bad. The first question I'd ask you is have you been into the computer case recently? Look at my signature for for the link to the SMART Wiki page, ID 199 indicates a data transmission error. This does not appear to be a drive failure yet but it could be the drive electronics once you have ruled out other possible components.

1) Replace the SATA cable for this drive.
2) If the problem occurs again for the same drive, swap the SATA ports on the motherboard for this drive with any other drive.
3) If the problem occurs again for the same drive, the drive is failing. If the problem moves to a different drive then the SATA cable is bad or the SATA port (controller) is bad, could be firmware too depending on your controller but ask for more help if this is the case.

Good luck.

 

[jdong]

I'm using all 8 of the built in SATA3 controllers. Nothing on the 4xSATA2.
Zero issues in 18 months so pretty sure its not that.

Well I got no checksum errors for the first 12 months either until I added 2 more drives to the system, which seemed perfectly harmless. BTW, you are using the Marvell controller if you're using all SATA3. That was pretty much what I did too because I thought "hey why wouldn't I want SATA3 over SATA2"?

http://www.asrockrack.com/general/productdetail.asp?Model=C2550D4I#Specifications

1. 2 SATA3 6.0Gbps, 4 SATA2 3.0Gbps by C2550
2. 4 x SATA3 6.0 Gb/s by Marvell SE9230, 2 x SATA3 6.0 Gb/s by Marvell SE9172

If your checksum errors follow one drive across multiple scrubs, then it's probably not related to this. But for me, my checksum errors would randomly show up on all my drives (1 or 2 per scrub). I also had no explanation for why this setup worked for 12+ months for me, no scrub errors, and it was plugging in two more drives that seemed to throw it over the edge.

 

[wintermute000]

other drives are clean, zero errors

Thanks guys, will replace the SATA cable if it happens again.

Can I move the SATA ports without changing any Freenas config? I didn't think so or is it smart enough to do this??
e.g if I move ada4 to ada7 position will it just pick it up? ditto with any other drive or multiple drives???

 

[hugovsky]

You can move drives. No problem. ZFS uses own id of drives.

 

[joeschmuck]

Exactly, ZFS doesn't care, part of the beauty of being able to relocate the drives into another computer system should your motherboard or drive controller break. This is one of the main reasons I love FreeNAS.

 

[jdong]

I can confirm what the others said. FreeNAS did not care at all when I moved all the drives. And I also saw no performance difference with a bunch of WD Reds and HGST 7200RPM drives.


Sent from my iPhone using Tapatalk

 

[SweetAndLow]

other drives are clean, zero errors

Thanks guys, will replace the SATA cable if it happens again.

Can I move the SATA ports without changing any Freenas config? I didn't think so or is it smart enough to do this??
e.g if I move ada4 to ada7 position will it just pick it up? ditto with any other drive or multiple drives???

There is no relationship between ada devices and sata ports. If you unplug and plug back into the same port you might get a different ada identifier.

 

[jdong]

There is no relationship between ada devices and sata ports. If you unplug and plug back into the same port you might get a different ada identifier.

Correct, and for the OP's clarity, it's worth mentioning that FreeNAS internally tracks drives by their GPT labels, which is metadata stored on the drive. ZFS additionally tracks disks by metadata on each member's filesystem, and even without GPT labeling does not care when drives change their block device names.

So, nothing on the system cares about the ada numbers being renumbered. FreeNAS's GUI simply resolves GPTIDs to ada numbers for your own convenience, so if you get in a situation where you need to run terminal commands, you know what disk the GUI is talking about, without googling for that FreeBSD command to turn GPTIDs to block device names ;-)