<?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: Question on /stand/bootconf in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154552#M502579</link>
    <description>Thank you all for the information.  That is  exactly what I was looking for.</description>
    <pubDate>Wed, 04 Feb 2009 15:33:56 GMT</pubDate>
    <dc:creator>Bill Costigan</dc:creator>
    <dc:date>2009-02-04T15:33:56Z</dc:date>
    <item>
      <title>Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154546#M502573</link>
      <description>I'm trying to understand what /stand/bootconf is used for.  Or to put it another way - what will break if boodconf is not correct.  For example, what if only the first disk of a mirrored root drive is in the bootconf file.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 03 Feb 2009 21:36:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154546#M502573</guid>
      <dc:creator>Bill Costigan</dc:creator>
      <dc:date>2009-02-03T21:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154547#M502574</link>
      <description>Hi Bill:&lt;BR /&gt;&lt;BR /&gt;It holds the boot disk device files so that 'swinstall' can find and update the boot loader if necessary.  See the manpages :&lt;BR /&gt;&lt;BR /&gt;# man bootconf(4)&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 03 Feb 2009 21:54:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154547#M502574</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-02-03T21:54:48Z</dc:date>
    </item>
    <item>
      <title>Re: Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154548#M502575</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt;When you say swinstall, is that swinstall that I might be running to install patches on an already running server? And bootconf tells it all the disks that need to be updated if a patch changes some file in the LIF area?&lt;BR /&gt;&lt;BR /&gt;Or is this an swinstall / hpux install that is being used to initially install a new system on a fresh set of disks? There are some posts about make_tape_recovery using this file, but I was sure what it was using it for.</description>
      <pubDate>Tue, 03 Feb 2009 22:15:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154548#M502575</guid>
      <dc:creator>Bill Costigan</dc:creator>
      <dc:date>2009-02-03T22:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154549#M502576</link>
      <description>Hi (again) Bill:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; When you say swinstall, is that swinstall that I might be running to install patches on an already running server? &lt;BR /&gt;&lt;BR /&gt;Yes.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Feb 2009 22:21:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154549#M502576</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-02-03T22:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154550#M502577</link>
      <description>From the man pages:&lt;BR /&gt;&lt;BR /&gt;This file, /stand/bootfonf, contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the Software Distributor and HP-UX kernel control scripts (fileset OS-Core.KERN-RUN) to determine how and where to update the initial boot loader.  Normally the kernel's checkinstall script queries the system's hardware and creates the file.  In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the /stand/bootconf file manually.&lt;BR /&gt;&lt;BR /&gt;RegardS!</description>
      <pubDate>Tue, 03 Feb 2009 22:23:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154550#M502577</guid>
      <dc:creator>Andres_13</dc:creator>
      <dc:date>2009-02-03T22:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154551#M502578</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;On average, about 90% of all HP-UX servers I&lt;BR /&gt;check or get access to, have incorrect&lt;BR /&gt;or incomplete /stand/bootconf.&lt;BR /&gt;&lt;BR /&gt;Very often, mirrors are not listed in this&lt;BR /&gt;file. The accuracy and importance of&lt;BR /&gt;/stand/bootconf tends to be a forgotten&lt;BR /&gt;issue.&lt;BR /&gt; &lt;BR /&gt;Where mirrors exist, the /stand/bootconf&lt;BR /&gt;MUST have its own line for each of the&lt;BR /&gt;mirrors (LVM or VxVM). &lt;BR /&gt;&lt;BR /&gt;/stand/bootconf is used by SD-UX and kernel&lt;BR /&gt;control scripts to determine how and where&lt;BR /&gt;to update the boot loader. &lt;BR /&gt;&lt;BR /&gt;The /stand/bootconf file contains the&lt;BR /&gt;address and disk layout type of the system's&lt;BR /&gt;boot devices. It is used by the HP-UX kernel&lt;BR /&gt;control script (fileset OS-Core.KERN-RUN) to&lt;BR /&gt;determine how and where to update the&lt;BR /&gt;initial boot loader. &lt;BR /&gt;&lt;BR /&gt;Where /stand/bootconf becomes so "visible"?&lt;BR /&gt;&lt;BR /&gt;Here are real-life examples of problems and&lt;BR /&gt;disasters:&lt;BR /&gt;&lt;BR /&gt;A) Ignite reports an error "not a LIF&lt;BR /&gt;volume".&lt;BR /&gt;&lt;BR /&gt;B) Patch upgrade or O/S upgrade (for&lt;BR /&gt;example, from 11.00 to 11.11) can leave the&lt;BR /&gt;server unbootable:&lt;BR /&gt;&lt;BR /&gt;The preinstall script will read each line in&lt;BR /&gt;the bootconf file, look at the device file&lt;BR /&gt;specified, and verify that it is bootable.&lt;BR /&gt;If it can't find a bootable disk in any of&lt;BR /&gt;the entries in bootconf, the install of that&lt;BR /&gt;fileset will fail. If it finds a bootable&lt;BR /&gt;disk, the install will proceed. You can&lt;BR /&gt;verify this by looking at the file /var/adm/sw/products/OS-Core/KERN-RUN/preinstall,&lt;BR /&gt;as an example.&lt;BR /&gt;&lt;BR /&gt;Let's say a single entry in /etc/bootconf&lt;BR /&gt;file pointed to the wrong disk (it didn't&lt;BR /&gt;point to a correct boot disk). The admin&lt;BR /&gt;starts the upgrade from the command line,&lt;BR /&gt;sees that XYZ filesets were going to be&lt;BR /&gt;installed, and goes away. Of the XYZ&lt;BR /&gt;filesets, number of them are kernel&lt;BR /&gt;filesets. &lt;BR /&gt;&lt;BR /&gt;Since the bootconf file is incorrect, the&lt;BR /&gt;analysis of the kernel filesets fails and&lt;BR /&gt;they are not installed while the other&lt;BR /&gt;non-kernel filesets are installed. This&lt;BR /&gt;leaves the server with half its filesets&lt;BR /&gt;11.00 (the kernel filesets) and the other&lt;BR /&gt;half 11.11 (non-kernel filesets), making it&lt;BR /&gt;unusable!!!&lt;BR /&gt;&lt;BR /&gt;So, please ensure that /stand/bootconf&lt;BR /&gt;contains right information.&lt;BR /&gt;&lt;BR /&gt;For that very reason, my Perl script&lt;BR /&gt;check contents of /stand/bootconf&lt;BR /&gt;and reports errors if it is not&lt;BR /&gt;in proper state:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.circlingcycle.com.au/Unix-sources/HP-UX-check-OAT.pl.txt" target="_blank"&gt;http://www.circlingcycle.com.au/Unix-sources/HP-UX-check-OAT.pl.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For example:&lt;BR /&gt;&lt;BR /&gt;AUDIT-PASS: Boot disk /dev/disk/disk3_p2 listed in /stand/bootconf&lt;BR /&gt;AUDIT-PASS: Boot disk /dev/disk/disk4_p2 listed in /stand/bootconf&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;VK2COT</description>
      <pubDate>Wed, 04 Feb 2009 02:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154551#M502578</guid>
      <dc:creator>VK2COT</dc:creator>
      <dc:date>2009-02-04T02:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: Question on /stand/bootconf</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154552#M502579</link>
      <description>Thank you all for the information.  That is  exactly what I was looking for.</description>
      <pubDate>Wed, 04 Feb 2009 15:33:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-stand-bootconf/m-p/5154552#M502579</guid>
      <dc:creator>Bill Costigan</dc:creator>
      <dc:date>2009-02-04T15:33:56Z</dc:date>
    </item>
  </channel>
</rss>

