Skip to main content
NetApp Knowledge Base

CONTAP-729114: FSx for ONTAP HA pair can get stuck in takeover/reboot loop after throughput scaling when takeover-with-halt overlaps with check-takeover

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Issue

  • In FSx for ONTAP (AWS), after a throughput scaling operation (instance type change) and a planned/negotiated takeover, if a takeover-with-halt occurs while check-takeover runs (often triggered by Upgrade Preparedness Check), the rebooting node may fail to complete boot/giveback and repeatedly halt/reboot.
  • Node01 is experiencing a boot loop due to a 'serial number not found' error:

ena1: <ENA adapter>SN(volxxx) does not match ephemeral nvram bootarg.vm.vnvram.sn=AWSxxx disk_ident(volxx mem 82e)
Root mount waiting for:SN(volxxx) does not match ephemeral nvram bootarg.vm.vnvram.sn=AWSxx disk_ident(volxx CAMena1: ENA Express tuning is enabled.
Ephemeral vNVRAM SN (AWSxxx) not found, clear bootarg.vm.vnvram.sn and reboot
SerialNumber(AWSxxx) matches ephemeral vNVRAM, using bootarg.vm.nvramdevice=/dev/nda8

  • HA remains degraded until manual recovery.

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.