<?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: E01000502: EID_PARITY_INIT_FAILED in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038855#M11971</link>
    <description>&lt;P&gt;We have checjed by looking at the status and all disks were reported oke.&lt;/P&gt;&lt;P&gt;No other problems detected. So I looked at the ADU log and found disk 2 reporting a lot Read Erros Hard, whils all other drives were oke.&lt;/P&gt;&lt;P&gt;So I assume during a parity init the system got some read errors and this created the problem.&lt;/P&gt;&lt;P&gt;We have replaced the disk and it is now in rebuild status.&lt;/P&gt;&lt;P&gt;Thn\anks for the hrpl&lt;/P&gt;</description>
    <pubDate>Tue, 19 Mar 2019 13:58:39 GMT</pubDate>
    <dc:creator>HanCas</dc:creator>
    <dc:date>2019-03-19T13:58:39Z</dc:date>
    <item>
      <title>E01000502: EID_PARITY_INIT_FAILED</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038825#M11967</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We have P4300G2 showing the following E01000502: EID_PARITY_INIT_FAILED.&lt;BR /&gt;The 'Data Array 1' Parity Initialization Status is Failed&lt;BR /&gt;How can we recover, or will this be fixed automagically in background by recalcing the parity?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 10:37:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038825#M11967</guid>
      <dc:creator>HanCas</dc:creator>
      <dc:date>2019-03-19T10:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: E01000502: EID_PARITY_INIT_FAILED</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038829#M11968</link>
      <description>&lt;P&gt;Hi HanCas,&lt;/P&gt;&lt;P&gt;the only way to recover from this failed status of the parity init is to put the node in repair and to reconfigure the raid.&lt;/P&gt;&lt;P&gt;There is no other way to start this process on the array.&lt;/P&gt;&lt;P&gt;There are some reasons this can fail&lt;/P&gt;&lt;P&gt;- firmware of Smart Array Controller&lt;/P&gt;&lt;P&gt;- firmware Hdd&lt;/P&gt;&lt;P&gt;- bad drive&lt;/P&gt;&lt;P&gt;- timeout&lt;/P&gt;&lt;P&gt;HowTo: &lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0112618" target="_blank" rel="noopener"&gt;HP StoreVirtual 4000 - Repair with Cliq Stop Store&lt;/A&gt;&lt;/P&gt;&lt;P&gt;hope this helps&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 10:58:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038829#M11968</guid>
      <dc:creator>Assen</dc:creator>
      <dc:date>2019-03-19T10:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: E01000502: EID_PARITY_INIT_FAILED</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038836#M11969</link>
      <description>&lt;P&gt;Thanks for the reply. We are V12 I believe so it should be doable, if we can find the source of the problem.&lt;/P&gt;&lt;P&gt;Hopefully it is just one disk, otherwise we have the risc of totally rebilding the node&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 11:35:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038836#M11969</guid>
      <dc:creator>HanCas</dc:creator>
      <dc:date>2019-03-19T11:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: E01000502: EID_PARITY_INIT_FAILED</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038851#M11970</link>
      <description>&lt;P&gt;it depends which hdd are bad or need to be replaced&lt;/P&gt;&lt;P&gt;here is a layout of the logical drives and config of p4300g1/g2 nodes&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="4300g1-g2.PNG" style="width: 572px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/108799iF10F33CBD67595DA/image-size/large?v=v2&amp;amp;px=2000" role="button" title="4300g1-g2.PNG" alt="4300g1-g2.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 13:33:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038851#M11970</guid>
      <dc:creator>Assen</dc:creator>
      <dc:date>2019-03-19T13:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: E01000502: EID_PARITY_INIT_FAILED</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038855#M11971</link>
      <description>&lt;P&gt;We have checjed by looking at the status and all disks were reported oke.&lt;/P&gt;&lt;P&gt;No other problems detected. So I looked at the ADU log and found disk 2 reporting a lot Read Erros Hard, whils all other drives were oke.&lt;/P&gt;&lt;P&gt;So I assume during a parity init the system got some read errors and this created the problem.&lt;/P&gt;&lt;P&gt;We have replaced the disk and it is now in rebuild status.&lt;/P&gt;&lt;P&gt;Thn\anks for the hrpl&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 13:58:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7038855#M11971</guid>
      <dc:creator>HanCas</dc:creator>
      <dc:date>2019-03-19T13:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: E01000502: EID_PARITY_INIT_FAILED</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7077970#M12226</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1814464"&gt;@Assen&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would appreciate your help on this issue regarding 2 errors we have on a P4500 that we are trying to decommision but still have critical workloads in operation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;IMG src="c:\capture.png" border="0" alt="" /&gt;Event ID: E01000502:EID_PARITY_INIT_FAILED | Data Array 1 ' Parity Initialisation Status = 'Failed'&lt;/P&gt;
&lt;P&gt;Event ID: E01020301:EID_CACHE_ENABLED_DISABLED | Write Cache 1 'Status ='Disabled'&lt;/P&gt;
&lt;P&gt;We have done the following without any resolution:&lt;/P&gt;
&lt;P&gt;1. Repalced Cache Battery more than once&lt;/P&gt;
&lt;P&gt;2. Replaced failed disks on node that were rebuilt however partity error above has not cleared.&lt;/P&gt;
&lt;P&gt;Please could we chat, offline if necessary?&lt;/P&gt;
&lt;P&gt;Many Thanks&lt;/P&gt;
&lt;P&gt;NHS Stealth &lt;LI-EMOJI id="lia_winking-face" title=":winking_face:"&gt;&lt;/LI-EMOJI&gt; Acute Hospital&lt;/P&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2020 04:27:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/e01000502-eid-parity-init-failed/m-p/7077970#M12226</guid>
      <dc:creator>NHS-Stealth</dc:creator>
      <dc:date>2020-02-05T04:27:54Z</dc:date>
    </item>
  </channel>
</rss>

