[Self-SOLVED] Stuck on "Loading initial ramdisk"

[quaint dove]

Hello, I am trying to boot into my arch linux install but get stuck on "Loading initial ramdisk". Recently I had a power outage that my desktop did not enjoy, and since then I've had my KDE window manager (or something sounding like that) crash a few times unexpectedly. Upon crashing the second time, I decided to shut off my computer for the night and now when booting into arch, it is stuck on "Loading initial ramdisk".

For my storage layout, I have a hardware RAID for a windows install, a hardware RAID as an extra drive for windows, then an NVME drive for arch linux and my grub bootloader. My arch install is encrypted with LKUS(2, possibly- using archinstall this time). I also have an arch install USB ready to help.

I have modified my grub to have a custom theme and include my Windows install, but I haven't had issues with that for months. I also believe with 95% certainty that the quiet flag isn't being used by grub for booting into arch, so I should be seeing something. I am also able to boot into Windows with grub so I am unsure what to do.

From some googling and research, it would seem that I may need to reinstall grub, but due to being able to boot into Windows, then I would assume it is an issue with arch and the "initial ramdisk" thing and not grub? Would it be a good idea to boot into my USB, and re-create my initramfs? I noticed that here.

I am unsure, so I would like some assistance please!

"CPU2 failed to report alive state" is the first thing I see when booting into the install USB.
Concerning in my non-expert opinion...

[quaint dove]

Rebooting again, I see that in grub that I have an "Advanced options for Arch Linux" folder with an "Arch Linux, with Linux Linux (fallback initramfs)" option that has successfully booted my arch linux install. From here, what would you recommend I do? I'll try updating any packages with yay and wait until some help.
Makes me think that the "initramfs" is broken and that is needs to be recreated, so I will do some research on how to do that but I'll still wait for help in case there are complications due to my lack of experience or my LKUS encryption, etc.

I can also confirm that there are no parameters like -quiet in grub that would hide any messages.

While running yay to update all my packages, I see there are packages like core/linux so... the linux kernel and modules I assume? Must have just been updated since I updated around 24 hours ago. I hope this will fix my issue?
I also see extra/nvidia-open which is nice since I often seem to have issues with my nvida gpu, but unrelated.

Looking at the last few messages from running yay, I see lines saying, Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img' and the same thing for the initramfs-linux-fallback.img that I used to boot this time.
In a bit, I will reboot and attempt to boot into my arch linux install normally. I can either see this working fine, or still being broken and now my fallback is touched, and possibly broken too... we will see.

Well, I can't tell if this is a curse or a good thing, but it seems like with the majority of issues, I just need time 🙃.
I spend some time doing things, can't figure it out, post for help somewhere, no reply so I keep working on it, and boom, done!
So, I have indeed been able to boot into my arch linux install normally woo hoo!

For anyone who stumbles on this thread, I would like to know how I can figure out why this has happened, and what I could do to fix it in future if there wasn't an update to the linux kernel and modules. I would assume re-creating the initramfs? Funny how there was an update that did so for me just as it broke.

As for those stumbling on this looking for help with the same issue, try booting into your initramfs fallback! If that works, you could try updating your packages in-case there is an update to the linux kernel, or you can then re-create your initramfs or something else? It seems like a good first place to start imo.
If you are not able to boot into either, then it may be your grub install broken? No idea, but good luck!

[Self-SOLVED] Stuck on "Loading initial ramdisk"