Mirror ZFS showing intermitant WRITE_FPDMA_QUEUED CAM status: Uncorrectable pari

Started by jonny5, October 24, 2023, 11:02:13 PM

Previous topic - Next topic
The error will pop up from time to time, more often when I was using the RAM to map /var/log which I found odd. It will seem to have to do with the pressure or write/backup load the router/OS is going through.

WRITE_FPDMA_QUEUED CAM status: Uncorrectable parity/CRC error

It will mention three retries. It appears to resolve on its own, but appears alarming all the same.

In short, I found this post about how to handle issues like this in FreeBSD and wanted to check with the group, have you seen this error, and if so, does this solve it for you (too? - still testing) or did you find another way to resolve the oddity.

Thread about CAM status errors in FreeBSD:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745#c59

The initial try for my setup was to issue these commands, note, my 'tags' were previously 32:
camcontrol tags ada0 -N 25
camcontrol tags ada1 -N 25


The hardware is only slightly old:
ASRock 970 Extreme3 R2.0 with AMD FX-8320E Eight-Core Processor, AMD graphics, 4 memory modules (4 x Crucial BLS8G3D18ADS3.16FE 8GB), 2 drives (2 x Samsung SSD 870 EVO 500GB)

Any feedback is welcome, I am new to FreeBSD (Gentoo->RHEL->Ubuntu->Manjaro->FreeBSD) and quite new to ZFS.
Custom: ASRock 970 Extreme3 R2.0 / AMD FX-8320E / 32 GB DDR3 1866 / X520 & I350 / 500GB SATA

QuoteWRITE_FPDMA_QUEUED CAM status: Uncorrectable parity/CRC error
This is a hardware issue. The question is, which part. Controller - cabling - (possibly) backplane - disk/SSD drives.

I'd switch the cheapest component first and just replace the cabling for good measure.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)