I've had my system up and running for several months now.  I pre-emptively shut down my server due to some storms in the area.  When I turned the system back on, I'm greeted by Unraid not finishing the boot process.  The process is stopping at

amdgpu: Topology: Add CPU node

 

The same issue occurs when regardless of which boot option I select.  I've recreated the boot drive both from My Servers backup and stock and the issue occurs.  Tells me it's probably a hardware issue.  Any ideas on what the boot process is hanging on?

Try booting  using a new flash drive with a stock Unraid install, no key needed, just to see if it boots and the problem is config related.

4 hours ago, JorgeB said:

Try booting  using a new flash drive with a stock Unraid install, no key needed, just to see if it boots and the problem is config related.

 

Same issue.  I don't suppose there is a debug mode/log file that will tell me what the boot process is attempting to check before checking it.

Try blacklisting the GPU, see here:

https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel

35 minutes ago, JorgeB said:

Try blacklisting the GPU, see here:

https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel

 

So, TrueNAS can experience the same issue and their forums had a suggestion; add

nomodeset 

to the SYSLINUX.cfg.  I tried that and I'm able to get past this issue.  The TrueNAS folks state that Linux "seems" to have issues with multiple video cards.  I have an AMD processor with integrated GPU and an Intel A770 running on a ASRock X570 Taichi.  There is no way in the BIOS to turn off the AMD GPU-- you can only set the default device and whether you want hybridgraphics.  The only thing I can think of is there is a bug/change in the AGESA Combo V2 PI 1.2.0.8 microcode.  I updated the BIOS a few weeks ago and have rebooted several times without issue, but that's the only recent change and not sure why this issue popped up with this restart.