So, I took my second Proxmox node out of the cluster by running

pvecm expected 1
pvecm delnode proxmox2

Then, took another look at my Proxmox2 node, reseated everything a third time, and now it recognized the boot drive.

So now, I have a standalone node running just fine and a second node looking for a cluster.

I ran the following commands on proxmox2:

systemctl stop pve-cluster corosync
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster


I seleted the /etc/corosync directory and /etc/pve/corosync.conf from the first server and was able to make a new cluster. So, now I have my old BBS VM available, but I'm happy with it on Windows 11 for now.

I'll be playing with Windows 10 IOT LTSC to see if that's a better low-profile OS than Windows 11.

Proxmox wants 3 for a quorum, I'm considering throwing Proxmox on a rPi to give me 3 nodes.
--- SBBSecho 3.29-Win32
* Origin: realitycheckBBS.org -- information is power. (1337:3/178)

Proxmox wants 3 for a quorum, I'm considering throwing Proxmox on a rPi
to give me 3 nodes.

It's been a while since I did this, but back when I did you didn't need Proxmox on the rPi, you could just install a daemon that would do the trick.

A quick Google suggests QDevice is the thing to search for.

This was back when I had two R620's running Proxmox here at home. The power bill put an end to that and I ended up moving those two servers to a local datacentre (a previous employer let me use some unused space in their rack) and added a 3rd, so I had a quorum anyway. These days I have just a single Proxmox server back at home, so don't currently have a need...

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: TassieBob BBS, Hobart, Tasmania (1337:2/106)