CAM status: Uncorrectable parity/CRC error

[briancmoses]

Two new threads in one week, I'm a little disappointed in myself! I kicked off a scrub today so I can safely pull out a defective drive that's been giving me some SMART errors (OfflineUncorrectableSector) and get it RMAed. During that scrub I noticed this error in the web UI's console output:

Code:

Sep 24 17:44:57 DrTeeth kernel: (ada6:ahcich4:0:0:0): READ_FPDMA_QUEUED. ACB: 60 18 b8 90 c7 40 07 00 00 00 00 00
Sep 24 17:44:57 DrTeeth kernel: (ada6:ahcich4:0:0:0): CAM status: Uncorrectable parity/CRC error
Sep 24 17:44:57 DrTeeth kernel: (ada6:ahcich4:0:0:0): Retrying command

The OfflineUncorrectableSector are on a different drive, so I don't think it's related. But I thought it'd be worth mentioning here first.

Here's the output of: smartctl -q noserial -a /dev/ada6

Code:

[root@DrTeeth] ~# smartctl -q noserial -a /dev/ada6
smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p10 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD20EFRX-68AX9N0
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
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 Sep 24 18:04:54 2014 CDT
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:                (27600) 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:        ( 279) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x70bd) 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       -       0
  3 Spin_Up_Time            0x0027   177   175   021    Pre-fail  Always       -       4133
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       14
  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   095   095   000    Old_age   Always       -       3859
 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       -       14
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       11
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   108   106   000    Old_age   Always       -       39
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%         5         -

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@DrTeeth] ~#

Am I translating that SMART output correctly in that there's not really anything all that concerning in there?

I've been digging around all the CAM status: Uncorrectable parity/CRC error threads I can find in the forum and one of the suggestions seems to be swapping cables on that particular drive or trying it in a different SATA port. Is that a good next step?

I tweaked the scheduled SMART tests to run the long test tomorrow morning morning, is there a way to kick them off manually?

Again, thanks in advance for the help not only in this thread but all the other similar ones I've been digging through. Sorry if I overlooked my answer if it's in another thread!

 

[cyberjock]

I'd say everything looks fine, with one exception. Your one and only SMART test, a long test, was performed at power-on hours=5. You are at 3859, which is approximately 160 days since a SMART test has been run. So I'd *definitely* setup SMART tests. I'd do a short, conveyance, and long test on ada6 and see what happens.

If I were a betting man my guess would be that the drive will pass all of the tests and the problem is more than likely the data cable for that disk.

If you don't know what schedule to do SMART tests on I have a thread with what I use. ;)

 

[briancmoses]

Wow! Interesting, I could've sworn that I had the SMART Long/Short tests both set up to run periodically throughout the month, I guess I probably boogered that up.

Edit: I found the thread over in the Configuration forum: http://forums.freenas.org/index.php?threads/scrub-and-smart-testing-schedules.20108/

 

[briancmoses]

Alright, I read through your post. It actually rang a bell, I think I may have used it as a template when I first created my Long/Short SMART test schedule. It's a little concerning that it hasn't been running on this one particular drive. The meta-data for my tests was basically the same, except on different days of the month but for some reason it's not been happening as I would've expected.

Assuming that all of my drives belong to both of these tests, can anyone think of a reason why a Long Self-Test won't run overnight at 3AM?

Edit: I caught this too late, FreeNAS is amazing but it's not capable of time-travel. I've updated the Long Test to run at 3AM on the 12th and 26th of every month. So hopefully it'll run tonight!

​

Is there anything I can check behind the GUI to make sure these are getting executed correctly? I tried poking around the crontab, but I didn't have much luck but that's probably because I have a VERY limited *NIX skillset.

 

[cyberjock]

Click on them and check the disks chosen. I bet that disk isn't selected for the tests. ;)

 

[briancmoses]

Click on them and check the disks chosen. I bet that disk isn't selected for the tests. ;)

I'm betting that you were right. I've revised these two tests quite a few times the past couple days. I bought 4 disks originally, than bought 3 more to add to it at a later date. I bet each of the 2nd grouping of disks was originally missing from the tests' configuration. I bet in my first round of edits, I noticed not all the disks were selected and added the missing disks.