Skip to content

Clearing out a node

Wiping a node

If the node(s) are from an existing HyperCloud or HyperDrive environment, it is necessary to wipe the data prior to reuse.

If the device was part of a Bcache SSD/HDD cache set then this should be stopped first:

for dev in /sys/block/bcache*/bcache/stop; do echo 1 > ${dev}; done

Run the following command to wipe file system signatures:

wipefs -a -f /dev/XXXX

XXXX is the disk that will have its file system wiped.

Nuking a node

If the node was part of a previous cluster build, HyperCloud may refuse to wipe an existing data disk and ingest it into the cluster. If you are unable to boot another OS to wipe the data disk(s), then you can create a cluster control fact to nuke the disks.

Run the following command:

touch /var/run/cluster-control/facts/clusternode_NODENAME_nuke_disks

Replace NODENAME with the HyperCloud hostname of the machine in question. This will create a file in the /cluster-control/facts/ directory which will be seen by HyperCloud's routine file scans and trigger the system to demolish the named node.