Boot the recovery image - FAS8200
Boot the ONTAP recovery image from the USB drive on a FAS8200 system to restore the boot media. This procedure includes booting from the USB flash drive, restoring the file system, verifying environmental variables, and returning the controller to normal operation, with specific steps that vary depending on whether the system is in a two-node MetroCluster configuration.
The FAS8200 system supports only manual boot media recovery procedures. Automated boot media recovery is not supported.
Option 1: Most systems
: You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental variables.
This procedure applies to systems that are not in a two-node MetroCluster configuration.
-
From the LOADER prompt, boot the recovery image from the USB flash drive:
boot_recoveryThe image is downloaded from the USB flash drive.
-
When prompted, either enter the name of the image or accept the default image displayed inside the brackets on your screen.
-
Restore the var file system:
If your system has… Then… A network connection
-
Press
ywhen prompted to restore the backup configuration. -
Set the healthy controller to advanced privilege level:
set -privilege advanced -
Run the restore backup command:
system node restore-backup -node local -target-address impaired_node_IP_address -
Return the controller to admin level:
set -privilege admin -
Press
ywhen prompted to use the restored configuration. -
Press
ywhen prompted to reboot the controller.
No network connection
-
Press
nwhen prompted to restore the backup configuration. -
Reboot the system when prompted by the system.
-
Select the Update flash from backup config (sync flash) option from the displayed menu.
If you are prompted to continue with the update, press
y.
-
-
Ensure that the environmental variables are set as expected:
-
Take the controller to the LOADER prompt.
-
Check the environment variable settings with the
printenvcommand. -
If an environment variable is not set as expected, modify it with the
setenv environment-variable-name changed-valuecommand. -
Save your changes using the
savenvcommand.
-
-
The next depends on your system configuration:
-
If your system has onboard keymanager, NSE or NVE configured, go to Restore OKM, NSE, and NVE as needed
-
If your system does not have onboard keymanager, NSE or NVE configured, complete the steps in this section.
-
-
From the LOADER prompt, enter the
boot_ontapcommand.If you see… Then… The login prompt
Go to the next Step.
Waiting for giveback…
-
Log into the partner controller.
-
Confirm the target controller is ready for giveback with the
storage failover showcommand.
-
-
Connect the console cable to the partner controller.
-
Give back the controller using the
storage failover giveback -fromnode localcommand. -
At the cluster prompt, check the logical interfaces with the
net int -is-home falsecommand.If any interfaces are listed as "false", revert those interfaces back to their home port using the
net int revertcommand. -
Move the console cable to the repaired controller and run the
version -vcommand to check the ONTAP versions. -
Restore automatic giveback if you disabled it by using the
storage failover modify -node local -auto-giveback truecommand.
Option 2: Controller is in a two-node MetroCluster
You must boot the ONTAP image from the USB drive and verify the environmental variables.
This procedure applies to systems in a two-node MetroCluster configuration.
-
From the LOADER prompt, boot the recovery image from the USB flash drive:
boot_recoveryThe image is downloaded from the USB flash drive.
-
When prompted, either enter the name of the image or accept the default image displayed inside the brackets on your screen.
-
After the image is installed, start the restoration process:
-
Press
nwhen prompted to restore the backup configuration. -
Press
ywhen prompted to reboot to start using the newly installed software.You should be prepared to interrupt the boot process when prompted.
-
-
As the system boots, press
Ctrl-Cafter you see thePress Ctrl-C for Boot Menumessage., and when the Boot Menu is displayed select option 6. -
Verify that the environmental variables are set as expected.
-
Take the node to the LOADER prompt.
-
Check the environment variable settings with the
printenvcommand. -
If an environment variable is not set as expected, modify it with the
setenv environment-variable-name changed-valuecommand. -
Save your changes using the
savenvcommand. -
Reboot the node.
-