<?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 Replace manually a broken disk with a spare one in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Replace-manually-a-broken-disk-with-a-spare-one/m-p/454779#M43899</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this Monday, I've had two discs fall into failed state. One was automatically replaced by one of the spare disks, but the other was not.&amp;nbsp;For information, my aggregate is made up of 7200RPM disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I actually had 3 spare disks:&lt;BR /&gt;- 1 x 7200RPM (the one that replaced the failed disk)&lt;BR /&gt;- 2 x 15000RPM (which don't automatically launch the replacement)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess the replacement doesn't start automatically because the disks have different specifications (I understand that and I'm quite okay with it).&lt;/P&gt;&lt;P&gt;However, I'd like to force the disk replacement even if the spare disk is faster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most of the disks have been running for as long as the disks that failed, and I'd like to minimize the chances of ending up with 3 failed disks (and then the drama...).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My failed aggregate:&lt;/P&gt;&lt;P&gt;Position Disk Pool Type RPM Size Size Status&lt;BR /&gt;-------- --------------------------- ---- ----- ------ -------- -------- ----------&lt;BR /&gt;shared 2.0.8 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.10 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.12 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.14 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.16 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.1.23 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.4 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared FAILED - - - 3.57TB - (failed)&lt;BR /&gt;shared 2.0.22 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My spare disks:&lt;/P&gt;&lt;P&gt;Disk HA Shelf Bay Chan Pool Type Class RPM Size Size Owner&lt;BR /&gt;--------------- ------------ ---- ------ ------ ----------- ------ -------- -------- --------&lt;BR /&gt;2.0.6 0a 0 6 B Pool0 SAS performance 15000 3.63TB 3.64TB SAME_OWNER_AS_THE_AGGREGATE&lt;BR /&gt;2.0.17 0a 0 17 B Pool0 SAS performance 15000 3.63TB 3.64TB SAME_OWNER_AS_THE_AGGREGATE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance !&lt;/P&gt;</description>
    <pubDate>Fri, 30 Aug 2024 13:37:30 GMT</pubDate>
    <dc:creator>UnitIT</dc:creator>
    <dc:date>2024-08-30T13:37:30Z</dc:date>
    <item>
      <title>Replace manually a broken disk with a spare one</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Replace-manually-a-broken-disk-with-a-spare-one/m-p/454779#M43899</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this Monday, I've had two discs fall into failed state. One was automatically replaced by one of the spare disks, but the other was not.&amp;nbsp;For information, my aggregate is made up of 7200RPM disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I actually had 3 spare disks:&lt;BR /&gt;- 1 x 7200RPM (the one that replaced the failed disk)&lt;BR /&gt;- 2 x 15000RPM (which don't automatically launch the replacement)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess the replacement doesn't start automatically because the disks have different specifications (I understand that and I'm quite okay with it).&lt;/P&gt;&lt;P&gt;However, I'd like to force the disk replacement even if the spare disk is faster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most of the disks have been running for as long as the disks that failed, and I'd like to minimize the chances of ending up with 3 failed disks (and then the drama...).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My failed aggregate:&lt;/P&gt;&lt;P&gt;Position Disk Pool Type RPM Size Size Status&lt;BR /&gt;-------- --------------------------- ---- ----- ------ -------- -------- ----------&lt;BR /&gt;shared 2.0.8 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.10 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.12 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.14 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.16 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.1.23 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared 2.0.4 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;BR /&gt;shared FAILED - - - 3.57TB - (failed)&lt;BR /&gt;shared 2.0.22 0 FSAS 7200 3.57TB 3.64TB (normal)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My spare disks:&lt;/P&gt;&lt;P&gt;Disk HA Shelf Bay Chan Pool Type Class RPM Size Size Owner&lt;BR /&gt;--------------- ------------ ---- ------ ------ ----------- ------ -------- -------- --------&lt;BR /&gt;2.0.6 0a 0 6 B Pool0 SAS performance 15000 3.63TB 3.64TB SAME_OWNER_AS_THE_AGGREGATE&lt;BR /&gt;2.0.17 0a 0 17 B Pool0 SAS performance 15000 3.63TB 3.64TB SAME_OWNER_AS_THE_AGGREGATE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance !&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2024 13:37:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Replace-manually-a-broken-disk-with-a-spare-one/m-p/454779#M43899</guid>
      <dc:creator>UnitIT</dc:creator>
      <dc:date>2024-08-30T13:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: Replace manually a broken disk with a spare one</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Replace-manually-a-broken-disk-with-a-spare-one/m-p/454804#M43903</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;It's normal way, different type of disk could not be in the same AGGR, for you : SAS and FSAS (Sata)&lt;/P&gt;&lt;P&gt;But it's a best practice to avoid mixed disk type and avoid performance issue, if your are aware abot this issues you can try this command to authorize the mix :&lt;/P&gt;&lt;P&gt;7-Mode&lt;BR /&gt;&amp;gt;raid.disktype.enable&lt;/P&gt;&lt;P&gt;Cluster ONTAP&lt;BR /&gt;&amp;gt;storage raid-options modify - raid.disktype.enable&lt;/P&gt;&lt;P&gt;The source is this article :&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.netapp.com/t5/Network-and-Storage-Protocols/mixed-disk-types-in-one-aggregate/td-p/9777" target="_blank"&gt;https://community.netapp.com/t5/Network-and-Storage-Protocols/mixed-disk-types-in-one-aggregate/td-p/9777&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Sep 2024 16:11:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Replace-manually-a-broken-disk-with-a-spare-one/m-p/454804#M43903</guid>
      <dc:creator>cedric_renauld</dc:creator>
      <dc:date>2024-09-01T16:11:47Z</dc:date>
    </item>
  </channel>
</rss>

