<?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 E-Series Data Loss in EF &amp; E-Series, SANtricity, and Related Plug-ins</title>
    <link>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132106#M410</link>
    <description>&lt;P&gt;Twice in the last nine months we have had a drive failure followed by significant data loss. Event type is 2046 Isolation of drive causing redundancy mismatch. Tough to lose TB of data and multiple machines running under VMware. Anyone experience this?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 14:56:20 GMT</pubDate>
    <dc:creator>SEGway</dc:creator>
    <dc:date>2025-06-04T14:56:20Z</dc:date>
    <item>
      <title>E-Series Data Loss</title>
      <link>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132106#M410</link>
      <description>&lt;P&gt;Twice in the last nine months we have had a drive failure followed by significant data loss. Event type is 2046 Isolation of drive causing redundancy mismatch. Tough to lose TB of data and multiple machines running under VMware. Anyone experience this?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:56:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132106#M410</guid>
      <dc:creator>SEGway</dc:creator>
      <dc:date>2025-06-04T14:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: E-Series Data Loss</title>
      <link>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132126#M411</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I did a search and found this for you:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A title="https://kb.netapp.com/support/s/article/ka21A0000000jL7/what-does-isolation-of-drive-causing-redundancy-mismatch-mean" href="https://kb.netapp.com/support/s/article/ka21A0000000jL7/what-does-isolation-of-drive-causing-redundancy-mismatch-mean" target="_blank"&gt;https://kb.netapp.com/support/s/article/ka21A0000000jL7/what-does-isolation-of-drive-causing-redundancy-mismatch-mean&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A title="https://kb.netapp.com/support/index?page=content&amp;amp;id=2025182" href="https://kb.netapp.com/support/index?page=content&amp;amp;id=2025182" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=2025182&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also I found a related support case for this issue and the solution was in the above KB (to perform a parity scan and repair on the volume)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/Matt&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2017 14:31:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132126#M411</guid>
      <dc:creator>mbeattie</dc:creator>
      <dc:date>2017-06-21T14:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: E-Series Data Loss</title>
      <link>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132140#M412</link>
      <description>&lt;P&gt;Thanks but I can get to the first article but not the second.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2017 18:48:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132140#M412</guid>
      <dc:creator>SEGway</dc:creator>
      <dc:date>2017-06-21T18:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: E-Series Data Loss</title>
      <link>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132150#M413</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Here is the external link:&lt;BR /&gt;&lt;BR /&gt;&lt;A title="https://kb.netapp.com/support/s/article/ka11A0000001aGz/isolation-of-drive-causes-redundancy-mismatch" href="https://kb.netapp.com/support/s/article/ka11A0000001aGz/isolation-of-drive-causes-redundancy-mismatch" target="_blank"&gt;https://kb.netapp.com/support/s/article/ka11A0000001aGz/isolation-of-drive-causes-redundancy-mismatch&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you are unable to access the above URL, whilst the KB article does provide technical detail on how to identify the volume requiring a parity scan and perform a repair based on the raw data in the logs, it also contains the following statement:&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;"WARNING: Isolation of drive causing redundancy mismatch does involve data integrity &lt;STRONG&gt;and any actions should take place under the guidance of NetApp Support&lt;/STRONG&gt;. If there are any uncertainties or unexpected results, please engage appropriate resources."&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;Therefore I'd advise opening a support case as the appropriate course of action.&lt;BR /&gt;&lt;BR /&gt;/Matt&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2017 01:27:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/EF-E-Series-SANtricity-and-Related-Plug-ins/E-Series-Data-Loss/m-p/132150#M413</guid>
      <dc:creator>mbeattie</dc:creator>
      <dc:date>2017-06-22T01:27:37Z</dc:date>
    </item>
  </channel>
</rss>

