Server bricked after failed backup and cutting power to server

[bfish2]

I have had a Proxmox 8 server (called Proxmox) for about a year running Home Assistant and Pi-hole. All good. Recently I added a second (called Proxmox2) as a backup and to run a few other VMs/CTs. I created a cluster with Proxmox as primary and added Proxmox2 as a node. Yes, I have since learned I will need to fix my quorum issue. So far I have edited the quorum config file to simply require Proxmox to be the 1 vote in the quorum.

Today I was experimenting with an NFS share to backup VMs/CTs and somehow in the process I got my LXC (Id=202) on Proxmox2 locked. I pulled the plug on Proxmox2 hoping a restart would fix it, but it appears I made things exponentially worse. I have spent the last several hours scouring this forum and the internet and almost everything that I have been offered and tried, resulted in some inability to do due to the locking situation.

All I really want to do at this point is remove CT 202 on Proxmox2, and have it be back up and running as-was. So, basically 2 questions:

1. Any advice
2. My gut tells me if I shut down the cluster I might be able to have better luck managing this issue on the console of Proxmox2. BUT, I really can't lose access to Proxmox right now. Do I risk that if I shut down the cluster service?

Thanks in advance!

 

[Kingneutron]

If you have not done so yet, I recommend you invest in a license and open a ticket with Proxmox support. You don't seem to have the basics of clustering down yet, and this configuration probably should have been left as 2 standalone servers.

To get LXC 202 back up and running, you would probably need to restore it from backup onto node1- but I'm guessing you don't even have backups.