Hi!
I have been dealing with a cache disk that is misbehaving. I have already taken the following diagnostic steps:
- Extended SMART report: passed
- Memtest86+: passed
- Investigated log files myself with a lot of googeling: no definitive result
I guess I have a similar issue to this post:
I know I've had issues with the cache filling up completely, due to the Arr stack trying to download faster than the mover could keep up with. However, in those scenarios the docker containers would simply freeze, I'd kick the mover and it would all come back to life after a few minutes. In this scenario, the cache disk is not full at all.
Somehow after running memtest the cache was writable, and I was able to recreate the docker image slightly larger than before (30GB instead of the old 25GB, it was time again). However, right after this operation the cache locked itself again to read only. I do have a backup of the old docker image on the array.
I have attached diagnostics of both today, right after doing a reboot (so everything is fresh, apologies for the cleared syslog), and from a while ago when I was last investigating the issue. If any additional diagnostics are needed, please let me know.
I would also love to know how I could've found the exact issue myself, would be great if some pointers could be given to what I missed in my searches 🙂
Thanks for ya'lls time!
tower-diagnostics-20240116-1909.zip tower-diagnostics-20240103-1224.zip