Software2

For anyone else that comes across this thread, it's a bug in Unraid that's getting fixed in 6.12.3. For now, the workaround is to disable IPv6.

Attached

This has happened a third time, and just like before, diagnostics is unresponsive. While the machine is in this state, is there anything I can try to identify what's going on?

Hmm, well thanks for taking a look. I did try accessing the GUI on multiple computers without success. I've not tried booting into safe mode, since rebooting normally resolves the problem, at least temporarily. Since I have at least noticed this problem when my network switch had a dropout, I'm replacing that component and I'll hope as a side effect this issue can be avoided. Is there any indication of why diagnostics hung previously?

Diagnostics attached

Whoops, I don't know why my brain insisted on putting a 1 in front of the versions. I shall try that and report back. Thanks!

I recently upgraded to 6.12.2, from (I think) 6.5.x. One of my switches had a brief disconnection, and since that point, I haven't been able to access to web GUI from a browser (http://[local ip address]/Main). Other connections like SMB work just fine. And I'm still able to locally access the terminal. Rebooting the server did end up resolving the issue. However, this issue has happened again (switch had an interruption, web GUI stopped working). So this time I went to the machine, logged in to the terminal and ran `diagnostics`. The text cursor went to the next line, and nothing happened. I went to bed, came back the next day, and it's still nothing. I attempted to run `diagnostics` via ssh, and the same behavior is happening. And I did verify there is no new diagnostics file generated. What are the next steps I can use to diagnose this issue?