Hello all and thank you for taking the time to read my issues. 

I checked the recent parity check and found 3415 errors. This started me down the road of what is wrong so I checked the logs and found what looks like errors with the cache drive. 

A lot of these: Tower kernel: BTRFS error (device nvme0n1p1): bad tree block start, mirror 1 want 1217675264 have 954269588246591778

 

and these: Tower kernel: BTRFS error (device nvme0n1p1): tree first key mismatch detected, bytenr=652554223616 parent_transid=12074950 key expected=(481234,92,3210737364) has=(481234,84,3210737364)

 

I started looking around the internet to see if I could fix the problem and what I could gather it is likely the cache SSD is either bad or has corrupted blocks. I ran fix common problems and it did not report anything. I ran "btrfs dev stats /mnt/cache" and it reported 27 corrupted errors, but when I tried to use the scrub command it did not report any errors. Also the SMART report for the NVME is not reporting any issues. I have attached my diag file and just want to make sure the parity errors are from the cache and not the array before I do a parity write correction, and replace the cache NVME if needed.

 

I am running a i910900K with a Z490 ASUS MOBO

 

3060 EVGA GPU

 

All of the HDD are shucked drives.

 

Docker is binhex plex and Krusader

 

Plugins: Fix Common Problems, AMD Vendor Reset, CA Backup / Restore Appdata, Community Applications, Dynamix Auto Fan Control, Dynamix S3 Sleep, Dynamix System Buttons, Dynamix System Information, Dynamix System Statistics, Dynamix System Temperature, GPU Statistics, Intel GPU TOP, Nvidia Driver, Tips and Tweaks, Unassigned Devices, Unassigned Devices Plus, Unassigned Devices Preclear, User Scripts.

 

UNRAID version - 6.12.10

 

tower-diagnostics-20240813-1250.zip

Start by running memtest

Thank you for the response. I am working on doing the memtest now, and I will update this thread when I have the test results.

@JorgeB, thank you again for the reply. I ran the memtest three times and it passed all three times with zero errors.

Memtest is only definitive if it finds errors, reboot to clear the log, then run two consecutive correcting parity checks without rebooting and post new diags.

 

 

@JorgeB, thank you for the continued help. Here are the new diags from the two consecutive correcting parity checks after a reboot. I have also upgraded to UNRAID version 6.12.11.

tower-diagnostics-20240825-0925.zip

2nd check didn't find any errors, so should be OK now, but see if the next scheduled check finds more, if it doesn't, the issue should be resolved.

Thank you for the help.