<?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: Call home for DISK CONFIGURATION ERROR in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160523#M36682</link>
    <description>&lt;P&gt;We will try this option and feedback. thank you.&lt;/P&gt;</description>
    <pubDate>Wed, 21 Oct 2020 07:36:37 GMT</pubDate>
    <dc:creator>Divine</dc:creator>
    <dc:date>2020-10-21T07:36:37Z</dc:date>
    <item>
      <title>Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160381#M36667</link>
      <description>&lt;P&gt;Hello Guys,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We just set up a FAS2720. We attached some disk shelves from an older system to the controller after unowning them, but we realized that there were 4 disks that still pointed to the old controller. So we performed a disk zeroing on the first controller; that was successful, but on the second controller the process is stuck in a loop of rebooting. It cannot find any disk, not even the ones on the FAS2720 controller. This is what we have been getting over and over:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Oct 19 16:25:29 Power outage protection flash de-staging: 46 cycles&lt;BR /&gt;***OS2SP configured successfully***Oct 19 16:26:19 [localhost:cf.ic.sbb:notice]: HA interconnect: SBB Compatibility Event. Compatible partner node found. The interconnect device has been enabled.&lt;BR /&gt;Oct 19 16:27:20 [localhost:fal_nvme.partition.status:notice]: Partition 0-1 with capacity 894 GiB status: online.&lt;BR /&gt;Oct 19 16:27:53 [localhost:config.noPartnerDisks:error]: No disks were detected for the partner; this node cannot perform takeover correctly.&lt;BR /&gt;Oct 19 16:27:53 [localhost:callhome.dsk.config:error]: Call home for DISK CONFIGURATION ERROR&lt;BR /&gt;cryptomod_fips: Executing Crypto FIPS Self Tests.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'CPU COMPATIBILITY' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 ECB, AES-256 ECB' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 CBC, AES-256 CBC' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 GCM, AES-256 GCM' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 CCM' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'CTR_DRBG' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'SHA1, SHA256, SHA512' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'HMAC-SHA1, HMAC-SHA256, HMAC-SHA512' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'PBKDF2' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-XTS 128, AES-XTS 256' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'Self-integrity' passed.&lt;BR /&gt;Oct 19 16:27:55 [localhost:raid.autoPart.disabled:notice]: Auto-partitioning is disabled on this system: the system needs a minimum of 8 usable internal hard disks.&lt;BR /&gt;WARNING: 0 disks found!&lt;/P&gt;
&lt;P&gt;Storage Adapters found:&lt;BR /&gt;0 Fibre Channel Storage Adapters found!&lt;BR /&gt;2 SAS Adapters found!&lt;BR /&gt;0 Parallel SCSI Storage Adapters found!&lt;BR /&gt;0 ATA Adapters found!&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Select option 4 from the boot menu to choose disks for the root volume and spare core space.&lt;BR /&gt;Target Adapters found:&lt;BR /&gt;4 Fibre Channel Target Adapters found!&lt;BR /&gt;0 iSCSI Target Adapters found!&lt;/P&gt;
&lt;P&gt;WARNING: there do not appear to be any disks attached to the system.&lt;BR /&gt;No root volume found.&lt;BR /&gt;Rebooting... (press ctrl-c during boot to break reboot loop)&lt;BR /&gt;Uptime: 3m23s&lt;BR /&gt;System rebooting...&lt;BR /&gt;BIOS Version: 11.5&lt;BR /&gt;Portions Copyright (C) 2014-2018 NetApp, Inc. All Rights Reserved.&lt;/P&gt;
&lt;P&gt;Initializing System Memory ...&lt;BR /&gt;Loading Device Drivers ...&lt;BR /&gt;Configuring Devices ...&lt;/P&gt;
&lt;P&gt;CPU = 1 Processor(s) Detected.&lt;BR /&gt;Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz (CPU 0)&lt;BR /&gt;CPUID: 0x00050664. Cores per Processor = 12&lt;BR /&gt;32768 MB System RAM Installed.&lt;BR /&gt;SATA (AHCI) Device: SV9MST6D120GLM41NP&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:48:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160381#M36667</guid>
      <dc:creator>Divine</dc:creator>
      <dc:date>2025-06-04T10:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160382#M36668</link>
      <description>&lt;P&gt;halt both sides.&amp;nbsp; &amp;nbsp;and since this is new&amp;nbsp; try option 9a/9b and see where that gets you.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2020 17:17:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160382#M36668</guid>
      <dc:creator>SpindleNinja</dc:creator>
      <dc:date>2020-10-19T17:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160383#M36669</link>
      <description>&lt;P&gt;Okay. We will try that tomorrow and update you. Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2020 17:24:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160383#M36669</guid>
      <dc:creator>Divine</dc:creator>
      <dc:date>2020-10-19T17:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160385#M36670</link>
      <description>&lt;P&gt;no problem.&amp;nbsp; opt 9 is kinda like opt4 but with more options.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2020 17:44:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160385#M36670</guid>
      <dc:creator>SpindleNinja</dc:creator>
      <dc:date>2020-10-19T17:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160504#M36677</link>
      <description>&lt;P&gt;It did not work.&amp;nbsp; this is what we're seeing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Starting AUTOBOOT press Ctrl-C to abort...&lt;BR /&gt;Loading X86_64/freebsd/image1/kernel:0x200000/1056103 0x302000/10666816 0xf2e340/3748248 0x12c14d8/13689912 0x200200/1016 Entry at 0xffffffff80302000&lt;BR /&gt;Loading X86_64/freebsd/image1/platform.ko:0x1fd0000/4294256 0x23e8670/591912&lt;BR /&gt;Starting program at 0xffffffff80302000&lt;BR /&gt;NetApp Data ONTAP 9.6P9&lt;BR /&gt;mlx5en: Mellanox Ethernet driver 3.5.0 (November 2018)&lt;BR /&gt;mlx5ib: Mellanox Connect-IB Infiniband driver 3.5.0 (November 2018)&lt;BR /&gt;ena_rss_init_default_deferred() [TID:100000]: No devclass ena&lt;/P&gt;
