<?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: failed disks on one head only in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128811#M7936</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Greg -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it's not production - play with it !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd try the 'disk fail' and then 'disk unfail' on the owning controller, and skip swapping in new disks...&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope this response has been helpful to you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At your service,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eugene E. Kashpureff, Sr.&lt;BR /&gt;Independent NetApp Consultant &lt;A href="http://www.linkedin.com/in/eugenekashpureff" target="_blank"&gt;http://www.linkedin.com/in/eugenekashpureff&lt;/A&gt;&lt;BR /&gt;Senior NetApp Instructor, FastLane US &lt;A href="http://www.fastlaneus.com/" target="_blank"&gt;http://www.fastlaneus.com/&lt;/A&gt;&lt;BR /&gt;(P.S. I appreciate 'kudos' on any helpful posts.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Mar 2017 16:15:07 GMT</pubDate>
    <dc:creator>ekashpureff</dc:creator>
    <dc:date>2017-03-08T16:15:07Z</dc:date>
    <item>
      <title>failed disks on one head only</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128799#M7933</link>
      <description>&lt;P&gt;Have an HA pair. &amp;nbsp;An ESH module failed causing some disks to pre-maturely fail. &amp;nbsp;Swapped the module and disks and everything is fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem now is that the partner head sees a few disks as failed. &amp;nbsp;The head that owns the disks sees them as healthy and they are data disks. &amp;nbsp;Not spares or parity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What can I do to get the partner to recognize the disks as healthy? &amp;nbsp;Fail them prematurely and swap them? &amp;nbsp;not sure what path to take.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:21:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128799#M7933</guid>
      <dc:creator>greghaa69</dc:creator>
      <dc:date>2025-06-04T15:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: failed disks on one head only</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128808#M7934</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Greg -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've never seen this before.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I could suggest two operations, but I'd be leary of proceeding on a production system without the adult supervision of NetApp support !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You're suggestion of failing the disks sounds good, but I wouldn't swap them out.&lt;/P&gt;&lt;P&gt;Instead I'd use the advanced priv 'disk unfail' command.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The other more risky option would be to fail over to the partner.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again - I'd open a ticket with support rather than proceed on my own ...&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope this response has been helpful to you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At your service,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eugene E. Kashpureff, Sr.&lt;BR /&gt;Independent NetApp Consultant &lt;A href="http://www.linkedin.com/in/eugenekashpureff" target="_blank"&gt;http://www.linkedin.com/in/eugenekashpureff&lt;/A&gt;&lt;BR /&gt;Senior NetApp Instructor, FastLane US &lt;A href="http://www.fastlaneus.com/" target="_blank"&gt;http://www.fastlaneus.com/&lt;/A&gt;&lt;BR /&gt;(P.S. I appreciate 'kudos' on any helpful posts.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 15:44:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128808#M7934</guid>
      <dc:creator>ekashpureff</dc:creator>
      <dc:date>2017-03-08T15:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: failed disks on one head only</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128809#M7935</link>
      <description>&lt;P&gt;That was the only idea I could come up with. &amp;nbsp;"disk unfail -s" on the partner head and let a spare take over. Although on the owned head the disks aren't failed so not sure that will work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could possibly fail the disk on the head that owns the disk and let a spare take over and then swap with a good disk. &amp;nbsp; I think because the module failed and was replaced it set a failed state in the partner and was never cleared when the good module came online. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a QA system and only serves data internally. &amp;nbsp;Not a prod system.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 16:04:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128809#M7935</guid>
      <dc:creator>greghaa69</dc:creator>
      <dc:date>2017-03-08T16:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: failed disks on one head only</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128811#M7936</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Greg -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it's not production - play with it !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd try the 'disk fail' and then 'disk unfail' on the owning controller, and skip swapping in new disks...&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope this response has been helpful to you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At your service,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eugene E. Kashpureff, Sr.&lt;BR /&gt;Independent NetApp Consultant &lt;A href="http://www.linkedin.com/in/eugenekashpureff" target="_blank"&gt;http://www.linkedin.com/in/eugenekashpureff&lt;/A&gt;&lt;BR /&gt;Senior NetApp Instructor, FastLane US &lt;A href="http://www.fastlaneus.com/" target="_blank"&gt;http://www.fastlaneus.com/&lt;/A&gt;&lt;BR /&gt;(P.S. I appreciate 'kudos' on any helpful posts.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 16:15:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/failed-disks-on-one-head-only/m-p/128811#M7936</guid>
      <dc:creator>ekashpureff</dc:creator>
      <dc:date>2017-03-08T16:15:07Z</dc:date>
    </item>
  </channel>
</rss>

