<?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 POST Error: 283-Memory Address in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204453#M184908</link>
    <description>&lt;P&gt;Hello all.&lt;/P&gt;&lt;P&gt;I was in the midst of uploading some files to one of my vmware virtual machines last night when I realized that I had been disconnected from my ESXi Dashboard. My first reaction was to assume that ESXi was the culprit and had initiated a software reboot (which has not happened to me before by the way)&lt;/P&gt;&lt;P&gt;It wasn't long before I realized that it was in fact my Proliant server that had rebooted on it's own. Once the reboot sequence was terminated was I able to log into the iLO dashboard and go through the logs and events. Lo and behold I came across a POST message with Class "Critical". It read:&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;POST Error: 283-Memory Address/Command Parity Error Detected - Processor 2, Channel 2. Action: Reseat the DIMMs. If the issue persists, contact HP service.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;I have to confess that this was not the first time that this has happened to me. I have not had the server for long but I experienced the same issue some two weeks ago. At which point I did reseat the memory and hoped that I had resolved this worrisome problem. Obviously, this was not the case.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Intelligent Provisioning / Insight Diagnostics. I ran short / long tests on the total memory and processors and everythinng came up green. Is there a way that I can pinpoint which memory or sticks are is/are causing the self-reboot.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Your time, expertise and assistance will be greatly appreciated. Peter&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;A href="https://i.postimg.cc/ryjF56vj/Parity-error-Screenshot-2024-01-11-201032.jpg" target="_blank" rel="noopener"&gt;Parity Error&lt;/A&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 13 Jan 2024 12:03:51 GMT</pubDate>
    <dc:creator>peterbatah</dc:creator>
    <dc:date>2024-01-13T12:03:51Z</dc:date>
    <item>
      <title>POST Error: 283-Memory Address</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204453#M184908</link>
      <description>&lt;P&gt;Hello all.&lt;/P&gt;&lt;P&gt;I was in the midst of uploading some files to one of my vmware virtual machines last night when I realized that I had been disconnected from my ESXi Dashboard. My first reaction was to assume that ESXi was the culprit and had initiated a software reboot (which has not happened to me before by the way)&lt;/P&gt;&lt;P&gt;It wasn't long before I realized that it was in fact my Proliant server that had rebooted on it's own. Once the reboot sequence was terminated was I able to log into the iLO dashboard and go through the logs and events. Lo and behold I came across a POST message with Class "Critical". It read:&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;POST Error: 283-Memory Address/Command Parity Error Detected - Processor 2, Channel 2. Action: Reseat the DIMMs. If the issue persists, contact HP service.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;I have to confess that this was not the first time that this has happened to me. I have not had the server for long but I experienced the same issue some two weeks ago. At which point I did reseat the memory and hoped that I had resolved this worrisome problem. Obviously, this was not the case.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Intelligent Provisioning / Insight Diagnostics. I ran short / long tests on the total memory and processors and everythinng came up green. Is there a way that I can pinpoint which memory or sticks are is/are causing the self-reboot.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Your time, expertise and assistance will be greatly appreciated. Peter&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;A href="https://i.postimg.cc/ryjF56vj/Parity-error-Screenshot-2024-01-11-201032.jpg" target="_blank" rel="noopener"&gt;Parity Error&lt;/A&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jan 2024 12:03:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204453#M184908</guid>
      <dc:creator>peterbatah</dc:creator>
      <dc:date>2024-01-13T12:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: POST Error: 283-Memory Address</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204462#M184913</link>
      <description>&lt;P&gt;Hi Peterbatah,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; I suggest to upgrade the system firmware by using &lt;A href="https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_ab56dbf228be4a80adfb576b2a" target="_blank" rel="noopener"&gt;SPP&lt;/A&gt;.&amp;nbsp; &amp;nbsp;It definitely works for you.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Please check the ILO logs about Fan running speed, Powersupply, processor and Temperature. These factors also may cause the system reboot.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Shiva_JR&lt;BR /&gt;Please give KUDOS and mark as 'Accepted solution' if my post worked.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 18:15:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204462#M184913</guid>
      <dc:creator>shiva_jr</dc:creator>
      <dc:date>2024-01-12T18:15:37Z</dc:date>
    </item>
    <item>
      <title>Re: POST Error: 283-Memory Address</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204486#M184916</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2067433"&gt;@shiva_jr&lt;/a&gt;&amp;nbsp;Thank you so much for following up with me. Much appreciated. My apologies for not acknowledging your response sooner as I have been preoccupied with the issue that I discussed in my original post. A few more details if I may:&lt;/P&gt;&lt;P&gt;1) System firmware was upgraded last week using P03093_001_spp-Gen8.1-SPPGen81.4. The link that you provided appears to be the Gen9 Service Pack&lt;/P&gt;&lt;P&gt;2) The server is located in a room whose temperature hovers between 10-15 degress celsius. Fans run anywhere between 6-13%&lt;/P&gt;&lt;P&gt;3) Yesterday I began running a complete systems diagnostic. Began at 16:45PM and was still running well past midnight. Will keep you posted.&lt;/P&gt;&lt;P&gt;4) Would you be kind enough to look over the log file once the diagnostics process has completed? What is odd is that the Test log does not show a memory error&lt;/P&gt;&lt;P&gt;Note: I came across the same POST Error: message approx. 1-5 weeks ago at which time I reseated the memory as suggested. I was hoping that would have resolved the issue but that was wishful thinking I suppose.&lt;/P&gt;&lt;P&gt;&lt;A href="https://i.postimg.cc/65frCwvM/Fan-Speed-2024-01-13.jpg" target="_blank" rel="noopener"&gt;Fan Speed&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://i.postimg.cc/2j4hfm2C/Sensor-Data-2024-01-13.jpg" target="_blank" rel="noopener"&gt;Sensor Data&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://i.postimg.cc/YSGLDwvK/Power-Supply-Summary-2024-01-13.jpg" target="_blank" rel="noopener"&gt;Power Supply Summary&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://i.postimg.cc/mZNz5jgD/Processor-Summary-2024-01-13.jpg" target="_blank" rel="noopener"&gt;Processor Summary&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 14 Jan 2024 01:05:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204486#M184916</guid>
      <dc:creator>peterbatah</dc:creator>
      <dc:date>2024-01-14T01:05:25Z</dc:date>
    </item>
    <item>
      <title>Re: POST Error: 283-Memory Address</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204512#M184918</link>
      <description>&lt;P&gt;Hello Peter,&lt;/P&gt;&lt;P&gt;Based on the error that is reported, this may require a DIMM replacement. We would request you to log a HPE Support ticket with the support team to get the DIMM replacement.&amp;nbsp;&lt;BR /&gt;Above recommendation is based on the troubleshooting steps that you have already attempted.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jan 2024 09:27:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/post-error-283-memory-address/m-p/7204512#M184918</guid>
      <dc:creator>SydUmar_1</dc:creator>
      <dc:date>2024-01-15T09:27:39Z</dc:date>
    </item>
  </channel>
</rss>