&lt;P&gt;Copyright (C) 1992-2020 NetApp.&lt;BR /&gt;All rights reserved.&lt;BR /&gt;*******************************&lt;BR /&gt;* *&lt;BR /&gt;* Press Ctrl-C for Boot Menu. *&lt;BR /&gt;* *&lt;BR /&gt;*******************************&lt;BR /&gt;cryptomod_fips: Executing Crypto FIPS Self Tests.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'CPU COMPATIBILITY' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 ECB, AES-256 ECB' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 CBC, AES-256 CBC' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 GCM, AES-256 GCM' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'CTR_DRBG' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'SHA1, SHA256, SHA512' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'HMAC-SHA1, HMAC-SHA256, HMAC-SHA512' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'PBKDF2' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-XTS 128, AES-XTS 256' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'Self-integrity' passed.&lt;BR /&gt;Tue Oct 20 13:21:34 2020 [nv2flash.restage.progress:NOTICE]: ReStage is not needed because the flash has no data.&lt;BR /&gt;Starting DHCP client on e0M&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Oct 20 13:22:55 Power outage protection flash de-staging: 45 cycles&lt;BR /&gt;***OS2SP configured successfully***Oct 20 13:23:45 [localhost:cf.ic.sbb:notice]: HA interconnect: SBB Compatibility Event. Compatible partner node found. The interconnect device has been enabled.&lt;BR /&gt;Oct 20 13:24:46 [localhost:fal_nvme.partition.status:notice]: Partition 0-1 with capacity 894 GiB status: online.&lt;BR /&gt;Oct 20 13:25:20 [localhost:config.noPartnerDisks:error]: No disks were detected for the partner; this node cannot perform takeover correctly.&lt;BR /&gt;Oct 20 13:25:20 [localhost:callhome.dsk.config:error]: Call home for DISK CONFIGURATION ERROR&lt;BR /&gt;cryptomod_fips: Executing Crypto FIPS Self Tests.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'CPU COMPATIBILITY' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 ECB, AES-256 ECB' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 CBC, AES-256 CBC' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-128 GCM, AES-256 GCM' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'CTR_DRBG' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'SHA1, SHA256, SHA512' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'HMAC-SHA1, HMAC-SHA256, HMAC-SHA512' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'PBKDF2' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'AES-XTS 128, AES-XTS 256' passed.&lt;BR /&gt;cryptomod_fips: Crypto FIPS self-test: 'Self-integrity' passed.&lt;BR /&gt;Oct 20 13:25:22 [localhost:raid.autoPart.disabled:notice]: Auto-partitioning is disabled on this system: the system needs a minimum of 8 usable internal hard disks.&lt;BR /&gt;WARNING: 0 disks found!&lt;/P&gt;
&lt;P&gt;Storage Adapters found:&lt;BR /&gt;0 Fibre Channel Storage Adapters found!&lt;BR /&gt;2 SAS Adapters found!&lt;/P&gt;
&lt;P&gt;0 Parallel SCSI Storage Adapters found!&lt;BR /&gt;0 ATA Adapters found!&lt;/P&gt;
&lt;P&gt;Select option 4 from the boot menu to choose disks for the root volume and spare core space.&lt;BR /&gt;Target Adapters found:&lt;BR /&gt;4 Fibre Channel Target Adapters found!&lt;BR /&gt;0 iSCSI Target Adapters found!&lt;/P&gt;
&lt;P&gt;WARNING: there do not appear to be any disks attached to the system.&lt;BR /&gt;No root volume found.&lt;BR /&gt;Rebooting... (press ctrl-c during boot to break reboot loop)&lt;BR /&gt;Uptime: 3m54s&lt;BR /&gt;System rebooting...&lt;BR /&gt;BIOS Version: 11.5&lt;BR /&gt;Portions Copyright (C) 2014-2018 NetApp, Inc. All Rights Reserved.&lt;/P&gt;
&lt;P&gt;Initializing System Memory ...&lt;BR /&gt;Loading Device Drivers ...&lt;BR /&gt;Configuring Devices ...&lt;/P&gt;
&lt;P&gt;CPU = 1 Processor(s) Detected.&lt;BR /&gt;Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz (CPU 0)&lt;BR /&gt;CPUID: 0x00050664. Cores per Processor = 12&lt;BR /&gt;32768 MB System RAM Installed.&lt;BR /&gt;SATA (AHCI) Device: SV9MST6D120GLM41NP&lt;/P&gt;
&lt;P&gt;Boot Loader version 6.0.6&lt;BR /&gt;Copyright (C) 2000-2003 Broadcom Corporation.&lt;BR /&gt;Portions Copyright (C) 2002-2018 NetApp, Inc. All Rights Reserved.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2020 18:02:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160504#M36677</guid>
      <dc:creator>Divine</dc:creator>
      <dc:date>2020-10-20T18:02:20Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160517#M36679</link>
      <description>&lt;P&gt;What are the external shelves and drives?&amp;nbsp; &amp;nbsp;What's internal?&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a feeling that it's doing something screwy with RAID TEC and the internal shelves when it tries to create the roots.&amp;nbsp; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;it's been talked about before -&amp;nbsp;&lt;A href="https://community.netapp.com/t5/FAS-and-V-Series-Storage-Systems-Discussions/FAS-2720-new-aggregate-not-create/td-p/145463" target="_blank"&gt;https://community.netapp.com/t5/FAS-and-V-Series-Storage-Systems-Discussions/FAS-2720-new-aggregate-not-create/td-p/145463&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try maybe doing the re-init without the attached shelves?&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Halt&amp;nbsp;&lt;/P&gt;
