<?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: Ignite Server Issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985042#M420701</link>
    <description>Hi Guru's&lt;BR /&gt;&lt;BR /&gt;Anyone please ???&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Help me ???&lt;BR /&gt;&lt;BR /&gt;Its urgent&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Arunkumar.B</description>
    <pubDate>Tue, 13 Jun 2006 08:35:40 GMT</pubDate>
    <dc:creator>Arunkumar.B</dc:creator>
    <dc:date>2006-06-13T08:35:40Z</dc:date>
    <item>
      <title>Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985041#M420700</link>
      <description>Hi Guru's,&lt;BR /&gt;&lt;BR /&gt;I am having two superdomes with 3 npar each &amp;amp; 9 vpars in each superdome.&lt;BR /&gt;&lt;BR /&gt;Sd1 vpars are configured as ignite Client in SD2.&lt;BR /&gt;&lt;BR /&gt;SD2 vpars are configured as ignite client in SD1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Now One of My vpar configured as ignite server in SD2 primary disk is giving I/O error.My alternate mirror disk in that vpars physical extent 0000(lvol1) shows stale.&lt;BR /&gt;&lt;BR /&gt;When i tried to take ignite backup from sd2 to sd1.Its giving completed with warning saying that VPMON I/0 error.&lt;BR /&gt;&lt;BR /&gt;Now the sd2 ignite server vpar running fine with I/O error Primary disk &amp;amp; alternate root disk with 0000 physical extents as stale.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How should i change my Primary root disk&lt;BR /&gt;&lt;BR /&gt;1)should i try with Ignite backup completed with warning (vpmon I/O error)&lt;BR /&gt;&lt;BR /&gt;2)Should i mirror from the secondry disk which is having stale in physical extents 0000&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Arunkumar.B</description>
      <pubDate>Tue, 13 Jun 2006 07:47:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985041#M420700</guid>
      <dc:creator>Arunkumar.B</dc:creator>
      <dc:date>2006-06-13T07:47:40Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985042#M420701</link>
      <description>Hi Guru's&lt;BR /&gt;&lt;BR /&gt;Anyone please ???&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Help me ???&lt;BR /&gt;&lt;BR /&gt;Its urgent&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Arunkumar.B</description>
      <pubDate>Tue, 13 Jun 2006 08:35:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985042#M420701</guid>
      <dc:creator>Arunkumar.B</dc:creator>
      <dc:date>2006-06-13T08:35:40Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985043#M420702</link>
      <description>I would suggest you to try booting from alternate disk, I suspect because of primary disk became bad alternate disk developed some stale extents. So there won't be a problem while booting from alternate disk.&lt;BR /&gt;it gave warning vpmon I/o error because of the I/O error on primary disk so restoring this would be a second option.</description>
      <pubDate>Tue, 13 Jun 2006 08:38:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985043#M420702</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2006-06-13T08:38:36Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985044#M420703</link>
      <description>Arun,&lt;BR /&gt;&lt;BR /&gt;Try to boot from alternate disk as because of IO erros on prmiary disk we recd vpmon io error. It depends that which physical extents has gone bad so whether server will boot with ignite restore or not.&lt;BR /&gt;&lt;BR /&gt;Botting from alternate disk won't be an issue else what is the purpose of having mirror disk on the servers.</description>
      <pubDate>Tue, 13 Jun 2006 08:47:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985044#M420703</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2006-06-13T08:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985045#M420704</link>
      <description>HI Midhal,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanx for ur reply.Just now i tried that one.&lt;BR /&gt;&lt;BR /&gt;vparboot -p neptune -B ALTBOOT -o "-lq"&lt;BR /&gt;&lt;BR /&gt;It is throwing me the error&lt;BR /&gt;&lt;BR /&gt;"can't boot /stand/vmunix"&lt;BR /&gt;neptune halted&lt;BR /&gt;&lt;BR /&gt;Is there any other way ???&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jun 2006 09:09:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985045#M420704</guid>
      <dc:creator>Arunkumar.B</dc:creator>
      <dc:date>2006-06-13T09:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985046#M420705</link>
      <description>If you can't boot to primary then:&lt;BR /&gt;&lt;BR /&gt;1a) reboot and interupt the boot process&lt;BR /&gt;1b) sea ipl (* check for bootable devices and verify that an alternate exists&lt;BR /&gt;1c) bo alt (* is exists&lt;BR /&gt;&lt;BR /&gt;If no alt exists and you're able to boot to run level one:&lt;BR /&gt;&lt;BR /&gt;2a) umount /stand&lt;BR /&gt;fsck -p /dev/vg00/rlvol1 (* check for bad sectors for example then bad disk *)&lt;BR /&gt;&lt;BR /&gt;2b) #dd if=/dev/rdsk/cxtydx of=/dev/null bs=1024k  (* check bad disk for failure *)&lt;BR /&gt;&lt;BR /&gt;If fsck OK but still can't boot and probably if you just rebuilt the kernel, like with new patches *)&lt;BR /&gt;&lt;BR /&gt;3)  reboot and interact with IPL&lt;BR /&gt;&lt;BR /&gt;ISL &amp;gt; hpux -ll /stand/system (* verify vmunix.prev&lt;BR /&gt;&lt;BR /&gt;ISL &amp;gt; hpux /stand/vmunix.prev (* boot from vmunix.prev&lt;BR /&gt;&lt;BR /&gt;4) If still fails then call HW and get your latest ignite tape and prepare to recover.</description>
      <pubDate>Tue, 13 Jun 2006 09:51:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985046#M420705</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2006-06-13T09:51:48Z</dc:date>
    </item>
    <item>
      <title>Re: Ignite Server Issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985047#M420706</link>
      <description>We Got it work without Ignite restore&lt;BR /&gt;&lt;BR /&gt;1)stale in the secondry PE 0000&lt;BR /&gt;2)Ignite Restoration failed with errors&lt;BR /&gt;&lt;BR /&gt;Here is the scoop&lt;BR /&gt;1)mirrored all lvol's except lvol1 (Stand)&lt;BR /&gt;2)created new lvol mounted as standbak in the secondry&lt;BR /&gt;3)copy the stand directory to standbak&lt;BR /&gt;4)copied vpmon from another vpar&lt;BR /&gt;5)then normal lvlnboot,booted with alt successfully.&lt;BR /&gt;6)Replaced the primary then vgcfgrestore &amp;amp; dd lvolbak to lvol1&lt;BR /&gt;7)onceagain lvlnboot&lt;BR /&gt;&lt;BR /&gt;Started working Fine&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thankx guys for ur Help&lt;BR /&gt;&lt;BR /&gt;Arunkumar.B</description>
      <pubDate>Fri, 16 Jun 2006 02:39:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ignite-server-issue/m-p/4985047#M420706</guid>
      <dc:creator>Arunkumar.B</dc:creator>
      <dc:date>2006-06-16T02:39:41Z</dc:date>
    </item>
  </channel>
</rss>

