Hello!

Of course one of my servers went down the day I left for vacation, a simple reboot by my mom coming by to take care of the dogs didn't fix it.

I am now home and am confused.  I can't access the server, it boots up sometimes.  This last time required me to f2 and go to bios and then click on the USB and it booted.  I clicked to boot to GUI, and watched it load.  Everything worked until it got to the login page, then my screen went blank.  

When I login to Unraid connect, I can see it's online, but I can't access it from anywhere so I can't get a diagnostic or anything.

Any help?  Already tried pulling the plug, powered it down overnight, rebooted the router (can see it on my network, at this IP) and still cant access it.

Tower is the server I'm having issues with.  

Any help would be appreciated!!

Thanks!

 

I wonder if your address got reassigned to a different nic.  Try connecting different ports to your switch and look for (ping) that .10 IP.

12 minutes ago, Veah said:

I wonder if your address got reassigned to a different nic.  Try connecting different ports to your switch and look for (ping) that .10 IP.

Ahh!! That fixed it!! Changed it to a different port on my switch and it pulled up!! I'll try to switch it back here in a little bit to see if the port is going bad, or if it just got stuck or something.

Thanks so much!! Such a simple solution sometimes goes over our heads!!

 

Well that's interesting....it pulled up, and I logged in, and then I go to click on docker....now it's gone again

It's still showing online on my router, and unraid connect still shows it connected as well.

I turned it off and back on again....this pops up right before I lose access....of course its not up long enough for me to access a syslog.  I tried powering up in safe more, gui no plugins....it seems the array starting is what causes the crash.

So here is the syslog.  I see network errors, any thoughts? 

tower-syslog-20240720-1452.zip

Please post the complete diagnostics.

7 minutes ago, JorgeB said:

Please post the complete diagnostics.

 

tower-diagnostics-20240720-1308.zip

Network cfg has a 4 NIC bound but only one NIC is currently being detected, delete/rename /boot/config/network.cfg and reboot.

33 minutes ago, JorgeB said:

Network cfg has a 4 NIC bound but only one NIC is currently being detected, delete/rename /boot/config/network.cfg and reboot.

ok, so I went and deleted that network.cfg file and rebooted....it still took several reboots before I got the bios part and it actually booted to unriad.  Once it did, it didn't have that error above.  That timeout error, but once the array started trying to turn on again, it became unreachable again.

I was going to login and check the network.cfg file, but after I got the diag file I hear a click behind me, and the monitor goes dark.  I then go and turn it off and rebooted it to try to get it again, and in the middle of booting up, like booting up unraid it clicks and turns off again...

To clarify, by turn off I hear the click, but all the lights, fans etc etc are still on.  I just can't see the display anymore, and I can't access it anymore if it was started up by that time. 

Thanks

 

tower-diagnostics-20240720-1357.zip

26 minutes ago, coltonc18 said:

it still took several reboots before I got the bios part

That sounds like a hardware issue.

 

 

Just now, JorgeB said:

That sounds like a hardware issue.

 

 

Does the diagnostic point to anything?  This is all new hardware, as of like Feb, I know that doesn't mean it can't fail.  I already pulled the memory sticks, one at a time and that didn't make a change.  Just trying to narrow this down.  

Most hardware issues don't leave anything logged, but for sure a board failing to post multiple times has nothing to do with the OS.