<?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: vPar boot issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117697#M447243</link>
    <description>well that depends. if your origional vpar creation was correct, then recreating it will make no difference. What matters here is that you have a boot disk that is installed correctly, including having the Vpars software on it, and that your vpar creation points to the correct device, with the correct syntax, i.e. teh :BOOT option added at the end of teh hardware path.&lt;BR /&gt;</description>
    <pubDate>Mon, 07 Jul 2008 06:06:52 GMT</pubDate>
    <dc:creator>melvyn burnard</dc:creator>
    <dc:date>2008-07-07T06:06:52Z</dc:date>
    <item>
      <title>vPar boot issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117693#M447239</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I'm new in vPar's. I have create two vPars (vPar1 and vPar2) in a rx8640. The first vpar boot normally no problem...just stay to slow when i'm writing on HP-UX. Then i have installed on npar mode a second hp-ux boot disk with the dvd's (i tried the make_recovery but something has gone wrong and the installations was with problems) Now when i boot on vPar mode the first vpar boot normally but the second don't boot and gives a message that can't find the boot disk. I have perform a vparinfo vPar2 and the boot disk is the one i have created. &lt;BR /&gt;&lt;BR /&gt;Can someone help me?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Márcio</description>
      <pubDate>Sat, 05 Jul 2008 11:59:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117693#M447239</guid>
      <dc:creator>MárcioAFM</dc:creator>
      <dc:date>2008-07-05T11:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: vPar boot issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117694#M447240</link>
      <description>Hi Marcio:&lt;BR /&gt;&lt;BR /&gt;I'll need to see your procedure in order to help you.  I'll also need to see the exact error message.  You'll have to copy and paste the error message into the thread.  You'll find these messages in /var/tmp on the first vPar.  You can use 'ls -lart' to list out /var/tmp in cronological order.  The file will look something like this:&lt;BR /&gt;&lt;BR /&gt;/var/tmp/VPAAAa08035</description>
      <pubDate>Sat, 05 Jul 2008 13:00:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117694#M447240</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2008-07-05T13:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: vPar boot issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117695#M447241</link>
      <description>also give us the output of vparstatus (verbose) for the second vpar.&lt;BR /&gt;</description>
      <pubDate>Sun, 06 Jul 2008 07:58:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117695#M447241</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2008-07-06T07:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: vPar boot issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117696#M447242</link>
      <description>Hello again,&lt;BR /&gt;&lt;BR /&gt;I'm not in the server until monday, anyway... i think the problem is that a create the vpar2 without the OS installed on the boot disk. The solution maybe is from vPar1 remove vPar2 then create the vpar2 again.&lt;BR /&gt;&lt;BR /&gt;Think is a good idea?&lt;BR /&gt;&lt;BR /&gt;Regards and thank you&lt;BR /&gt;&lt;BR /&gt;MÃ¡rcio</description>
      <pubDate>Sun, 06 Jul 2008 16:55:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117696#M447242</guid>
      <dc:creator>MárcioAFM</dc:creator>
      <dc:date>2008-07-06T16:55:41Z</dc:date>
    </item>
    <item>
      <title>Re: vPar boot issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117697#M447243</link>
      <description>well that depends. if your origional vpar creation was correct, then recreating it will make no difference. What matters here is that you have a boot disk that is installed correctly, including having the Vpars software on it, and that your vpar creation points to the correct device, with the correct syntax, i.e. teh :BOOT option added at the end of teh hardware path.&lt;BR /&gt;</description>
      <pubDate>Mon, 07 Jul 2008 06:06:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117697#M447243</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2008-07-07T06:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: vPar boot issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117698#M447244</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thank you for the help!&lt;BR /&gt;&lt;BR /&gt;I solved the problem with this:&lt;BR /&gt;&lt;BR /&gt;vparload -p vPar2 -E 0 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Márcio</description>
      <pubDate>Tue, 08 Jul 2008 17:33:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vpar-boot-issue/m-p/5117698#M447244</guid>
      <dc:creator>MárcioAFM</dc:creator>
      <dc:date>2008-07-08T17:33:24Z</dc:date>
    </item>
  </channel>
</rss>

