Procedure for replacing the boot drive on Cisco platforms running Qumulo Core.
The boot drive holds Qumulo Core’s operating system. Replacing it requires a different procedure than replacing data drives — the new boot drive must be initialized before the node rejoins the cluster.
After you replace the boot drive, you must initialize the replacement boot drive by using the Qumulo Core Installer and then rebuild the replacement boot drive by using a script on the node in your cluster.
Step 1: Initialize the Replacement Boot Drive
To get the correct version of the Qumulo Core Installer for the node in your cluster, contact the Qumulo Care Team
-
Power on your node, enter the boot menu, and select your USB drive.
The Qumulo Core Installer begins to run automatically.
-
When prompted, take the following steps:
-
Select
[x] Perform maintenance. -
Select
[1] Boot drive resetand then follow the prompts.
The Qumulo Core Installer initializes the boot drive.
-
-
When the process is complete, the node is powered down automatically.
Step 2: Rebuild the Replacement Boot Drive
-
Power on your node and log in to the node by using the
qqCLI. -
To get
rootprivileges, run thesudo qshcommand. -
To stop the Qumulo Networking Services, run the
service qumulo-networking stopcommand. -
To configure the IP address for the node, run the
ip addr addcommand and specify the node’s IP address. For example:ip addr add 203.0.113.0/CDR dev bond0 -
Ensure that the node can ping other nodes in the cluster.
-
Run the
rebuild_boot_drive.pyscript and specify the IP address of another node in the cluster, the ID of the node whose boot drive has been replaced, and the password of the administrative account of the cluster. For example:Note
If your password includes special characters such as the parenthesis (() or the asterisk (*), use the backslash (\) to escape these characters./opt/qumulo/rebuild_boot_drive.py \ --address 203.0.113.1 \ --node-id 2 \ --username admin \ --password my\(Special\*PasswordFollow the prompts.
-
When the process is complete, reboot the node.