How to use the boot_recovery LOADER command for recovery of a boot
device
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_use_the_boot_recovery_LOADER_com…
Updated: Thu, 23 Jan 2025 12:45:02 GMT
Applies to
• ONTAP 9
• AFF Models
• FAS Models
Description
Typically a boot device replacement will follow the procedure outlined in the published AFF and FAS System
Documentation Center. However, at times there may be a need to recover the existing boot device within the
system.
'NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations
provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations
provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
Procedure
Prerequisites
• Determine if the AFF or FAS model has external USB support
• Confirm the boot device is recognized at LOADER
• Follow the process to prepare a USB drive to use in the ONTAP boot_recovery procedure
• Download the ONTAP 9 image desired to install
• For the models listed below, download the Service Image (BIOS)
◦ AFF A800, AFF A700s, AFF A400, AFF A320, AFF A250
◦ FAS8700, FAS8300, FAS500f
Process
1. Copy the downloaded ONTAP image directly onto the root directory of the USB flash drive. Make note of
the full file name as it will be required later.
2. If the model required the download of the Service Image (BIOS), extract the contents of the Service Image
and copy the EFI folder directly to the root directory of the USB flash drive.
3. Insert the USB flash drive into the controller.
4. Perform the following action based upon the current state of the controller.
State Action
Controller is not inserted into chassis Insert the controller into the chassis to allow it to boot
The sytem is at the LOADER prompt Issue the command "bye" to power cycle the controller
The controller is not responsive Perform a system power cycle
5. For systems requiring the EFI folder on the EFI boot device, the system will boot directly to LOADER. For
all other controller models, press CTRL-C when prompted in order to return to the LOADER prompt.
Starting AUTOBOOT press Ctrl-C to abort...
6. Perform the folowing action based upon the configuration.
Configuration Action
Controller is a platform that has the e0S interface No action is needed
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
Other controller platforms in preperation to use the restore-backup Follow the procedure Configure
command network at LOADER prompt
Preparation to use the procedure to restore from option 6 when no
No action is needed
network is available (not preferred)
7. Enter the boot_recovery command specifying the exact name of the ONTAP image copied to the USB flash
drive (do not rename the file). For instance:
LOADER-A> boot_recovery 97P11_q_image.tgz
8. The system will continue to boot. When prompted enter the name of the package to install. It may be the
same or different than the image booted from, but it must be located on the USB flash drive.
Enter recovery package name (Ctrl-C to abort) [97P11_q_image.tgz]:
9. When ONTAP is finished being extracted to the boot device, it will prompt to restore the backup
configuration.
10. At this time, remove the USB flash drive so the controller can boot into ONTAP after the restore process.
11. Perform the following action based upon the previous configuration.
Configuration Action
a. Press y when prompted to restore the backup configuration.
b. Set the healthy controller to advanced privilege level: set
-privilege advanced
c. Run the restore backup command: system node restore-
backup -node local -target-
address impaired_node_IP_address(this may take a couple
Controller is a platform that
has the e0S interface or of minutes)
the Configure network at
LOADER prompt was followed d. Return the controller to admin level: set -privilege admin
e. Press y when prompted to use the restored configuration.
f. Press y when prompted to reboot the controller.
g. If using Onboard Key Manager (OKM) the boot process must be
stopped with CTRL-C during boot in order to return to the boot
menu. Perform the How to restore onboard key manager server
configuration from the ONTAP boot menu procedure.
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3
No network is available Follow the procedure to restore from option 6 (not preferred)
Additional Information
• How to use the boot_recovery LOADER command for installing ONTAP for initial setup of a system
• EFI folder missing from Service Image download file used for boot device recovery for FAS and AFF models
• FAS and AFF boot device Resolution Guide
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 4
