Skip to main content
NetApp Knowledge Base

MetroCluster node PANIC after dirty shutdown: NVRAM contents are invalid

Views:
253
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • FAS8200
  • ONTAP 9.7P1
  • MetroCluster FC

Issue

  • A dirty shutdown occurred due to an unexpected FC link fault of MetrCluster system
  • The system repeated restart with the below panic string and remains in the loader

PANIC: NVRAM contents are invalid...   in SK process rc on release 9.1P2 (C) on Thu Feb 23 04:45:36 GMT 2023
version: 9.1P2: Tue Feb 28 05:55:17 PST 2017
compile flags: x86_64.optimize.nodar
Writing panic info to HA mailbox disks.
HA: current time (in sk_msecs) 44017 (in sk_cycles) 448920258524

login: admin
Password:

*****************************************************
* This is a serial console session. Output from this *
* session is mirrored on the SP console session. *
******************************************************

** SYSTEM MESSAGES **
***********************
The contents of the root volume may have changed and the local management
configuration may be inconsistent and/or the local management databases may be
out of sync with the replicated databases. This node is not fully operational.
Contact support personnel for the root volume recovery procedures.

 

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.