Skip to main content
NetApp Stage KB

Node does not boot due to disk reservation conflict during MetroCluster IP setup

Views:
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster IP installation
  • ONTAP 9.8
  • Node reboot 

Issue

  • After a reboot during MetroCluster IP installation one of the nodes in the HA pair doesn't boot due to: 

    Reservation conflict found on this node's disks!
  • HA partner is Waiting for partner node to recover: 
    Cluster::> storage failover show
      (storage failover show)
                                  Takeover          
    Node           Partner        Possible State Description  
    -------------- -------------- -------- -------------------------------------
     NodeA_1           NodeA_2             false    Connected to LK2ClusterNetapp-04,
                                            Takeover is not possible: Waiting
                                           for partner node to recover, Disk
                                           inventory not exchanged
    NodeA_2             NodeA_1                 -        Waiting for reservations to clear
  • Event log from the up node is showing release reservation messages: 
    [sanown_io: diskown.releasingMismatchedReservation:notice]: reservation process is releasing reservation on disk 

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.
2e06e974-972a-4a13-a895-503af2a92a2a