-
Server stops responding. Receive "login: timed out after 60 seconds" when trying to log in locally
I think I figured out the issue. I had to Disable C6 State in my BIOS. Once I did that I haven't had any issues of the computer shutting down/going to sleep
-
Server stops responding. Receive "login: timed out after 60 seconds" when trying to log in locally
I did have a network hiccup at that time where it lost connectivity for about thirty seconds but it came back. It did end up losing connectivity permanently around 20:45ish and I had to do a hard reboot at 21:03. Honestly it just seems like the computer goes in sleep/standby mode, but I can't find anything in the BIOS where I can turn that off.
-
Server stops responding. Receive "login: timed out after 60 seconds" when trying to log in locally
Diagnostic file attached. File from first post is from syslog server mediaserver-diagnostics-20230823-0856.zip
-
Server stops responding. Receive "login: timed out after 60 seconds" when trying to log in locally
I'm having issues with Unraid and I have no idea what or where to troubleshoot. I'm leaning towards hardware but I've had this machine for several years and didn't have any issues. The problem is that the server just randomly stops. I don't think it crashes, I would like to think I would see something the unraid logs that would tell me there's a problem and needs to shutdown but I can't seem to find anything. The tower remains powered on, but I can't access remotely by WebGUI, telnet or SSH. I can't even get a ping response back. I've hooked up a monitor, keyboard and mouse to the server I see the default "MediaServer login:" but when type in the username and hit Enter nothing happens then I get a message saying the "login: timed out after 60 seconds" then presented back to the "MediaServer login:" prompt. Only way I can get it back up is just by holding the power button and do a hard reset. The really weird thing is when I do the hard reset of course it detects it as an unclean shutdown and does a parity check. The whole time it does a parity check the server never hangs/crashes and performs the entire parity check with no issues which takes over 24 hours. But as soon as it's done sometimes it takes as short as 30 minutes sometimes a few hours it will stop responding again. It just seems like the system goes into a sleep state when it's not running a parity check. If it was a hardware issue I would expect that the server would hang/crash during the parity check but never does. There doesn't seem to be any consistency, I've ran memtest86 and passed with no errors so it doesn't seem to be memory. This used to be my gaming rig for several years and had no issues with any hardware when I had Windows installed. I'm just at a loss of what is going on and if someone could point me in the right direction I would greatly appreciate it. I'm attaching my syslog file if that helps, I don't know what else I can run/capture to better troubleshoot this issue. syslog-192.168.86.55.log
kinky-chin3536
Members
-
Joined
-
Last visited