<?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: diagnosing memory chip failures on DS25 Alpha servers in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899523#M80128</link>
    <description>Bill wrote &amp;gt;&amp;gt; I would think this is a failure of either one of your PCI adapters or the Pchip if this console error is returned every time the server is power cycled or an init is executed. I know the Pchips are located on the system board on the ES40 and I would expect the same for the DS25. Probably time to log a service call if you have a maintenance contract.&lt;BR /&gt;&lt;BR /&gt;We've seen some very interesting crashes and data corruptions with certain Pchip failures... and no errlog entries to help pinpoint the problem.&lt;BR /&gt;&lt;BR /&gt;Byron has added&amp;gt;&amp;gt; 11/17/2006 H-P support helped identify failures in recently replaced HBA card used for fiber-channel interface to SAN storage volumes which compounded the problems already occuring on this PCI Bus.. my thanks to all who contributed to the solution... it was eventually hardware replacement as the ultimate solution.</description>
    <pubDate>Fri, 17 Nov 2006 14:49:08 GMT</pubDate>
    <dc:creator>Byron Fowlkes</dc:creator>
    <dc:date>2006-11-17T14:49:08Z</dc:date>
    <item>
      <title>diagnosing memory chip failures on DS25 Alpha servers</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899518#M80123</link>
      <description>we had a cluster member  go down the last several days and initiate auto-restart action and is having no success in rejoining the cluster now... during conversational boot when the server is checking memory the console displays "Error detected by Pchip0.... GPError 00A0000... PCI Read data parity error" followed eventually by the boot prompt... my difficulty here is deciphering that message about PCI read data parity error... is it implying that software installed through the PRODUCT command in the POlyCenter facility is at the heart of the problem here.?? or is that way off-base? I would also like to evaluate the ERRLOG.SYS from the down system... any suggestion on how to make that available to the other nodes in cluster??&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Nov 2006 10:44:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899518#M80123</guid>
      <dc:creator>Byron Fowlkes</dc:creator>
      <dc:date>2006-11-16T10:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: diagnosing memory chip failures on DS25 Alpha servers</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899519#M80124</link>
      <description>In this case, I assume PCI means the PCI bus and has nothing to do with PCSI - the product installation facility.&lt;BR /&gt;If your nodes share a common system disk, the errlog can by found under SYS$SYSDEVICE:[SYSn.SYSERR], where N represents the system root.&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Thu, 16 Nov 2006 11:25:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899519#M80124</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-11-16T11:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: diagnosing memory chip failures on DS25 Alpha servers</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899520#M80125</link>
      <description>you are so right , they do indeed share a common system disk and I am working on that analysis now... and you seem to confirm my take on that  PCI error message  not being from something associated with PolyCenter</description>
      <pubDate>Thu, 16 Nov 2006 11:49:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899520#M80125</guid>
      <dc:creator>Byron Fowlkes</dc:creator>
      <dc:date>2006-11-16T11:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: diagnosing memory chip failures on DS25 Alpha servers</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899521#M80126</link>
      <description>I would think this is a failure of either one of your PCI adapters or the Pchip if this console error is returned every time the server is power cycled or an init is executed.  I know the Pchips are located on the system board on the ES40 and I would expect the same for the DS25.  Probably time to log a service call if you have a maintenance contract.&lt;BR /&gt;&lt;BR /&gt;We've seen some very interesting crashes and data corruptions with certain Pchip failures... and no errlog entries to help pinpoint the problem.&lt;BR /&gt;&lt;BR /&gt;Bill.</description>
      <pubDate>Thu, 16 Nov 2006 13:10:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899521#M80126</guid>
      <dc:creator>Bill Hall</dc:creator>
      <dc:date>2006-11-16T13:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: diagnosing memory chip failures on DS25 Alpha servers</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899522#M80127</link>
      <description>If you can, power cycle the box.&lt;BR /&gt;I've seen many problem never coming back after that (disk, cpu).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 17 Nov 2006 03:23:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899522#M80127</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-11-17T03:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: diagnosing memory chip failures on DS25 Alpha servers</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899523#M80128</link>
      <description>Bill wrote &amp;gt;&amp;gt; I would think this is a failure of either one of your PCI adapters or the Pchip if this console error is returned every time the server is power cycled or an init is executed. I know the Pchips are located on the system board on the ES40 and I would expect the same for the DS25. Probably time to log a service call if you have a maintenance contract.&lt;BR /&gt;&lt;BR /&gt;We've seen some very interesting crashes and data corruptions with certain Pchip failures... and no errlog entries to help pinpoint the problem.&lt;BR /&gt;&lt;BR /&gt;Byron has added&amp;gt;&amp;gt; 11/17/2006 H-P support helped identify failures in recently replaced HBA card used for fiber-channel interface to SAN storage volumes which compounded the problems already occuring on this PCI Bus.. my thanks to all who contributed to the solution... it was eventually hardware replacement as the ultimate solution.</description>
      <pubDate>Fri, 17 Nov 2006 14:49:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/diagnosing-memory-chip-failures-on-ds25-alpha-servers/m-p/3899523#M80128</guid>
      <dc:creator>Byron Fowlkes</dc:creator>
      <dc:date>2006-11-17T14:49:08Z</dc:date>
    </item>
  </channel>
</rss>

