<?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: array accelerator parity read errors: 6 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854083#M6745</link>
    <description>We installed a third controller this resolved the issue. The first replcament was a bad controller to. In another machine that faulty one also had read errors.</description>
    <pubDate>Fri, 13 Dec 2002 10:24:43 GMT</pubDate>
    <dc:creator>diekiller</dc:creator>
    <dc:date>2002-12-13T10:24:43Z</dc:date>
    <item>
      <title>array accelerator parity read errors: 6</title>
      <link>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854081#M6743</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a compaq proliant 3000 that gives us some problems. Last week it started rebooting because it detects ASR's. The machine tries to start NT 4 &amp;amp; hangs in the "blue screen" where OS loader and SP are displayed... After running the ADU (1.30A) it displayed array accelerator parity read errors:15. &lt;BR /&gt;It seems that there is a problem with the ECC memory on the accelerator card. &lt;BR /&gt;Can this cause the corruption in the NT4 installation?&lt;BR /&gt;&lt;BR /&gt;After replacing the board with a "new" one the same problem reoccured after a few days. Parity read errors:6&lt;BR /&gt;&lt;BR /&gt;Note: Don't run the ADU 1.30A under windows it will detect RIS copy problems on the disks. But this seems a ADU software problem. A higher version won't detect them&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Nov 2002 09:27:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854081#M6743</guid>
      <dc:creator>diekiller</dc:creator>
      <dc:date>2002-11-28T09:27:09Z</dc:date>
    </item>
    <item>
      <title>Re: array accelerator parity read errors: 6</title>
      <link>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854082#M6744</link>
      <description>If you have tried a 2nd controller and also have tried a newer ADU and errors don't show up, then you probably do not have a controller problem.  As another test, try disabling the cache and see what happens (use Array Config Utility for this).&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Dec 2002 16:08:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854082#M6744</guid>
      <dc:creator>Roy Main</dc:creator>
      <dc:date>2002-12-02T16:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: array accelerator parity read errors: 6</title>
      <link>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854083#M6745</link>
      <description>We installed a third controller this resolved the issue. The first replcament was a bad controller to. In another machine that faulty one also had read errors.</description>
      <pubDate>Fri, 13 Dec 2002 10:24:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/array-accelerator-parity-read-errors-6/m-p/2854083#M6745</guid>
      <dc:creator>diekiller</dc:creator>
      <dc:date>2002-12-13T10:24:43Z</dc:date>
    </item>
  </channel>
</rss>

