<?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: MSATA 4TB disks (EOS) broken with no owner and pool NONE in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/MSATA-4TB-disks-EOS-broken-with-no-owner-and-pool-NONE/m-p/444518#M11541</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;indeed, it is not possible to launch an update with broken disk.&lt;BR /&gt;If they are not assigned you can physically remove them from the shlves so that they are no longer taken into account by the system and launch the update&lt;/P&gt;</description>
    <pubDate>Tue, 23 May 2023 05:15:24 GMT</pubDate>
    <dc:creator>cedric_renauld</dc:creator>
    <dc:date>2023-05-23T05:15:24Z</dc:date>
    <item>
      <title>MSATA 4TB disks (EOS) broken with no owner and pool NONE</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/MSATA-4TB-disks-EOS-broken-with-no-owner-and-pool-NONE/m-p/444487#M11540</link>
      <description>&lt;P&gt;We're preparing a FAS9000 for an ONTAP upgrade and we have several broken disks that belong to pool NONE and therefore they do not have an owner. The disk model is EOS and it's not going to be replaced.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We wanted to unassign those disks but as they do not have an owner we don't know what we should do. Would it be possible to add them to FAILED pool? Would that assign an owner to the disk? Is it safe to remove the disks as they are (pool NONE, no owner) without doing anything to guarantee the ONTAP upgrade must be performed?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for your help.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:48:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/MSATA-4TB-disks-EOS-broken-with-no-owner-and-pool-NONE/m-p/444487#M11540</guid>
      <dc:creator>jessango</dc:creator>
      <dc:date>2025-06-04T09:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: MSATA 4TB disks (EOS) broken with no owner and pool NONE</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/MSATA-4TB-disks-EOS-broken-with-no-owner-and-pool-NONE/m-p/444518#M11541</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;indeed, it is not possible to launch an update with broken disk.&lt;BR /&gt;If they are not assigned you can physically remove them from the shlves so that they are no longer taken into account by the system and launch the update&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2023 05:15:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/MSATA-4TB-disks-EOS-broken-with-no-owner-and-pool-NONE/m-p/444518#M11541</guid>
      <dc:creator>cedric_renauld</dc:creator>
      <dc:date>2023-05-23T05:15:24Z</dc:date>
    </item>
  </channel>
</rss>

