Initial commit

docs/06-troubleshooting.md

@@ -0,0 +1,39 @@
+# 06 - Troubleshooting
+
+Common interventions for pipeline failures or hardware reuse.
+
+## LVM Provisioning Failures (Dirty Disks)
+If Ansible halts at the LVM Volume Group creation phase, the target block device likely retains partition data. Ensure you are targeting the correct device and wipe the signatures manually:
+
+```bash
+# Execute on the specific Proxmox node
+wipefs -a /dev/sdX
+```
+Rerun the playbook after clearing the disk.
+
+## Corosync Quorum Loss
+If execution hangs on `pvecm status` or clustering commands, Corosync has lost quorum. In a 3-node cluster, 2 nodes must be online. To force a single active node to regain quorum and unblock operations (for recovery only):
+
+```bash
+pvecm expected 1
+```
+
+## Linstor HA VIP Unreachable
+If the controller does not initialize, verify the promoter plugin state:
+```bash
+systemctl status drbd-reactor
+journalctl -u drbd-reactor -n 50
+```
+Verify switch layer allows IP spoofing / MAC address floating for the defined `ha_vip`.
+
+## Complete Cluster Reset
+To obliterate Corosync configuration and reset the node to a standalone state:
+```bash
+systemctl stop pve-cluster
+pmxcfs -l
+rm /etc/pve/corosync.conf
+rm -rf /etc/corosync/*
+killall pmxcfs
+systemctl start pve-cluster
+```
+*Note: If DRBD configurations are active, an OS reinstall is significantly faster and safer than manual DRBD block device teardown.*