Unraid not accessible via Browser or SSH (but Docker Containers and VMs are still working)

[zAch523]

Hello Community!

I have a really strange problem with Unraid. Sometimes at random I can't access the WEB-GUI or connect via SSH. The crazy thing about this is, that the docker containers and VMs are still working.

For example, I can use Home Assistant (VM) or connect to my FileRun-Instance (Docker) and it even seems like it is downloading games to the SteamCache (Docker)...  But when I try to go to the web login at my servers ip it takes a very long time until the error 500 appears. If I try to connect via SSH it stops after I entered my password like this:

 

I had the problems for a couple of days now and it really makes me feel uncomfortable because I have to pull the plug on my server...

I have attached the diagnistics file from yesterday after I restarted unraid (by unplugging the server 😵 ) but I am not even sure if this contains helpful information?

 

I would be very thankfull if anyone could help me figure this out!

unraid-diagnostics-20221116-1947.zip

[zAch523]

Little update... I connected a monitor to the unraid server and instead of the usual text I just have a black screen.

Edited November 18, 2022 by zAch523
typos

[ljm42]

1 minute ago, zAch523 said:

Littel update... I connected a monitor to the unraid server and instead of the usual text is just have a black screen.

Just guessing, but the monitor probably needs to be connected before you turn on the server, otherwise your motherboard won't initialize the hdmi port

[zAch523]

3 minutes ago, ljm42 said:

Just guessing, but the monitor probably needs to be connected before you turn on the server, otherwise your motherboard won't initialize the hdmi port

Normally the monitor turns off after a couple of seconds if it receives no signal (I tried the PCIe-graphics card first 😉).

With the mainboard HDMI the monitor seemed to receive a black image. Do you mean this, or should it just turn off if the port is not initialized?

[ljm42]

Pressing keys on the keyboard may wake it up? Otherwise I think you'll need to reboot and figure out where to plug in the monitor until it lights up during boot.

 

Or you can wait for someone else to chime in  

[zAch523]

I think the HDMI was correct (I unplugged the graphics card for debugging reasons now). I tried "waking" up the system with mouse and keyboard, but no success... 

 

So now after "hard resetting" the machine I have access again and pulled the diagnostics files again. Maybe this is worth something 😅

unraid-diagnostics-20221118-2046.zip

Edited November 18, 2022 by zAch523
clearification

[zAch523]

It happened again... something I noticed is, that whenever I have to kill my server, after the reboot it starts the parity check. This seems strange to me, because I turned of scheduled checks...

[JorgeB]

Just now, zAch523 said:

after the reboot it starts the parity check

This means it's detecting an unclean shutdown, posting the diagnostics auto saved in the flash drive (/logs folder) might give some clues.

[zAch523]

The folder looks like this:


Which file do you mean?

[JorgeB]

Latest one should be fine, it should be from the date/time you last rebooted.

[zAch523]

2 hours ago, JorgeB said:

Latest one should be fine, it should be from the date/time you last rebooted.

 

I attached the latest one... Is there a difference between these files and the ones I sent before, that came from the diagnostics tool.

Also I enabled writing the syslog to flash - would this be of any help?

unraid-diagnostics-20221119-0005.zip

[JorgeB]

Currently set shutdown timeout is not enough, change from 90 to 150 secs (Settings -> Disk Settings), you can also stop the array and time how long it takes, than add a few seconds to that.

[zAch523]

Quote

change from 90 to 150 secs

Thanks for the tip - Can this cause the WEB-GUI and SSH to become unresponsive?

Another thing I remembered is, I get Oout Of Memory Errors quite often... Maybe this is the cause?

Edited December 1, 2022 by zAch523
applied proposed settings

[JorgeB]

That will only help with unclean shutdown.