Tried to remove a node and go back to standalone /etc/pve/.members Input/output error

notromda

New Member
Mar 22, 2025
3
0
1
I removed one of two nodes in my cluster, reformatted for other purposes, and then tried to remove it from the web interface etc ... learned about quorum issues ... I had previously been able to get things running by bringing that down to 1 but in trying to remove the cluster entirely I'm pretty jammed up.

I think I started with instructions from https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node ...

and now some AI help has not gotten me any better.


I've
StepActionCommand/ExampleNotes
1Stop all Proxmox servicessystemctl stop pve-cluster pveproxy pvedaemonEnsure no processes interfere.
2Remove pmxcfs databaserm -f /var/lib/pve-cluster/config.dbForces a fresh start, preserving backups if any.
3Check for cluster remnantsls /etc/pve; ls /etc/corosync (previously removed these)Ensure no corosync.conf or cluster files remain.
4Test pmxcfs manuallypmxcfs -d -f then echo '{"nodename":"simon","id":1,"online":1,"ip":"192.168.1.4","version":0}' > /etc/pve/.members


And When I get there, It says -bash: /etc/pve/.members: Input/output error

Something with the FUSE filesystem isn't restoring correctly, the existing .members file seems a little less than expected:
{
"nodename": "simon",
"version": 0
}

and the web interface now won't come up and containers are not starting. Any ideas?
 
Last edited:
I guess the web interface comes up, iss ssl errors, but there are no nodes present in the display.
 
Thankfully I had a backup of my /var/log/pve-cluster/config.db ... I put that back, and then went back through the initial steps:

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

and from there I was able to see all lof my machines and restart them manually. I'm still a bit nervous about a reboot.