Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 7 results
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/MetroCluster_node_PANIC_after_dirty_shutdown__NVRAM_contents_are_invalid
      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.....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 * session is mirrored on the SP console session. * 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
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/MDB_RECOVERY_UNSUCCESSFUL_FOR_THE_XXXXXX
      Applies to ONTAP 9.7P5 Issue Unable to access System Manager Clustershell commands return There are no entries matching your query. ASUP notification: HA Group Notification (MDB RECOVERY UNSUCCESSFUL ...Applies to ONTAP 9.7P5 Issue Unable to access System Manager Clustershell commands return There are no entries matching your query. ASUP notification: HA Group Notification (MDB RECOVERY UNSUCCESSFUL FOR THE vldb) EMERGENCY HA Group Notification (MDB RECOVERY UNSUCCESSFUL FOR THE vifmgr) EMERGENCY HA Group Notification (ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED) EMERGENCY
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/After_upgrade_to_9.7x_release_the_system_comes_up_with_root_volume_not_working_properly
      Applies to ONTAP 9.7 Issue Upgrading to 9.7x release may cause the system to come up with the following error: ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Root_Volume_Recovery_required_following_panic_during_ONTAP_update
      Applies to ONTAP 9 Root Volume Recovery Issue Unexpected reboot during ONTAP upgrade or hardware replacement with the following panic message: NVRAM contents are invalid... in SK process rc on release...Applies to ONTAP 9 Root Volume Recovery Issue Unexpected reboot during ONTAP upgrade or hardware replacement with the following panic message: NVRAM contents are invalid... in SK process rc on release 9.6P9 (C) The following message is encountered: callhome.root.vol.recovery.reqd:EMERGENCY]: Call home for ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED.
    • https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Resolving_root_volume_recovery_in_Cloud_Volumes_ONTAP_and_ONTAP_select_environments
      Resolving root volume recovery in cloud environment
    • https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Select_ROOT_VOLUME_NOT_WORKING_PROPERLY__RECOVERY_REQUIRED
      Applies to ONTAP Select ONTAP 9 Issue Node not serving data. Following notification is displayed: System Notification (ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED) EMERGENCY Vol0 is full / low...Applies to ONTAP Select ONTAP 9 Issue Node not serving data. Following notification is displayed: System Notification (ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED) EMERGENCY Vol0 is full / low on free space.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Root_Volume_Recovery_required_after_an_unexpected_Power_Outage_or_HeadSwap
      Unexpected power outage causes ONTAP to boot with ‘Root Volume Recovery required’ message, '[cluster:callhome.root.vol.recovery.reqd:EMERGENCY]: Call home for ROOT VOLUME NOT WORKING PROPERLY: RECOVER...Unexpected power outage causes ONTAP to boot with ‘Root Volume Recovery required’ message, '[cluster:callhome.root.vol.recovery.reqd:EMERGENCY]: Call home for ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED'. KB articles provides recovery steps for ONTAP 9.4 or later and ONTAP 9.3 or earlier.