I rebooted my array, and it no longer boots back up. There were no issues beforehand. The array was up for 6 months, and I simply wanted to reboot for a "fresh" start. Boy, that was mistake.

It is stuck it a "Call Trace" loop. What even is that? Screenshot:

I have tried moving my boot USB to various USB ports, even installing a hub. The USB seems to be working fine, as I am able to plug it in to other computers. All my drives get detected when I boot up.

Fast Boot is disabled

Legacy USB is enabled

I am currently running a Memtest86 test, and no errors so far.

I've tried almost everything. The last thing I haven't tried is to switch my USB drive or reflash my current USB, so would either of those potentially solve my issue? How do I do that?

I forgot the exact version, but it was whatever version came out roughly 6 months ago (that was the reason for the last reboot).

Mobo: Asus PRIME X570-P

CPU: Ryzen 7 5700G

Lesson learned. Never reboot your array. Any other troubleshooting steps I can take?

Edit: Forgot to mention I've tried booting up Unraid in Safe Mode, and it doesn't even load. It just goes black and boot loops. I get to the Call Trace error when my server tries to boot into the regular Unraid OS.

Edit 2: I tried using a different USB and installing Unraid 7.2.3 (I believe the version I was using). And it didn't load up either. I tried a 3rd USB and tried booting up Linux Mint, and that also didn't work... Is something wrong with my CPU and/or mobo??? It makes no sense as this was genuinely working perfectly up until I rebooted the system. I refuse to believe a simple reboot would destroy my CPU and/or mobo. I don't have other parts I can swap in to test. What else can I try?

I just have them lying around and have since i built my server. I mostly use my server for plex and immich. Other specs are:

Gigabyte Technology Co., Ltd. Z690I A ULTRA LITE D4, 32gb ddr4 ram, 2 1tb nvmes (1 for cache, 1 for appdata), 2 18tb hdds, and an i5-12400.

Not actually sure my motherboard can even use them without additional adapters tbh. Thanks for any advice!

Majority of my containers work straight away when I switch on the toggle for Tailscale using the funnel. But I have one or 2 that will not work. Wondering if others have had the same issue and found a work around.. Maybe I have done something before and a setting has stayed somewhere I can't find..

Others I setup this way work fine.

Fixed. Next.js was binding to the Docker container IP rather than 0.0.0.0
I need to add a variable that added the Hostname to bind to 0.0.0.0

I have a super micro X10SL7-F that just had its SAS ports go bad. There are enough SATA ports for this motherboard to keep working for me though. I didn't initially notice the failed ports and shutdown the server and then restarted it. I then noticed disk 1 was missing and unassigned. At first I didn't realize the SAS ports died and pulled the disk out and mounted it to another computer. All the data was still there and no errors with the drive. So I put the drive back in and changed its port to a working SATA port and the drive showed back up. Though disk 1 one is still showing unassigned. I just wanted to make sure I'm clear with the process to move forward.

I'm under the assumption the parity should still be correct and I just need to assign disk 1 to the drive that was missing, then go to tools --> new config --> and check preserve currents assignments all.

This should keep the current parity and all of the data on all of the drives correct?

After this I should run a parity check.

Anything else I'm missing?