Tower kernel: BTRFS error (device sdg1)

[mwasserman]

Hi all, I've been using Unraid for about a year now without any major issues. I looked into my log the other day and started to notice many the follow warning.

Mar 31 23:52:09 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:09 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:09 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:09 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:10 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:10 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:10 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503
Mar 31 23:52:10 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 620778586112 wanted 16531233 found 15373503

In my case sdg is an SSD Cache drive in an array of 2 Cache drives. I'm assumming (sdg1) and sdg are referring to the same drive? Is this correct?

I've been googling around and found many many pointing to bad SATA cables suggested to run scrub. I've run the scrub operation and it is reporting "no errors found". What are my next steps in trying to fix this warning?

 

[trurl]

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post 

[mwasserman]

I have attached my diagnostics zip file

tower-diagnostics-20200401-0807.zip

[JorgeB]

One of the cache devices dropped offline before (one or more times):

Mar 29 19:14:52 Tower kernel: BTRFS info (device sdg1): bdev /dev/sde1 errs: wr 107909131, rd 5294447, flush 1500255, corrupt 0, gen 0

 

Since the pool is a mirror all errors are correct automatically, and if the scrub didn't find any it means it's all up to date for now, but see here for better pool monitoring.