Skip to main content
NetApp Knowledge Base

E-Series replacement controller locks down due to auto synchronization failure

  1. Last updated
  2. Save as PDF
Views:
368
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

  • NetApp E-Series
  • E-Series platforms: E2800, E5700, E4000, EF300 and EF600
  • NetApp SANtricity 11.70.4 or newer

Issue

  • After replacing an E-Series controller, the replacement enters into a lock down state due to mismatched firmware. 
  • The native (alternate) controller reports auto code synchronization (ACS) failure due to missing bundle metadata file. Error "/bundle/metadata.active/metadata doesn't exist" can be seen in the journal logs:
    • The journal logs can be retrieved from the diag shell using this command: sudo journalctl --since "2 days ago"

Dec 07 02:36:59 eos-b downloadmgr[]: [tid=42688] Received request -
Dec 07 02:36:59 eos-b acsDaemon[]: Spawning /usr/bin/sendImageCert -b root.active raid.active msw.active iom.active
Dec 07 02:36:59 eos-b acsDaemon[]: [tid=34816] Spawning /usr/bin/sendImageCert -b root.active raid.active msw.active iom.active
Dec 07 02:36:59 eos-b downloadmgr[]: [tid=42688] Runnable for ServerMessagingProtocol exiting
Dec 07 02:36:59 eos-b sendImageCert[]: [tid=23616] set stdErrLogging 0
Dec 07 02:36:59 eos-b sendImageCert[]: [tid=23616] isZeroMD5Supported: response = {"status":"success","source":"DownloadMgr_A"}
Dec 07 02:36:59 eos-b sendImageCert[]: [tid=23616] /bundle/metadata.active/metadata doesn't exist

  • The replacement controller reports ACS no valid Dom0Image found in the eos controller shell or the console logs available in diag (/var/log/eos-_eos_console.log)

12/12/25-23:28:17 (acsDriveImage): NOTE:  ACS Dom0 evaluate existing extents
12/12/25-23:28:17 (acsDriveImage): WARN:  ACS findImages - 5 extents found for Dom0 Image
12/12/25-23:28:17 (acsDriveImage): WARN:  ACS no valid Dom0Image found
12/12/25-23:28:17 (acsDriveImage): NOTE:  ACS Dom0 getCompleteImages - 0  images to evaluate

  • The replacement controller reports repeadetly ICON MsgQ Error!!! in the eos controller shell or the console logs available in diag (/var/log/eos-_eos_console.log) until the issue is resolved.

12/18/25-19:43:42 (SasIniWkr0): WARN:  ICON MsgQ Error!!!
12/18/25-19:44:43 (SasIniWkr0): WARN:  ICON MsgQ Error!!!
12/18/25-19:45:44 (SasIniWkr0): WARN:  ICON MsgQ Error!!!
12/18/25-19:46:45 (SasIniWkr0): WARN:  ICON MsgQ Error!!!
12/18/25-19:47:46 (SasIniWkr0): WARN:  ICON MsgQ Error!!!
12/18/25-19:48:47 (SasIniWkr0): WARN:  ICON MsgQ Error!!!
12/18/25-19:49:48 (SasIniWkr0): WARN:  ICON MsgQ Error!!!

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.