Skip to main content
NetApp Knowledge Base

Unable to boot from EFOS after switch reboot

  1. Last updated
  2. Save as PDF
Views:
159
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster IP
  • BES-53248 switches
  • EFOS 3.4.4.4

Issue

  • The switch cannot boot after being rebooted during the upgrade procedure
  • The EFOS image is not present (Boot0005)
Example:
ONIE:/ # efibootmgr
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0000,0005,0008,0009,0003,0004,000D,000E,0001,0002,0007,000C
Boot0000* ONIE: Open Network Install Environment
Boot0001  Hard Drive
Boot0002  UEFI: Built-in EFI Shell
Boot0003* UEFI: NIC1 IPv4 Intel(R) Ethernet Connection I354
Boot0004* UEFI: NIC1 IPv6 Intel(R) Ethernet Connection I354
Boot0006  Hard Drive
Boot0007  UEFI: Built-in EFI Shell
Boot0008* UEFI: NIC1 IPv4 Intel(R) Ethernet Connection I354
Boot0009* UEFI: NIC1 IPv6 Intel(R) Ethernet Connection I354
Boot000B  Hard Drive
Boot000C  UEFI: Built-in EFI Shell
Boot000D* UEFI: NIC1 IPv4 Intel(R) Ethernet Connection I354
Boot000E* UEFI: NIC1 IPv6 Intel(R) Ethernet Connection I354

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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 techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.