<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: FAS2020 Boot Loop in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/FAS2020-Boot-Loop/m-p/99997#M6108</link>
    <description>&lt;P&gt;Noticed couple of drives are missing from the list of disks, any idea?&lt;/P&gt;</description>
    <pubDate>Fri, 30 Jan 2015 13:39:58 GMT</pubDate>
    <dc:creator>organic_dave</dc:creator>
    <dc:date>2015-01-30T13:39:58Z</dc:date>
    <item>
      <title>FAS2020 Boot Loop</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/FAS2020-Boot-Loop/m-p/99951#M6105</link>
      <description>&lt;P&gt;Hi, recently our FAS2020 is acting up. We powered it down and turned it back on. Everything works except when we connect to the troubleshooting terminal, we see this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;[fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0b.&lt;/P&gt;&lt;P&gt;[fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0a.&lt;/P&gt;&lt;P&gt;NetApp Release 7.3.3&lt;/P&gt;&lt;P&gt;[nvram.battery.turned.on:info]: The NVRM battery is turned ON. It is turned OFF during systerm shutdown.&lt;/P&gt;&lt;P&gt;[diskown.isEnabled:info]: software ownership has been enabled for this system&lt;/P&gt;&lt;P&gt;[config.noPartnerDisks:CRITICAL]: No disks were detected for the partner; this node will be unable to takeover correctly&lt;/P&gt;&lt;P&gt;[fmmb.current.lock.disk:info]: Disk ?.? is a local HA mailbox disk.&lt;/P&gt;&lt;P&gt;[fmmb.current.lock.disk:info]: Disk 0c.00.2 is a local HA mailbox disk.&lt;/P&gt;&lt;P&gt;[fmmb.instStat.change:info]: definitely stale mailbox instance on local side.&lt;/P&gt;&lt;P&gt;Use aggr options root in maintenance mode to specify the proper root volumeWaiting to be taken over. REBOOT in 17 seconds.&lt;/P&gt;&lt;P&gt;Waiting to be taken over. REBOOT in 12 seconds.&lt;/P&gt;&lt;P&gt;Waiting to be taken over. REBOOT in 7 seconds.&lt;/P&gt;&lt;P&gt;-----&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then it reboots and cycles again and again. First, anyone know what the problem is?&amp;nbsp;And the best solution to resolve this issue? We are still able to access our data but we are afraid this is will turn into a much bigger problem. The data is very important to us so, please&amp;nbsp;share a none destructive fix for this issue, thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:12:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/FAS2020-Boot-Loop/m-p/99951#M6105</guid>
      <dc:creator>organic_dave</dc:creator>
      <dc:date>2025-06-05T05:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: FAS2020 Boot Loop</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/FAS2020-Boot-Loop/m-p/99997#M6108</link>
      <description>&lt;P&gt;Noticed couple of drives are missing from the list of disks, any idea?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2015 13:39:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/FAS2020-Boot-Loop/m-p/99997#M6108</guid>
      <dc:creator>organic_dave</dc:creator>
      <dc:date>2015-01-30T13:39:58Z</dc:date>
    </item>
  </channel>
</rss>

