I've had Unraid running pretty solidly on:

 

• Intel 9700k
• Gigabyte Aorus z390
• 64 GB RAM

 

Today, I installed my old GTX 1070 so that I could passthrough for some games.  However, Unraid will no longer boot.  The system now only takes me into the bios page.  I've changed the settings so that it boots with the integrated graphics enabled but that has not stop the system from going right into bios rather than loading Unraid.  Any thoughts?  I appreciate the help.

Are you local with a monitor or trying remotely?

I over came this issue with a monitor that could be connected to all the GPU's outputs. I think I needed to make the dGPU as the main one. But there seems to be a fight between Igpu a dGpu in who is in control. I can no longer boot into graphical unraid only the cli. then Use the web login.

 

But I do not remember exactly and my machine is in another building or I would look.

6 hours ago, rockbox948 said:

The system now only takes me into the bios page.

That suggests the boot device is not correctly configured.

8 hours ago, grumpy said:

Are you local with a monitor or trying remotely?

I over came this issue with a monitor that could be connected to all the GPU's outputs. I think I needed to make the dGPU as the main one. But there seems to be a fight between Igpu a dGpu in who is in control. I can no longer boot into graphical unraid only the cli. then Use the web login.

 

But I do not remember exactly and my machine is in another building or I would look.

Thanks for your reply!  Prior to installing the GPU, I was running things headlessly and I could login into the GUI with no problem.  When Unraid failed to start after the install, I connected my monitor to see what was going on.  That's when I realized that the system was no longer moving beyond bios.

 

3 hours ago, JorgeB said:

That suggests the boot device is not correctly configured.

Thanks for your reply!  

 

Any thoughts on where I should start?  As mentioned above, everything was fine before the install.  Also, I did set the bios to use the integrated graphic as the default.  That worked for the monitor (I had to switch the HDMI cable to the motherboard port) but the system still goes straight to bios.

Edited March 30, 20251 yr by rockbox948

Make sure the USB is still the first boot priority. 
 

you can also try a different USB port.

Is there a fast boot option in bios and or IGPU multi (view or something like that) There is a thread for WS W680-ACE IPMI with similar issues caused by the igpu and dgpu. This is where I searched because I have that motherboard. It was the fast boot that was the issue.

8 hours ago, grumpy said:

Is there a fast boot option in bios and or IGPU multi (view or something like that) There is a thread for WS W680-ACE IPMI with similar issues caused by the igpu and dgpu. This is where I searched because I have that motherboard. It was the fast boot that was the issue.

Thanks for the reply.  I double checked and fast boot was diabled.

 

10 hours ago, MowMdown said:

Make sure the USB is still the first boot priority. 
 

you can also try a different USB port.

Thanks for the reply.  The boot priority was correct but it seems that maybe the USB header on the board is faulty.  I removed the GPU and tried to reboot but the same issue persisted.  Then I moved the USB drive to a different port and the system booted.  I was able to access the GUI from my browser with no issues.   

 

However, I reinstalled the GPU and the system boots into Unraid but now I get timeout errors when trying to access the GUI from the browser.

Please post the diagnostics.
 

4 hours ago, JorgeB said:

Please post the diagnostics.
 

Here are the diagnostics.  Thanks!

diagnostics-20250331-0751.zip

Everything looks normal to me, you can boot with a different flash drive, using a stock install, no key needed, that will confirm if there's a config issue or an external problem.

On 3/31/2025 at 7:59 AM, JorgeB said:

Everything looks normal to me, you can boot with a different flash drive, using a stock install, no key needed, that will confirm if there's a config issue or an external problem.

Thanks for the suggestion.  I will try to do that this weekend and report back.

On 3/31/2025 at 7:59 AM, JorgeB said:

Everything looks normal to me, you can boot with a different flash drive, using a stock install, no key needed, that will confirm if there's a config issue or an external problem.

It looks like it is either a config issue or an issue with the original USB drive.  I did what you suggested and the system booted without issue.  Any thoughts on where I should start in trying to run this issue down?

You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool confirm it boots, if yes, restore the complete /config folder from the backup, if it stops working, do it again but just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.    

4 hours ago, JorgeB said:

You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool confirm it boots, if yes, restore the complete /config folder from the backup, if it stops working, do it again but just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.    

Thanks, I will get to work on this!