<?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: VMs Hard drive in Read-only state after Storage Fail-over in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/VMs-Hard-drive-in-Read-only-state-after-Storage-Fail-over/m-p/151306#M9734</link>
    <description>&lt;P&gt;It's always good to check for compatibility and any caveats in the IMT.&lt;/P&gt;
&lt;P&gt;The NetApp® &lt;A href="http://mysupport.netapp.com/matrix/#search" target="_blank" rel="noopener"&gt;Interoperability Matrix Tool&lt;/A&gt; (IMT) defines the qualified components and versions you can use to build FC/FCoE, iSCSI, NFS and CIFS configurations. &lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Note: ONTAP 9.2 is no longer actively supported by Engineering&amp;nbsp; -- it's in a &lt;A href="https://mysupport.netapp.com//info/web/ECMP1147223.html#ontap_svst" target="_self"&gt;limited support state until 2020&lt;/A&gt;.&amp;nbsp; If your environment allows (check IMT), consider upgrading to ONTAP 9.5P6 -- it's the cat's meow, currently. If you have IOM3/DS4243 storage shelves, you'd have to stick with 9.3Px -- 9.3P15 is the latest/greatest.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Sep 2019 17:08:52 GMT</pubDate>
    <dc:creator>andris</dc:creator>
    <dc:date>2019-09-27T17:08:52Z</dc:date>
    <item>
      <title>VMs Hard drive in Read-only state after Storage Fail-over</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/VMs-Hard-drive-in-Read-only-state-after-Storage-Fail-over/m-p/151285#M9729</link>
      <description>&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;We had an issue today where our storage triggered fail lover between controllers.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;During that process our Linux based VMs went in to read-only drive state to avoid data loss or corruption.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;When storage recovered we had to reboot Linux VMs to get out from read-only state,&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;CentOS systems rebooted with out issue - repaired itself and booted to normal read write drive state.&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Ubuntu VMs had to be re scanned after boot to come back online and few did not boot up at all with swap partition missing / not able to mount.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Windows VMs were not affected.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Here is our setup:&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;NetApp Storage FAS8040 - dual controller configured for HA running Ontap 9.2.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;ESXi - 6.0.0, 7967664 with multi-path connection to storage via ISCSI&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Ubuntu&amp;nbsp;&amp;nbsp;16.04.3 LTS&amp;nbsp; xenial - Disk Time out set to 180 - no multi path connectivity.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Is there specific Ubuntu setting for vmware that we are missing? Or maybe ESXi need specific configuration for NetApp?&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;From what i was able to find online ESXi before 6 were having this issue and Linux with older kernel but it should be patched with what we have right now.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;I appreciate any suggestions.&lt;/P&gt;
&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Martin&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:13:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/VMs-Hard-drive-in-Read-only-state-after-Storage-Fail-over/m-p/151285#M9729</guid>
      <dc:creator>marcinmf</dc:creator>
      <dc:date>2025-06-04T12:13:11Z</dc:date>
    </item>
    <item>
      <title>Re: VMs Hard drive in Read-only state after Storage Fail-over</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/VMs-Hard-drive-in-Read-only-state-after-Storage-Fail-over/m-p/151306#M9734</link>
      <description>&lt;P&gt;It's always good to check for compatibility and any caveats in the IMT.&lt;/P&gt;
&lt;P&gt;The NetApp® &lt;A href="http://mysupport.netapp.com/matrix/#search" target="_blank" rel="noopener"&gt;Interoperability Matrix Tool&lt;/A&gt; (IMT) defines the qualified components and versions you can use to build FC/FCoE, iSCSI, NFS and CIFS configurations. &lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Note: ONTAP 9.2 is no longer actively supported by Engineering&amp;nbsp; -- it's in a &lt;A href="https://mysupport.netapp.com//info/web/ECMP1147223.html#ontap_svst" target="_self"&gt;limited support state until 2020&lt;/A&gt;.&amp;nbsp; If your environment allows (check IMT), consider upgrading to ONTAP 9.5P6 -- it's the cat's meow, currently. If you have IOM3/DS4243 storage shelves, you'd have to stick with 9.3Px -- 9.3P15 is the latest/greatest.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 17:08:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/VMs-Hard-drive-in-Read-only-state-after-Storage-Fail-over/m-p/151306#M9734</guid>
      <dc:creator>andris</dc:creator>
      <dc:date>2019-09-27T17:08:52Z</dc:date>
    </item>
  </channel>
</rss>

