<?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: Help required for fixing our primary ROM invalid in HPE ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019183#M164033</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The solution is to run the ROMPAQ utility to update the ROM.&lt;/P&gt;
&lt;DIV&gt;&lt;STRONG&gt;Error Message:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;REDUNDANT ROM ERROR: Primary ROM invalid. Booting Backup ROM. - ...&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;...run ROMPAQ to correct error condition&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Audible Beeps:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;None&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Possible Cause:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;The primary system ROM is corrupt. The system is booting from the redundant ROM.&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Action:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;Run ROMPaq Utility to restore the system ROM to the correct version.&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;&lt;STRONG&gt;Thank You!&lt;/STRONG&gt;&lt;BR /&gt;I am an HPE Employee&lt;BR /&gt;&lt;STRIKE&gt;&lt;A&gt;Useful Links for ProLiant Servers&lt;/A&gt;&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;[Moderator edit: Removed the broken link. Please refer to&amp;nbsp;&lt;A href="https://support.hpe.com/" target="_blank"&gt;https://support.hpe.com/&lt;/A&gt;]&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jan 2025 13:32:57 GMT</pubDate>
    <dc:creator>Suman_1978</dc:creator>
    <dc:date>2025-01-08T13:32:57Z</dc:date>
    <item>
      <title>Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7018889#M164001</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I wanted to apply the latest BIOS (version from 21/05/2018 - cp036547.exe) for our&amp;nbsp;ProLiant ML370 G6.&lt;/P&gt;&lt;P&gt;During the POST, I could notice the following error "REDUNDANT ROM ERROR: Primary ROM invalid. Booting backup rom. Run ROMPaq to correct error condition".&lt;/P&gt;&lt;P&gt;I then decided to try to create a bootable USB key media (ROMPaq) by using&amp;nbsp;SP99324.exe. When I run the HPEUSB.exe to format the USB key and create the bootable key, I have the following errors:&lt;/P&gt;&lt;P&gt;- syslinux.exe has crashed&lt;BR /&gt;- Take too long to execute.&lt;/P&gt;&lt;P&gt;I tried this from different machines with different OS (Win 7, 8.1, Server 2008 R2) but the same happened.&lt;/P&gt;&lt;P&gt;Do you see a way that would allow me to fix our primary ROM ?&lt;/P&gt;&lt;P&gt;Thank you by advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Sep 2018 14:47:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7018889#M164001</guid>
      <dc:creator>Dan8</dc:creator>
      <dc:date>2018-09-19T14:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019150#M164029</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Does the server Boot into OS post this error?&lt;BR /&gt;If YES, they why dont you flash the BIOS from the OS.&lt;/P&gt;
&lt;P&gt;If you can download a different type of ROM update file i.e.&amp;nbsp;System ROMPaq Firmware Upgrade for HP ProLiant ML370 G6/DL370 G6 (P63) Servers (For USB Key-Media) SP99324.exe&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=3884313&amp;amp;swItemId=MTX_37660617800b4f3db17cb11599&amp;amp;swEnvOid=4184" target="_blank" rel="noopener"&gt;https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=3884313&amp;amp;swItemId=MTX_37660617800b4f3db17cb11599&amp;amp;swEnvOid=4184&lt;/A&gt;&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;&lt;STRONG&gt;Thank You!&lt;/STRONG&gt;&lt;BR /&gt;I am an HPE Employee&lt;BR /&gt;&lt;BR /&gt;Was the post useful? Click on the white &lt;STRONG&gt;KUDOS! Thumb&lt;/STRONG&gt; below.&amp;nbsp; Kudos is a way of saying thank you to a post.&lt;BR /&gt;&lt;STRIKE&gt;&lt;A&gt;Useful Links for ProLiant Servers&lt;/A&gt;&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;[Moderator edit: Removed the broken link. Please refer to&amp;nbsp;&lt;A href="https://support.hpe.com/" target="_blank"&gt;https://support.hpe.com/&lt;/A&gt;]&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jan 2025 13:29:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019150#M164029</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2025-01-08T13:29:40Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019180#M164032</link>
      <description>&lt;P&gt;Hello &lt;SPAN class="lia-link-navigation lia-page-link lia-link-disabled lia-user-name-link"&gt;&lt;SPAN&gt;Suman,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-link-navigation lia-page-link lia-link-disabled lia-user-name-link"&gt;&lt;SPAN&gt;Yes, it boots into the OS after the POST. It loads the backup ROM.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-link-navigation lia-page-link lia-link-disabled lia-user-name-link"&gt;&lt;SPAN&gt;I initially did try to do the upgrade from the OS but it doesn't change anything; the same message appear during POST and so it loads the backup ROM (which is not updated).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-link-navigation lia-page-link lia-link-disabled lia-user-name-link"&gt;&lt;SPAN&gt;Do you see anyhting else that could be done to fix this ?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 08:52:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019180#M164032</guid>
      <dc:creator>Dan8</dc:creator>
      <dc:date>2018-09-21T08:52:26Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019183#M164033</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The solution is to run the ROMPAQ utility to update the ROM.&lt;/P&gt;
&lt;DIV&gt;&lt;STRONG&gt;Error Message:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;REDUNDANT ROM ERROR: Primary ROM invalid. Booting Backup ROM. - ...&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;...run ROMPAQ to correct error condition&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Audible Beeps:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;None&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Possible Cause:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;The primary system ROM is corrupt. The system is booting from the redundant ROM.&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Action:&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;Run ROMPaq Utility to restore the system ROM to the correct version.&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;&lt;STRONG&gt;Thank You!&lt;/STRONG&gt;&lt;BR /&gt;I am an HPE Employee&lt;BR /&gt;&lt;STRIKE&gt;&lt;A&gt;Useful Links for ProLiant Servers&lt;/A&gt;&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;[Moderator edit: Removed the broken link. Please refer to&amp;nbsp;&lt;A href="https://support.hpe.com/" target="_blank"&gt;https://support.hpe.com/&lt;/A&gt;]&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jan 2025 13:32:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7019183#M164033</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2025-01-08T13:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7022547#M164365</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What I find odd is that when applying the rpm P63 firmware update to the server which produced the 'invalid ROM' error as per op's post, the detection scripts picked up on this version (05.21.2018) and fully mitigated the vulnerabilities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please assist with the exact command to run the SP99324.exe from a linux command shell? &amp;nbsp;The file I downloaded according to the above link is OS independent. &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Sun, 21 Oct 2018 08:56:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7022547#M164365</guid>
      <dc:creator>holdenmagroin</dc:creator>
      <dc:date>2018-10-21T08:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7022569#M164368</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1941457"&gt;@holdenmagroin&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What I find odd is that when applying the rpm P63 firmware update to the server which produced the 'invalid ROM' error as per op's post, the detection scripts picked up on this version (05.21.2018) and fully mitigated the vulnerabilities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please assist with the exact command to run the SP99324.exe from a linux command shell? &amp;nbsp;The file I downloaded according to the above link is OS independent. &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The file you downloaded is indeed OS Independent&amp;nbsp;as it is meant&amp;nbsp;to&amp;nbsp;be run in an offline mode from a USB key.&amp;nbsp; &amp;nbsp;To run the update from within an RPM&amp;nbsp;based Linux distribution you can download this version and follow the instructions listed on the&amp;nbsp;web page&amp;nbsp;&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=3884313&amp;amp;swItemId=MTX_0ce9186ad60746e9aa1948a755&amp;amp;swEnvOid=4184#tab1" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=3884313&amp;amp;swItemId=MTX_0ce9186ad60746e9aa1948a755&amp;amp;swEnvOid=4184#tab1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 03:52:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7022569#M164368</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2018-10-22T03:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7035250#M165689</link>
      <description>&lt;P&gt;I have the same error (DL370 G6 as well) but when I've tried to run ROMPAQ utility from USB key I got error message: "There are no ROMA inage file on ROMAQ disk for the device you have selected" . After confirmation for Do you wnat to reprogram another ROM getting the same error.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2019 12:08:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7035250#M165689</guid>
      <dc:creator>temeraf</dc:creator>
      <dc:date>2019-02-19T12:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: Help required for fixing our primary ROM invalid</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7135893#M174731</link>
      <description>&lt;P&gt;Did tis get ever resolved? I am doing this right now and I am getting this same error.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 May 2021 00:33:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/help-required-for-fixing-our-primary-rom-invalid/m-p/7135893#M174731</guid>
      <dc:creator>Susan Hebel</dc:creator>
      <dc:date>2021-05-25T00:33:20Z</dc:date>
    </item>
  </channel>
</rss>

