sup3rgh0st

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 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!

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!

Update on this, I found someone with the same motherboard and cpu combo and they're able to boot without issue. It looks like whatever the problem is, is an issue with Arch. The USB boot medium crashes there as well, this time hanging on the line "triggering uevents".

I was able to boot into Debian and Windows without issue, looks to be an issue with Unraid then which is a shame. I don't suppose there's a way to get and save better logs on boot to see what's going wrong?

Board issue as in something is physically wrong with my board or do you think there's a compatibility issue?

Hey Jorge, thanks for the suggestion. Resetting the BIOS to defaults and/or booting v6.11.5 resulted in the same stall. As did turning off FastBoot on v6.11.5. Anything else you can think I can try?

Is there a way I can enable more verbose logging to better diagnose what it's getting hung up on?

I'm currently in the process of trying to boot into Unraid on a spare PC, however it consistently freezes in that same spot in the boot process. The log on screen will get to "Btrfs loaded, crc32c=crc32c-generic, zoned=no, fseverity=no" followed by "pstore: Using crash dump compression: deflate" as pictured here: https://i.imgur.com/paGq45R.jpg Somewhat rarely after stalling it will give me a crash dump/stack trace, however it usually just stalls. Dump pictured here: https://i.imgur.com/7iO6QQz.jpg At this point I've stripped out pretty much everything from the PC, it's just the mobo, ram, and USB stick. No harddrives, gpu, etc.. I updated the bios, toggled pretty much every option available to me, Fastboot, CSM, Secure Boot, ran and passed memtest overnight. Windows boots just fine, the USB I'm booting from works on a different PC, tried two different USB sticks... I'm running out of ideas, any thoughts on what I can try? Here's the boot settings in my bios. Their current settings were set after resetting the bios to their defaults, as mentioned above I've trying turning things like fastboot off: https://imgur.com/a/g5FoFnR Using the latest version of Unraid at time of creating the stick: 6.12.6 Motherboard is an Asus PRIME Z270-A, Intel i7-7700K cpu

I'm also having issues setting up a 1.18.2 Forge server. I can't seem to find the guide that Maximus is referring to either. It appears that the latest versions of Forge use Java 17/18, and modern server setup installs Forge as a library in the server files. Starting the server requires a lengthy command that appends multiple files worth of arguments together. Any chance that we can get support for this in the future? Or is that outside the scope of this Docker container? It seems like a potential fix would be allowing to specify custom Java arguments in the template. For reference, I'm trying to setup a Direwolf20 1.18.2 (1.0.0) server using Forge 40.1.19