Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • How to troubleshoot Metadata drive moves to available as soon as adding it
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_troubleshoot_Metadata_drive_moves_to_available_as_soon_as_adding_it
      Applies to NetApp Element software Storage Node Description Metadata drive moves to available a few minutes later after adding it.
    • H610S NVDIMM persistenceLost True alert
      https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/H610S_NVDIMM_persistenceLost_True_alert
      ‘persistenceLost’, True alert messages occur in NetApp SolidFire H610S NVDIMM. Refer to KB article to check the cause and appropriate steps to fix the issue.
    • NetApp H610S1 node has hardwareRevision: incorrect revision warning
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/NetApp_H610S1_node_has_hardwareRevision__incorrect_revision_warning
      Applies to NetApp Element software NetApp H610S-1 Issue Nodes report the following on SolidFire Active IQ: NVRAM device warning={0 hardwareRevision: incorrect revision 00, 1 hardwareRevision: incorrec...Applies to NetApp Element software NetApp H610S-1 Issue Nodes report the following on SolidFire Active IQ: NVRAM device warning={0 hardwareRevision: incorrect revision 00, 1 hardwareRevision: incorrect revision 00}
    • After replacing NVDIMM on FAS9000 / AFF-A700, error message 'Data loss is likely' seen on boot
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/After_replacing_NVDIMM_on_FAS9000_AFF_A700_error_message_Data_loss_is_likely_seen_on_boot
      Applies to FAS9000 AFF-A700 Issue After replacing NVDIMM on FAS9000 / AFF-A700, 'Data loss is likely' seen on boot ****************************************************************** * CRITICAL ERROR *...Applies to FAS9000 AFF-A700 Issue After replacing NVDIMM on FAS9000 / AFF-A700, 'Data loss is likely' seen on boot ****************************************************************** * CRITICAL ERROR * * NVRAM has detected errors. Ontap cleared the error. * * Data loss is likely. * ******************************************************************
    • RTFI fails on H610S with 'NVDIMMs are not armed'
      https://kb.netapp.com/Legacy/NetApp_HCI/Hardware/RTFI_fails_on_H610S_with_NVDIMMs_are_not_armed
      Applies to NetApp Element software NetApp H610S storage node Issue On screen RTFI error: UnhandledError pid=1 cmd=return 1 Error in rtfi.log: NVDIMMs are not armed! THIS IS A BAD STATE AND SHOULDN'T H...Applies to NetApp Element software NetApp H610S storage node Issue On screen RTFI error: UnhandledError pid=1 cmd=return 1 Error in rtfi.log: NVDIMMs are not armed! THIS IS A BAD STATE AND SHOULDN'T HAPPEN!!!! Sfnodereset fails with the same errors
    • H610S: erroneous NVRAM error messages
      https://kb.netapp.com/Legacy/NetApp_HCI/Hardware/H610S__erroneous_NVRAM_error_messages
      This article covers sporadic logging of NVRAM faults on H610S nodes, which often results in eviction of a node's slice (metadata) drive. The node logs a variation of one of the NVRAM (NVDIMM) faults m...This article covers sporadic logging of NVRAM faults on H610S nodes, which often results in eviction of a node's slice (metadata) drive. The node logs a variation of one of the NVRAM (NVDIMM) faults mentioned in the issue section.
    • Panic "NVMEM must start in battery backed region" on AFF A800
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Panic_NVMEM_must_start_in_battery_backed_region_on_AFF_A800
      Applies to AFF A800 AFF C800 Issue During reboot (such as after a takeover or sync core), node continues to panic in boot loop: PANIC : NVMEM must start in battery backed region, start: 0x9470000000 b...Applies to AFF A800 AFF C800 Issue During reboot (such as after a takeover or sync core), node continues to panic in boot loop: PANIC : NVMEM must start in battery backed region, start: 0x9470000000 battery backed start: 0x9870000000 Additional DIMM mapped out errors in console logs prior to first panic show a mapped out NVMEM DIMM: Major Code 0x0A Minor Code 0x03 DIMM:11 mapped out. BIOS MRC mapped out DIMM. Major Code 0x14 Minor Code 0x02
    • After upgrade to ONTAP 9.7, system fails to boot with error 'NVDIMM Driver load failed'
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/After_upgrade_to_ONTAP_9_7_system_fails_to_boot_with_error_NVDIMM_Driver_load_failed
      Applies to ONTAP Select ONTAP Upgrade to 9.7 Issue After upgrade to ONTAP 9.7, system fails to boot, and the following error is seen: load /nvdimm.ko: failed - no such file or directory NVDIMM Driver ...Applies to ONTAP Select ONTAP Upgrade to 9.7 Issue After upgrade to ONTAP 9.7, system fails to boot, and the following error is seen: load /nvdimm.ko: failed - no such file or directory NVDIMM Driver load failed can't find 'x86_64/freebsd/image2/nvdimm.ko' VLOADER> _
    • Node booting with ERROR Arming NVDIMM
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Node_booting_with_ERROR_Arming_NVDIMM
      Node boots with ERROR Arming NVDIMM (non-volatile dual in-line memory module)