跳转到主内容

物理重新定位后节点无响应

Views:
13
Visibility:
Public
Votes:
0
Category:
fas-systems<a>mroot</a><a>2009501601</a><a>mdb recovery</a><a>file_io_error</a>
Specialty:
hw
Last Updated:

适用场景

  • ONTAP 9
  • FAS 系列

问题描述

  • 在物理重新定位集群后、一个节点未正确响应集群命令。
  • 以下错误将显示在事件日志中。
 WARNING: netapp_mount_mroot: d-blade boot is incomplete netapp_mount_mroot: /mroot is not mounted, retrying...WARNING: netapp_mount_mroot: Giving up waiting for mroot after 1201 seconds. [node-1:vifmgr.rpc.nblade.timeouts:error]: The virtual interface manager is not receiving responses from the node's networking component. [node-1:callhome.mdb.recovery.unsuccessful:EMERGENCY]: Call home for MDB RECOVERY UNSUCCESSFUL FOR THE vifmgr WARNING. [node-1:rdb.env.IOFailure:ALERT]: Error encountered in root volume I/O: Mkdir '/mroot/etc/cluster_config' failed, 30. [node-1:rdb.env.replicaCorrupt:ALERT]: Corruption in the local database of Data Replication Module: Failed to open SQLite environment: FILE_IO_ERROR. 
  • 登录到节点的服务处理器时、将显示以下消息。
************************* SYSTEM MESSAGES *************************The root volume is not up. This node is not fully operational. Contact supportpersonnel for further assistance.

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.