Skip to main content
NetApp Stage KB

Metrocluster switchback operation fails due to disk failure

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

 

 

Applies to

  • FAS/AFF
  • ONTAP 9
  • MetroCluster FC Switchback failing

Issue

  • The following event is generated due to switchback failure:

[Node-01: notifyd: callhome.mcc.switchback.failed:EMERGENCY]: Call home for METROCLUSTER SWITCHBACK FAILED

  • MetroCluster switchback fails with the following error:
Cluster-1 (manual recovery required): Some disks were left behind during switchback. They are listed along with a reason for failure: 4.27.1 (not responding)
If any of these disks are failed, replace them. Otherwise use the "metrocluster switchback" command again to return the disks to their original owner. Use the "storage disk show -dr-home-id !- -fields dr-home, container-type, aggregate" command for more details on the status of the left-behind disks.
  • ONTAP reports that the disk is not responding:

[cluster-101: config_thread: raid.config.filesystem.disk.not.responding:notice]: File system Disk /aggr1_data/plex1/rg1/CL008:6.126L501 Shelf 27 Bay 1 [NETAPP   X342_SSKBE1T2A10 NA02] S/N [WFKXXXXX] UID [5000C500:D1E41057:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] is not responding.
[cluster-101: config_thread: callhome.fdsk.noio:error]: Call home for FILESYSTEM DISK NOT RESPONDING

diskown.errorReadingOwnership:notice]: error 46 (disk condition triggered maintenance testing) while reading ownership on
disk FC-UTOR-RZ-02:6.126L507 (S/N PEGD1TGX)

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.