[solved] No unraid login Screen

[mikela]

Unlike many folks, I turn off my server every day.  I only use it for my home theater and don't want it running 24/7.  Recently I tried to reach the Login screen from my PC like I always do and received the message "This site can't be reached".  I also do not have access to any files.  Not sure where to go from here.  Any assistance would be greatly appreciated.

[jmztaylor]

31 minutes ago, mikela said:

Unlike many folks, I turn off my server every day.  I only use it for my home theater and don't want it running 24/7.  Recently I tried to reach the Login screen from my PC like I always do and received the message "This site can't be reached".  I also do not have access to any files.  Not sure where to go from here.  Any assistance would be greatly appreciated.

 

Whats the hardware?  Are you able to access via SSH?  Please post diagnostics.

[mikela]

24 minutes ago, jmztaylor said:

 

Whats the hardware?  Are you able to access via SSH?  Please post diagnostics.

Here is my hardware.  I can't seem to reach my unraid login screen via my laptop at all and therefore can't post diagnostics.  I'm wondering if hooking up my screen and keyboard directly to the server should be my next move?

[jmztaylor]

3 minutes ago, mikela said:

Here is my hardware.  I can't seem to reach my unraid login screen via my laptop at all and therefore can't post diagnostics.  I'm wondering if hooking up my screen and keyboard directly to the server should be my next move?

 

Yes that would be the best option.  If you can access it from SSH then you can just run the diagnostics command and the file will be on your flash drive in the logs folder.

[mikela]

1 hour ago, jmztaylor said:

 

Yes that would be the best option.  If you can access it from SSH then you can just run the diagnostics command and the file will be on your flash drive in the logs folder.

OK that worked.  I was able to log in that way.  My laptop was able to get the GUI.  So it seemed like everything was working again.  So I shutdown and tried with the just the laptop and no go.  I then tried the direct connection route again and now it was dumping me into the bios menu where it was indicating 404 Error.  I tried reseating the thumb drive and now it works again.  There is something intermittent going on apparently.  In any case, it's running right now so I ran a diagnostic.

tower-diagnostics-20220530-1707.zip

[mikela]

I'm guessing the diagnostics did not reveal any anomalous information.  Everything started normally today.  Fingers crossed.

[mikela]

I am still getting an intermittent issue where sometimes my server will boot up without any issues or will attempt to boot up and I wind up with this screen:

 

 

I have a dual mount USB adapter on the mother board.  If I unseat the adapter and reseat it, it seems to boot successfully and I temporarily get the following screen:

 

The blue section in the bios screen is hard to read but says "My Favorite" and it looks like it is giving me the option to delete it.  Is that something I should do?  Even though I reseat the USB adapter, it does not always boot properly...color me perplexed.

[JorgeB]

1 minute ago, mikela said:

Is that something I should do?

It shouldn't make any difference, you'll see the BIOS screen when a boot device is not found, try a different USB port/hub and make sure it's USB 2.0.

[mikela]

On 6/2/2022 at 11:20 AM, JorgeB said:

It shouldn't make any difference, you'll see the BIOS screen when a boot device is not found, try a different USB port/hub and make sure it's USB 2.0.

 

Switching to a USB 2.0 port on the back of my rack mounted server seems to have worked.

 

I swapped out my old Cruzer USB 2.0 drive with a Samsung BAR Plus USB 3.0 drive based on this review by gridrunner (aka SpaceInvader One).  Before trying the 2.0 port, I had been using this USB board adapter since my original build.  I have been using the Samsung 3.0 drive since April without any problems.  Only recently did I start having problems.  I reseated the adapter and continued to use the 3.0 drive.  That worked for awhile before reverting to previous behavior (failing to load the OS).  Taking the advice of @JorgeB and moving the Samsung drive to a 2.0 port seems to have cured the issue at least so far.