Frankthetank907

interesting, that is good to know, that would explain all the errors it is picking up, thanks for that info! Still would like to figure out why it decided to automatically write corrections to parity even with that option not being selected in the settings though, that could potentially be very problematic if there was some sort of corruption on the array.

I did do one back in October when I swapped an older 8TB parity drive out with another 18TB WD red pro, why?

Interesting, like I said in my original post this is the first time it has ever done something like this, and I did just update to the 6.12.6 release so maybe it is a new bug, or it could be a coincidence too but I am not going to pretend that I know what I am talking about when it comes to how the underlying system actually works lol. Will be interesting to see if you or anyone else is able to replicate this issue. Also thanks for letting me know about your plugin, I will install it after this parity check finishes for sure. Looking forward to see if you are able to come up with anything on your system, and thanks for looking into the logs and helping out, I have no idea what I am looking at when I was sifting through them lol.

I forgot to mention, during the parity check (which is still running) I do have all of my docker containers running and doing their normal tasks, I am not sure if this could have somehow caused a sync error between the disks and parity, but I have never hand an issue with it in the past.

I have been running unraid for a few years now, never have I ever had any errors detected when doing a parity check until now. As you can see from the screen shots I have attached it appears as if the automatic parity check is also writing corrections to parity, which I am confused by because I have always had the option for it to automatically write corrections to parity during scheduled checks deselected. I am running Unraid version 6.12.6 as of 4 days ago, I have also attached the diagnostics file for troubleshooting, if anyone can help me understand what is going on it would be greatly appreciated. Thanks for any help in advance. tower-diagnostics-20231205-2317.zip

This did the trick, thank you for the help!

I will give this a shot!

Hi, I have been running my server for almost 2 years with no issues, tonight I was having an issue where my server log file was filling up so I rebooted the server, when it came back up the second cache drive was missing completely from the system, like I never even had it in there. I tried reseating the connectors and even tried other connectors from a different drive and it still wouldn't show up, so I tried reducing the cache pool back to 1 drive until I can order a replacement drive. When I tried bringing the array online the remaining cache drive would not mount, it was giving me the "unmountable : not mounted" error, so I went to the drive and checked the BTRFS file system check in read only mode I also went to the drive and took a capture of the disk log itself I connected the "bad" drive to my computer and it shows up in disk management so I am unsure if it is actually bad or not. What can I do from here? I want to try to recover the file system if at all possible, any help is greatly appreciated.