<?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: Disk Path Name Changed After Motherboard Replacement in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Disk-Path-Name-Changed-After-Motherboard-Replacement/m-p/440339#M11427</link>
    <description>&lt;P&gt;Difficult to say what could have caused it but after motherboard/controller replacement weird things do happen sometimes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My suggestion would be: Have a support case open.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could try this but please do consult the NetApp support first.&lt;BR /&gt;1) Take-over and giveback of the Node (MB replaced)&lt;BR /&gt;if still unresolved then,&lt;BR /&gt;2) Re-cyle IOM Module.&lt;BR /&gt;&lt;A href="https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/How_to_non-disruptively_reboot_a_SAS_shelf" target="_blank"&gt;https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/How_to_non-disruptively_reboot_a_SAS_shelf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Dec 2022 10:03:14 GMT</pubDate>
    <dc:creator>Ontapforrum</dc:creator>
    <dc:date>2022-12-06T10:03:14Z</dc:date>
    <item>
      <title>Disk Path Name Changed After Motherboard Replacement</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Disk-Path-Name-Changed-After-Motherboard-Replacement/m-p/440333#M11426</link>
      <description>&lt;P&gt;After replacing a Motherboard on an A200 (ONTAP 9.8P7), the disk path name changed for SAS adapter 0a from something like 00.1 to 002D57EC.1. All 12 drives reporting on 0a have this nomenclature, while SAS adapter 0b represent the disk paths as expected (00.1, 00.2, etc.). Any ideas here?&lt;/P&gt;&lt;P&gt;Thx.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:54:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Disk-Path-Name-Changed-After-Motherboard-Replacement/m-p/440333#M11426</guid>
      <dc:creator>JPick</dc:creator>
      <dc:date>2025-06-04T09:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Path Name Changed After Motherboard Replacement</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Disk-Path-Name-Changed-After-Motherboard-Replacement/m-p/440339#M11427</link>
      <description>&lt;P&gt;Difficult to say what could have caused it but after motherboard/controller replacement weird things do happen sometimes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My suggestion would be: Have a support case open.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could try this but please do consult the NetApp support first.&lt;BR /&gt;1) Take-over and giveback of the Node (MB replaced)&lt;BR /&gt;if still unresolved then,&lt;BR /&gt;2) Re-cyle IOM Module.&lt;BR /&gt;&lt;A href="https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/How_to_non-disruptively_reboot_a_SAS_shelf" target="_blank"&gt;https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/How_to_non-disruptively_reboot_a_SAS_shelf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2022 10:03:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Disk-Path-Name-Changed-After-Motherboard-Replacement/m-p/440339#M11427</guid>
      <dc:creator>Ontapforrum</dc:creator>
      <dc:date>2022-12-06T10:03:14Z</dc:date>
    </item>
  </channel>
</rss>

