GumGum Posted December 22, 2023 Share Posted December 22, 2023 I have attached the diagnostics file. I noticed that I could not start any docker container. Restarting docker failed. Docker won't start after reboot Logs indicate that cache has switch to read-only mode. Please help! apollo-diagnostics-20231221-2042.zip Quote Link to comment
GumGum Posted December 22, 2023 Author Share Posted December 22, 2023 I started it up in maintenance mode and ran a 'check' on the cache pool. This showed that there were errors, so I ran a `--repair` on it. That seems to have fixed the issue. I then ran a scrub and there were no errors. Will try to reboot back into normal mode and see if everything works. If everything gets back to normal, I will most likely move everything off the cache and reformat it to ZFS. Quote Link to comment
Solution GumGum Posted January 5 Author Solution Share Posted January 5 The errors kept coming back and I was able to identify the root cause as a memory issue. Once I ran memtest on both modules, both showed multiple errors. Waiting for my replacements from GSkill. Hope that helps other folk who have faced something similar. Quote Link to comment
itimpi Posted January 5 Share Posted January 5 4 hours ago, GumGum said: The errors kept coming back and I was able to identify the root cause as a memory issue. Once I ran memtest on both modules, both showed multiple errors. Waiting for my replacements from GSkill. Hope that helps other folk who have faced something similar. Worth pointing out that sometimes you get such errors because the memory controller is struggling to handle all modules and it works with less modules. Have you tried repeating the memtest on individual modules as it is very rare for multiple modules to fail at the same time? 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.