Skip to main content
NetApp Knowledge Base

Node unjoin fails in ONTAP with 'Node is SFO and Node still has volumes'

Last Updated:

Applies to

  • FAS8020
  • ONTAP 9.1P3


  • Failure when trying to unjoin a node while in takeover mode.
  • Node 01 had previously failed and was taken over by node 02. 
  • The customer was able to unjoin node 01 without issue.
  • Executing cluster unjoin -node <node_name>  on node 02 would not unjoin due to:
Cluster unjoin only works for nodes not in a failover configuration. Node is SFO enabled with partner node .
Node has 2 volumes. Please either move or delete them from the node before unjoining.


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.


  • Was this article helpful?