Caboose20 Posted December 7, 2023 Share Posted December 7, 2023 Hello, I have been having this problem for a while now and thought its finally time to see if I can get some assistance. For some reason, my cache drive is entering read-only. If I reboot the array, it triggers a parity check but seems to temporarily solve the issue for a few days. Unfortunately the issue keeps coming back and I cannot narrow down what is causing it. Running Unraid Version: 6.12.6 Hoping someone can point me in the right direction Thanks, tower-diagnostics-20231207-0934.zip Quote Link to comment
itimpi Posted December 7, 2023 Share Posted December 7, 2023 The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to can get a log that survives a reboot so we can see what happened prior to the reboot. Quote Link to comment
JorgeB Posted December 7, 2023 Share Posted December 7, 2023 Switch the docker network to ipvlan, the filesystem issue could be RAM related, start by running memtest. Quote Link to comment
Caboose20 Posted December 7, 2023 Author Share Posted December 7, 2023 5 minutes ago, itimpi said: The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to can get a log that survives a reboot so we can see what happened prior to the reboot. I Rebooted yesterday when the server was working normally. This diagnostic is from the server right now which is still in a failed state. I haven't yet restarted it in order to preserve the logs. Quote Link to comment
Caboose20 Posted December 7, 2023 Author Share Posted December 7, 2023 5 minutes ago, JorgeB said: Switch the docker network to ipvlan, the filesystem issue could be RAM related, start by running memtest. I'll give these a try tonight and publish the result. Quote Link to comment
Caboose20 Posted December 7, 2023 Author Share Posted December 7, 2023 42 minutes ago, itimpi said: The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to can get a log that survives a reboot so we can see what happened prior to the reboot. I realized I did do this for another problem so here is the logs for the last few days syslog-192.168.1.216.log Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.