<?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 Superdome fail to  boot in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571297#M6090</link>
    <description>There is an issue while booting HP-UX 11.23,IA64 HP SUPERDOME SERVER SD64B.&lt;BR /&gt;It became panic twice while it is try to start netbackup service.&lt;BR /&gt;&lt;BR /&gt;Starting NetBackup ...................................FAIL Calling function e0000000011932c0 for Shutdown State 8 type 0x2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Could you help me please.</description>
    <pubDate>Tue, 26 Jan 2010 08:31:49 GMT</pubDate>
    <dc:creator>hello everybody</dc:creator>
    <dc:date>2010-01-26T08:31:49Z</dc:date>
    <item>
      <title>Superdome fail to  boot</title>
      <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571297#M6090</link>
      <description>There is an issue while booting HP-UX 11.23,IA64 HP SUPERDOME SERVER SD64B.&lt;BR /&gt;It became panic twice while it is try to start netbackup service.&lt;BR /&gt;&lt;BR /&gt;Starting NetBackup ...................................FAIL Calling function e0000000011932c0 for Shutdown State 8 type 0x2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Could you help me please.</description>
      <pubDate>Tue, 26 Jan 2010 08:31:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571297#M6090</guid>
      <dc:creator>hello everybody</dc:creator>
      <dc:date>2010-01-26T08:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: Superdome fail to  boot</title>
      <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571298#M6091</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;boot to single user mode and disable netbackup start.&lt;BR /&gt;&lt;BR /&gt;them start to normal mode, and check the system, for some errors ....&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Tue, 26 Jan 2010 08:44:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571298#M6091</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2010-01-26T08:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: Superdome fail to  boot</title>
      <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571299#M6092</link>
      <description>Disable Netbackup service by renaming /sbin/init.d/netbackup to some othere name and till where it goes in booting...&lt;BR /&gt;Is netbackup client is recently updated on the box?</description>
      <pubDate>Tue, 26 Jan 2010 08:46:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571299#M6092</guid>
      <dc:creator>TARUN SHARMA_1</dc:creator>
      <dc:date>2010-01-26T08:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: Superdome fail to  boot</title>
      <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571300#M6093</link>
      <description>disable the netbackup service in the single user mode and boot the system.if still not coming up lock the call with HP vendor.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Good luck</description>
      <pubDate>Tue, 26 Jan 2010 08:50:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571300#M6093</guid>
      <dc:creator>Jupinder Bedi</dc:creator>
      <dc:date>2010-01-26T08:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: Superdome fail to  boot</title>
      <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571301#M6094</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;vhats is the reason why you needed to start the system again.&lt;BR /&gt;&lt;BR /&gt;did you patch the system ??? If yes, you should know that some patches are making the Netbackup unusable.&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Tue, 26 Jan 2010 09:31:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571301#M6094</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2010-01-26T09:31:39Z</dc:date>
    </item>
    <item>
      <title>Re: Superdome fail to  boot</title>
      <link>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571302#M6095</link>
      <description>"...Multiple MCAs/INITs..." &lt;BR /&gt;&lt;BR /&gt;I wouldn't touch this with a 10 foot pole and neither should you.  You should be calling HP HW support.&lt;BR /&gt;&lt;BR /&gt;There is no way you can determine what is wrong without further event log information, which is going to report "...Multiple MCAs...".  As "...Multiple MCAs..." were reported to the console.&lt;BR /&gt;&lt;BR /&gt;And MCA event in IA64 archictecture is similar to an HPMC event in PA Risc.  A CPU or a DIMM is usually involved and needs replacement.  It is a catastrophic event that requires an HP CE.&lt;BR /&gt;&lt;BR /&gt;But because of the cell organization of a superdome only the partitions on the bad cell are affected, yet the entire box and every partition in this superdome are down.  This doesn't happen.  If you've got a 4 cell dome, then the partitions on the other three good cells should still be up.&lt;BR /&gt;&lt;BR /&gt;Something catastrophic has occurrred. &lt;BR /&gt;&lt;BR /&gt;Call HP.</description>
      <pubDate>Tue, 26 Jan 2010 10:04:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/superdome-fail-to-boot/m-p/4571302#M6095</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2010-01-26T10:04:19Z</dc:date>
    </item>
  </channel>
</rss>

