This is a continuation of a previous thread of mine posted over 6 months ago here: 

I was unable to boot unto Unraid, tried multiple versions of Unraid, Multiple USB sticks, BIOs settings, removing hardware from the system, etc.,.
Through trial and error I learned that I am able to boot into Unraid and access the WebUI if I limit the core count in the bios to 1 or 2. 3 or more leads to me getting stuck on boot on the message "clk: Disabling unused clocks" which as far as I can tell leads to some kind of CPU deadlock in the Arch Linux boot process(?). Has anyone seen anything like this before or have any ideas on what I can try? I tried reseating the CPU to no avail. 

Text transcribed from the photo of the boot log: https://pastebin.com/wbZnij5k
Image of the boot log: https://imgur.com/a/R0lcijw
With only two cores enabled, here is the log from the Unraid WebUI: https://pastebin.com/j3cC53zC

Thanks!

Edited July 20, 20241 yr by sup3rgh0st

I have the same thing happening to me right now, did you ever find a reason/fix for this?

I unfortunately never found a fix. The strongest lead I believe I had was that it was also an issue with other linux distros such as Arch Linux and Debian, so that broadens the search pool a bit for forums to search for people with similar issues. Let me know if you ever find a fix that's better than disabling cpu cores!

Ok

I think I may have found a workaround for this

• From another computer (if WebGUI is inaccessible):

  • Shutdown your Unraid server.

  • Remove the USB flash drive that contains the Unraid OS.

  • Insert the USB flash drive into another computer.

  • Open the USB flash drive and navigate to the /syslinux directory.

  • Open the syslinux.cfg file in a text editor.

1. Edit the syslinux.cfg file:

   • Locate the line that starts with append.

   • Add clk_ignore_unused as a boot parameter to this line. For example, if the line is currently append initrd=/bzroot, you would change it to append clk_ignore_unused initrd=/bzroot.

2. Save the changes and reboot:

   • Save the modified syslinux.cfg file.

   • Safely remove the USB flash drive from the computer.

   • Insert the USB flash drive back into your Unraid server.

   • Boot your Unraid server. 

On my first try, it got straight past the disabling clocks line. Now its stalled on a different line
"rc.udev: triggering udev events"

Can you try this and see if it works for you?

I tried this and as you say it stalls further down the boot process, this time on "usb 1-13: new high-speed USB device number 2 using xhci_hcd" but I believe this is a red herring. It will occasionally kernel panic instead with the following message "mce: CUPs not responding to MCE broadcast (may include false positives): 2,6" which aligns with the workarounds I found above; something wrong with the CPU or how its configured.
It didn't work for me, but you might have luck reseating your CPU.

I had already tried that.

I guess I'm gonna have to buy a new CPU to test :(

That's the only thing I didn't have a spare of lying around

Had a spare and tried motherboard/ram/ssd's/coolers and fans

Well, a friend had a spare cpu I could try.

replaced the CPU, put the original usb drive back in

Everything booted fine

straight in, no issues

So It is definitely a CPU issue. I just dont know what the issue is