My server got a call trace 2 days ago but has run fine until today. I was unable to stop my docker containers in an attempt to change network settings. This usually happened after getting a call trace on 6.8.3 and ended in a forced reboot.
The call trace and docker issue might be completely unrelated but my server did not shut down properly either when I tried to reboot it. After attempting and failing a graceful shutdown (I was watching the connected display) it did a force shutdown and created the diagnostics attached below. After 10 or so minutes of waiting for it to power off I force rebooted it and it's now doing a parity check.
Recommended Comments
There are no comments to display.
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.