🚀 Proxmox VE 9 – How to Remove Cluster Group (Step-by-Step)

In some scenarios, you may need to remove a Proxmox cluster configuration completely, especially when:

• ❌ A node failed permanently

• ❌ The cluster was misconfigured

• ❌ You are rebuilding the lab environment

• ❌ Corosync cluster communication is broken

• ❌ You want to convert a clustered node back to standalone

Improper cluster removal can cause:

• Quorum errors

• Locked configuration files

• Inconsistent node states

• Cluster services failing to start

In this tutorial, you will learn how to safely remove a cluster group in Proxmox VE 9, delete a faulty node, and clean the cluster configuration step-by-step.

⚠️ Important: Follow each step carefully and in the correct order.

🎯 When Should You Remove a Cluster?

Cluster removal is necessary if:

• A node like pve02 is permanently offline

• You cannot restore quorum

• Corosync configuration is corrupted

• You want to break the cluster and run standalone

Before proceeding, ensure:

• All virtual machines are stopped

• You understand this action is irreversible

• Backups are available if required

🛑 Step 1: Shutdown All Running VMs

Before modifying cluster configuration, stop all running virtual machines to avoid data corruption.

Ensure no VM or container is running.

🗑 Step 2: Delete the Faulty Node (Not Used, e.g., pve02)

If the node pve02 is permanently offline or no longer used, remove it from the cluster.

First, force quorum expectation to 1:

Then delete the node:

This removes the failed node from the cluster membership list.

Verify cluster status if needed using:

🧹 Step 3: Proceed to Remove Cluster Configuration

Now we will stop cluster services and clean cluster-related configuration files.

Stop cluster services:

Start pmxcfs in local mode:

Remove Corosync configuration:

Remove Corosync directory:

Remove cluster node directory:

Kill pmxcfs process:

Restart cluster service:

At this stage, the cluster configuration should be removed and the node converted back to standalone mode.

🔄 Step 4: Reboot Host

Finally, reboot the Proxmox host to ensure all services restart cleanly:

Reboot host proxmox

After reboot, verify:

• No cluster information appears

• pvecm status shows no cluster

• Web GUI loads normally

🧠 What Happens Internally?

When removing a cluster:

• Corosync communication is stopped

• Cluster filesystem (pmxcfs) is reset

• Node membership is cleared

• Cluster configuration files are deleted

Proxmox will now operate as a standalone node.

⚠️ Common Mistakes to Avoid

❌ Forgetting to stop VMs
❌ Removing corosync.conf while services are still running
❌ Skipping quorum adjustment (pvecm expected 1)
❌ Performing this in a healthy production cluster

Always ensure the node is truly intended to be removed.

🔐 Best Practices Before Cluster Removal

✔️ Backup important VMs
✔️ Document current cluster topology
✔️ Confirm node is permanently offline
✔️ Ensure no HA resources depend on the node
✔️ Perform during maintenance window

If you are working in production, evaluate whether repairing quorum is safer than removing the cluster.

🏗 Typical Use Cases

This procedure is commonly used when:

• Rebuilding a homelab cluster

• Recovering from 2-node quorum failure

• Migrating to a new cluster design

• Cleaning corrupted cluster metadata

It is especially useful in lab environments where nodes are frequently rebuilt.

🎯 Conclusion

Removing a cluster group in Proxmox VE 9 requires careful execution to avoid configuration corruption.

By following this step-by-step guide, you have:

• Removed a faulty node

• Cleaned cluster configuration

• Stopped Corosync properly

• Converted the node back to standalone mode

Cluster management is a critical skill for any virtualization administrator, and understanding both how to create and remove clusters is essential.