Proxmox boot completely destroyed(?) after creating a cluster. Fixing the boot partition?

[probablyoxy]

I've had my Proxmox server set up for months now, it runs on an R5 3600 with 64gb 2933mhz ram on a B450M Gaming. It runs my Truenas array with a passthroughed HBA, and a Pterodactyl server on Ubuntu. I had just finished installing Proxmox on my second computer, and created a cluster through the web ui in Datacenter/Cluster. I try to join the two and it says An error occurred on the cluster node: cluster not ready - no quorum? TASK ERROR: Cluster join aborted! on the joining party and the UI said Cannot initialize CMAP service on the main/creator. I found another post on this forum that had someone add the other nodes in the hosts file. I try to use nano on /etc/hosts and I get cannot execute binary file I have no idea what that means and I tried to look it up but found absolutely nothing related to anything I did, and assumed Proxmox was just getting finnicky after creating the cluster for whatever internal reason. So I restart the main one I created it on thinking that would be a good thing to try, and now it doesn't boot. Upon inserting a graphics card (into the NOT passthroughed slot!) I see it "boot" into a black screen. Nothing ever shows up. Upon pressing the power button to shut it back down, it immediately stops spinning the fans which tells me that it really isn't booting anything at all. Caps lock doesn't even blink on the keyboard. I tried disabling secure boot and then it just dumps a bunch of crap on the screen saying LoadImage failed in Boot Option Restoration. I also tried disabling virtualization but it didn't change anything.

Fast forward, midnight, I'm here in the debug installer off of the USB, and everything I've seen actually lead me anywhere tells me to do this: (not going to change all the examples, but the drive is nvme0n1 and the efi should be the 1 gig nvme0n1p2)

vgscan
vgchange -ay
mkdir /media/RESCUE
mount /dev/pve/root /media/RESCUE/
mount -o rbind /proc /media/RESCUE/proc
mount -o rbind /sys /media/RESCUE/sys
mount -o rbind /dev /media/RESCUE/dev
mount -o rbind /run /media/RESCUE/run
proxmox-boot-tool format /dev/sda2
proxmox-boot-tool init /dev/sda2
proxmox-boot-tool refresh

And then proxmox-boot-tool init /dev/sda2 just does not work :/
It returns

Re-executing [...] in new privatre mount namespace...
UUID=[...] SIZE [...] FSTYPE [...] etc etc.
Mounting /dev/nvme0n1p2 on /var/tmp/espmounts/877D-AC00
Installing systend-boot..
E: bootctl is not available - make sure systemd-boot is installed

How in the world is the recovery boot not going to include everything necessary to function as a recovery? This is genuinely bewildering to me. I feel like every single time I try to do anything with my server there's some unforeseen consequences like I'm trying to get the Combine off Earth. I still have no idea what even happened in the first place, literally the only thing I did was press create cluster. This is actually unreal.
Also, why am I the only one that has this problem?? I haven't seen a single one of the sources for those commands have anything like this. Are those commands just 20 years old, or am I just cursed?

Fast forward again. It's 3:36 AM. I'm so tired.
Using the official documents (and yes of course I went to the official docs first, I'm not that bad at this. It just didn't work, like it isn't now, so I moved on.) I make it all the way through until Chroot.
chroot: failed to run command '/bin/sh': No such file or directory
I'm just at a loss lol. I am so confused.. what happened to my server lol. I just want to apologize right now if I seem like a jerk, this stuff just makes me so annoyed beyond belief, like I didn't even do anything.

Here are pictures of what it shows when I try to boot into Proxmox. "Load Error" is with secure boot off, and "Access Denied" is with secure boot on.


I guess the only good thing about this is I don't have to worry about my data, as all my servers and storage other than VMs (which will definitely change soon) are on dedicated drives. I also used Clonezilla earlier to backup the drive in case anything gets even worse. I really wanted to just fix this as I thought it would be easier since I wouldn't have to reinstall TrueNAS and Pterodactyl... which still sounds more annoying but maybe would have taken less time... BUT I'm about to rebuild my server anyway so if I'm going to reinstall it will be then.

It's just past 4:20 now so that's what I'm going to do because I gotta relax lol. Thank you so much in advance to anyone that helps out! And please let me know if you need more info!!!

 

[probablyoxy]

Day,,, 3... I think. Spent all night talking to a friend about this. Trying things and nothing working. Just spent the last 3 hours installing Proxmox on a HORRIBLE usb drive. (It was my only choice!!!) Two hours to install, and the last hour went to cloning partitions and trying to get this to work.
I cloned both the 1GB (512MB on the USB) and the 1024K~ efi partition. Now, instead of getting Load Error and Access Denied, I make it all the way to grub!! But only to grub. Just the terminal for grub. That seems great! now I really do have a grub problem and this official method might work!

Love is in the air?
WRONG!
chroot: failed to run command '/bin/sh': No such file or directory

If nobody responds to this soon () I guess I'm just going to have to reinstall... My new motherboard just came in, so I might try to tough it out until I can get all the new parts but being without my NAS is kind of annoying. Plus all my servers are down.

Yes, a collect call for Mrs. Floyd from Mr. Floyd, will you accept the charge? From the United States?
Oh, he hung up.