Had some networking issues out of the blue for no apparent reason, no recent changes just couldn't see my server anymore. Thought nothing of it and did a restart only to find I still could not see my server. Thought that was odd but no problem I'd just take a look locally in the GUI. Unable to boot to GUI / GUI in safe mode. I get the load up text then the dreaded blinking cursor I have seen in a few threads on here. No idea what has happened, as the server was working great with no major issues the past six months. Hardware was upgraded about halfway through that with zero issues. Hoping someone might be able to see an easy thing to fix in my logs. Thanks in advance.

matrix-diagnostics-20220529-2055.zip

Edited June 5, 20224 yr by Gummy
Resolved one of two problems

I was successful in getting local GUI mode working by enabling CSM from my BIOS thus allowing me to boot to my USB stick without UEFI enabled, doing so allowed GUI mode to work as suggested in other posts. In my specific scenario with my ASUS motherboard my steps were:

 

Boot into BIOS

Go to advanced

Boot

CSM

Launch CSM > Enabled

Change Boot Option from UEFI Sandisk Cruzer to Sandisk Cruzer

 

As for my network  issues, still a little stumped here, my IPV4 default gateway was 192.168.0.1 and my understanding is that needs to be the router's IP, which it is. However with ipconfig in windows it shows my default gateway as 192.168.1.1. I tried both and now I am getting Interface Ethernet Port 0 is Down.  I have tried getting rid of my static IP and going back to automatic with no luck.  Open to suggestions to try: 

 

 

 

Edit:

Seemed to have got it working

-Tried different Ethernet cable, no luck, tried that ethernet cable on my desktop and it worked no problem

-Disabled bonding

-Tried Fix Common Problems suggestion of setting my DNS Server to 8.8.8.8 and 8.8.4.4

-Tried Rebooting

-Tried once again setting my server assignment to automatic from static and it started working again, it set my DNS Server to 1.1.1.1 and 8.8.8.8

-Switched back to my static IP and kept those DNS servers and it seems to still be working. 

-Reenabling bonding caused it to stop working again, so went back to leaving it disabled

-Successfully went back to original ethernet cable

 

Hopefully this helps someone else in the future. From my understanding bonding allows you to run two network controllers and two ethernet cables for a more stable connection, is this correct? Due to me only having one network controller, I imagine I do not need it. Makes me wonder why the server worked beforehand with bonding enabled. 

Edited June 6, 20224 yr by Gummy