Skip to main content
NetApp Knowledge Base

Controller takeover failed: takeover during raid failed

  1. Last updated
  2. Save as PDF
Views:
171
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9

Issue

  • Call home for RAIDTREE ASSIMILATION FAILED in EMS log:
Wed May 25 20:17:28 -0700 [n10: config_failed_disk: callhome.raidtree.assim:EMERGENCY]: Call home for RAIDTREE ASSIMILATION FAILED
  • Call home for CONTROLLER TAKEOVER FAILED in EMS log:
Wed May 25 20:37:20 -0700 [n9: cf_takeover: cf.fm.takeoverCommitted:debug]: Failover monitor: takeover committed
Wed May 25 20:37:21 -0700 [n10: cf_takeover: raid.fm.takeoverFail:alert]: RAID takeover failed: Partner label processing failed.
Wed May 25 20:37:21 -0700 [n9: cf_takeover: cf.rsrc.takeoverFail:alert]: Failover monitor: takeover during raid failed; takeover cancelled.
Wed May 25 20:37:21 -0700 [n9: cf_takeover: cf.fm.takeoverFailed:alert]: Failover monitor: takeover failed 'node failed to takeover one of partner's subsystems'
Wed May 25 20:37:21 -0700 [n9: cf_takeover: cf.nduIncomplete:info]: params: {'reason': 'TAKEOVER_FAILED', 'token': 'n9_03:32:14_2022:05:20', 'host': 'n10'}
Wed May 25 20:37:21 -0700 [n9: cf_giveback: callhome.sfo.takeover.failed:alert]: Call home for CONTROLLER TAKEOVER FAILED

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.