This is a continuation from my previous thread

 

This morning I woke up to notifications of BTRFS errors on my cache pool. 

 

I shutdown the server, removed the problem drive (A), rebooted, and everything started fine with the cache running on the other cache pool drive (B).

 

After a bit of troubleshooting, I decided to re-seat the drive (A) and re-add it to the pool like I did last time I had this problem (in hindsight probably a mistake). I immediately saw a lot more BTRFS errors so I removed it from the cache pool again and rebooted.

 

Now when I try to start the array using the good cache drive (B), I get a "Unmountable: wrong or no file system".

 

Running a BRTFS check on the drive (B) shows many errors "parent transid verify failed on 1121019887616 wanted 565475 found 564570".

 

Have I screwed up my cache?

 

syslog-errors.txt btrfs-check.txt

I needed to get my server back up and running asap, so I removed both of the cache pool drives from my server, installed a fresh drive and set it as the cache drive, restored all the data from backups, and have re-setup my docker containers.

 

I guess my question now is, what caused this and how do I prevent it from happening again?

Please post the diagnostics.
 

6 hours ago, JorgeB said:

Please post the diagnostics.
 

Thank for the reply JorgeB.

 

Although I realize it's probably too late for these to be any use now that I've removed both of the cache drives I was using from my first post.

nas2-diagnostics-20250224-1055.zip

Was hoping there would still be something relevant in the syslog-previous, but looks like there isn't, so not possible to answer this:

17 hours ago, projectsunset said:

I guess my question now is, what caused this and how do I prevent it from happening again?

 

2 minutes ago, JorgeB said:

Was hoping there would still be something relevant in the syslog-previous, but looks like there isn't, so not possible to answer this:

 

 

Thank you JorgeB, I appreciate you taking a look.