メインコンテンツへスキップ

AFF A900/A70/A90またはFAS9500/FAS70/FAS90が「No NV device has been detected」でブートに失敗する

Views:
50
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

環境

  • AFF A900 / FAS9500
  • FAS70/90
  • AFF A70 / A90
  • ONTAP 9

問題

  • AFF A900/FAS9500ノードが次のようなアラートとともにブートに失敗する:

Wed Jun 28 00:00:00 GMT [nvram.hw.initFail:CRITICAL]: NVRAM hardware initialization failed: Failed to read SSD configuration.
Wed Jun 28 00:00:00 [node01:nv.flash.unable.to.monitor:ALERT]: Unable to monitor NVRAM device "NVRAM11".
Wed Jun 28 00:00:00 [node01:nv.none:EMERGENCY]: No NV device has been detected.

  • FAS70/90またはAFF A70/A90ノードは、次のようなアラートとともにブートに失敗することがあります:

    Feb 27 16:30:48 [localhost:nv.flash.unable.to.monitor:ALERT]: Unable to monitor NVRAM device "NVRAM12". NIC FW update from kernel error is :0
    Feb 27 16:31:00 [localhost:nv.none:EMERGENCY]: No NV device has been detected.
    Feb 27 16:31:00 [localhost:monitor.temp.unreadable:error]: The controller temperature (NVRAM M2 Temp) is not readable.
    Feb 27 16:31:01 [localhost:ha.partner.discovered:notice]: Discovered HA partner with system ID 538351174, port 0.
    Feb 27 16:31:01 [localhost:monitor.temp.unreadable:error]: The controller temperature (NVRAM DIMM1 Temp) is not readable.
    Feb 27 16:31:01 [localhost:monitor.temp.unreadable:error]: The controller temperature (NVRAM Inlet Temp) is not readable.
    Feb 27 16:31:01 [localhost:monitor.temp.unreadable:error]: The controller temperature (NVRAM Riser Temp) is not readable.
    Feb 27 16:31:01 [localhost:monitor.temp.unreadable:error]: The controller temperature (NVRAM FPGA Temp) is not readable.
    Feb 27 16:31:01 [localhost:sp.reboot.sensor.unreadable:notice]: Rebooting BMC because one or more sensors are unreadable.
  • FAS70/90またはAFF A70/A90ノードは、NVDIMM関連のエラーメッセージとともにブートに失敗することもあります:
 Tue May 20 03:58:52 GMT [nvram.hw.initFail:CRITICAL]: NVRAM hardware initialization failed: Failed to read NVRAM DIMM1 SPD information. Reseat or replace the NVRAM DIMM. Check for NVRAM DIMM1 label on the PCB silkscreen. Tue May 20 03:58:52 GMT [nvram.hw.initFail:CRITICAL]: NVRAM hardware initialization failed: Failed to read NVRAM DIMM2 SPD information. Reseat or replace the NVRAM DIMM. Check for NVRAM DIMM2 label on the PCB silkscreen. May 20 06:07:11 [node:nv.flash.unable.to.monitor:ALERT]: Unable to monitor NVRAM device "NVRAM12". ***OS2SP configured successfully***RC NIC fw update error is :0 NIC FW update from kernel error is :0 May 20 06:07:45 [node:fal_nvme.partition.status:notice]: Partition 0-1 with capacity 3576 GiB status: rewarm. May 20 06:07:45 [node:fal_nvme.partition.status:notice]: Partition 0-1 with capacity 3576 GiB status: rewarm. May 20 06:07:45 [node:ha.partner.discovered:notice]: Discovered HA partner with system ID 538341427, port 1. May 20 06:07:45 [node:ha.partner.discovered:notice]: Discovered HA partner with system ID 538341427, port 0. May 20 06:08:03 [node:nv.none:EMERGENCY]: No NV device has been detected.
  • コンソール ログ 
Waiting for giveback...(Press Ctrl-C to abort wait)******************************************************************* * ---=< WARNING --- WARNING --- WARNING >=--- * * * * NVRAM detected internal error and initiating a clean shutdown. * * * * Data loss WILL occur in non-HA system if clean shutdown failed. * ******************************************************************* Terminated Uptime: 2m25s PANIC : page fault (supervisor read data, page not present) on VA 0x448 cs:rip 0x20:0xffffffff80366fe3 rflags 0x10246 version: 9.15.1P11: Wed May 21 18:53:05 EDT 2025

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.