&lt;P&gt;detatch external shelves.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Park Controller 2 at LOADER&amp;gt;&lt;BR /&gt;&amp;nbsp;Boot Controller 1 in to the boot menu and do opt 9&lt;BR /&gt;&amp;nbsp;Run opt 9a&lt;BR /&gt;&amp;nbsp;Run opt 9b&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;Wait for the ….. &amp;nbsp;to finish on Controller 1&lt;BR /&gt;&amp;nbsp;Boot Controller2 in to the boot menu&lt;BR /&gt;&amp;nbsp;Run opt 9a&lt;BR /&gt;&amp;nbsp;Run opt 9b&lt;BR /&gt;&amp;nbsp;Wait for Controller 2 to finish.&lt;BR /&gt;&amp;nbsp;Create Cluster&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2020 21:33:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160517#M36679</guid>
      <dc:creator>SpindleNinja</dc:creator>
      <dc:date>2020-10-20T21:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160523#M36682</link>
      <description>&lt;P&gt;We will try this option and feedback. thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 07:36:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160523#M36682</guid>
      <dc:creator>Divine</dc:creator>
      <dc:date>2020-10-21T07:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160529#M36686</link>
      <description>&lt;P&gt;no problem.&amp;nbsp; &amp;nbsp;This is the BURT I was thinking about.&amp;nbsp;&amp;nbsp;&lt;A href="https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/948840" target="_blank" rel="noopener"&gt;https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/948840&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You should be patched,&amp;nbsp; but..&amp;nbsp; &amp;nbsp;worth trying the&amp;nbsp;&lt;SPAN&gt;bootarg.raid.allow-raid-tec work around.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if that still doesn't work, open a ticket at this point IMHO.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 13:07:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160529#M36686</guid>
      <dc:creator>SpindleNinja</dc:creator>
      <dc:date>2020-10-21T13:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: Call home for DISK CONFIGURATION ERROR</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160531#M36688</link>
      <description>&lt;P&gt;this option worked. Both controllers are up and can see the attached disks. thank you.&lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 13:49:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Call-home-for-DISK-CONFIGURATION-ERROR/m-p/160531#M36688</guid>
      <dc:creator>Divine</dc:creator>
      <dc:date>2020-10-21T13:49:12Z</dc:date>
    </item>
  </channel>
</rss>

