Thanks for the troubleshooting help. That doesn’t really explain the “used space” calculation being reset every time does it? i know the upload/download errors are a symptom of other things. its really hard to watch the logs when its crashing, cuz they autoclose (by unraid design now…makes sense why, just annoying)…i have to figure out how to stop that nonsense.
I have added the extra 30s to the write and read timeout (I added them. Those lines wasn’t there at all…just the verify read/write interval settings {they show 3m and 5m respectively); but they have the pound sign in front of them as well, i believe that means ignore?? i left them as they were)…now we wait…and i’ll post the results below:
…a little while later…
So after adding those 2 lines to the config.yaml (and rebooting the server just for kicks)…the node is still “storming”, as im calling it, and restarting constantly. Seen some lazy filewalker errors too, but i think thats just cuz partial files are being written as it crashes.
I also just installed some drives to temporarily hold the data while i rebuild this stupid pool…never using BTRFS again (i lie…it has some good points. just too cumbersome to navigate when there are better options. im also just learning non micro$ platforms and FS’s, after avoiding them since high school.)