<?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 problem loading Golden Image archive in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937532#M288388</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm running hpux 11.23 on itanium boxes. Running VXVM 4.1 and Ignite C.6.7.79. The ignite server is an rx1620 and the systems I'm loading are rx7620s. I am able to create a net recovery archive from a 7620 and load on other 7620 boxes without any issue (changing the mac address under /var/opt/ignite/clients). So there's no issue there.&lt;BR /&gt;&lt;BR /&gt;I'm also able to create a golden image archive with "make_sys_image". After configuring the INDEX and core11.cfg files on the ignite server I'm able to load the archive on another rx7620. However during the first reboot after the load I get the errors below.&lt;BR /&gt;&lt;BR /&gt;I spent a bit of time on troubleshooting and trying to change things around but I don't have a solution yet. Even tried to escape to the shell and install new/valid VXVM license keys for the host I'm loading and then reboot again, but that didn't work either.&lt;BR /&gt;&lt;BR /&gt;I was always able to setup golden image with LVM and even VXVM 3.5 and never really had many issues.&lt;BR /&gt;&lt;BR /&gt;Kind of stuck at this point. Since the network recovery archives are working with vxvm 4.1 I'm assuming the golden image should work but that it's probably some config issue.&lt;BR /&gt;&lt;BR /&gt;Any help appreciated - points will be promptly dealt!&lt;BR /&gt;&lt;BR /&gt;The error is below:&lt;BR /&gt;&lt;BR /&gt;-----------&lt;BR /&gt;&lt;BR /&gt;Loaded ACPI revision 2.0 tables.&lt;BR /&gt;NOTICE: cachefs_link(): File system was registered at index 4.&lt;BR /&gt;NOTICE: nfs3_link(): File system was registered at index 7.&lt;BR /&gt;Boot device's HP-UX HW path is: 0/0/0/3/0.5.0&lt;BR /&gt;igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 0/0/8/1/0/4&lt;BR /&gt;/0&lt;BR /&gt;&lt;BR /&gt;    System Console is on the Built-In Serial Interface&lt;BR /&gt;igelan1: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/1/1/0/4&lt;BR /&gt;/0&lt;BR /&gt;iether2: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-por&lt;BR /&gt;t 1000B-T Combo Adapter at hardware path 1/0/4/1/0/6/0&lt;BR /&gt;iether3: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-por&lt;BR /&gt;t 1000B-T Combo Adapter at hardware path 1/0/4/1/0/6/1&lt;BR /&gt;    Swap device table:  (start &amp;amp; size given in 512-byte blocks)&lt;BR /&gt;        entry 0 - major is 1, minor is 0x1; start = 0, size = 20480000&lt;BR /&gt;Starting the STREAMS daemons-phase 1&lt;BR /&gt;Difference in /dev/vx node values detected.&lt;BR /&gt;UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;unknown_fstyp (no matches)&lt;BR /&gt;UX:vxfs mount: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version&lt;BR /&gt;Root filesystem mounted R/W.&lt;BR /&gt;insf: Unable to lock /etc/ioconfig - : Cannot open /etc/ioconfig with specified&lt;BR /&gt;flags.&lt;BR /&gt;insf: Installing special files for pseudo driver vols&lt;BR /&gt;insf: Unable to lock /etc/ioconfig - : Cannot open /etc/ioconfig with specified&lt;BR /&gt;flags.&lt;BR /&gt;insf: Installing special files for pseudo driver dmp&lt;BR /&gt;insf: Can't make special file vx/dmpconfig: File exists&lt;BR /&gt;rm: /dev/vx/dsk/rootdg/standvol not removed.  Read-only file system&lt;BR /&gt;rm: /dev/vx/rdsk/rootdg/standvol not removed.  Read-only file system&lt;BR /&gt;mknod: File exists&lt;BR /&gt;mknod: File exists&lt;BR /&gt;Nodes in /dev/vx repopulated.&lt;BR /&gt;Starting vxconfigd in boot mode (pre_init_rc).&lt;BR /&gt;VxVM vxconfigd ERROR V-5-1-1589 enable failed: Configuration daemon error 19&lt;BR /&gt;        No such device; aborting&lt;BR /&gt;Checking root file system.&lt;BR /&gt;UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;unknown_fstyp (no matches)&lt;BR /&gt;Root check done.&lt;BR /&gt;VxVM vxdctl ERROR V-5-1-460 Cannot get pid for vxconfigd: No such file or direct&lt;BR /&gt;ory&lt;BR /&gt;vxdctl stop returned&lt;BR /&gt;Create STCP device files&lt;BR /&gt;Starting the STREAMS daemons-phase 2&lt;BR /&gt;     $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $&lt;BR /&gt;Memory Information:&lt;BR /&gt;    physical page size = 4096 bytes, logical page size = 4096 bytes&lt;BR /&gt;    Physical: 33512648 Kbytes, lockable: 25367480 Kbytes, available: 29502132 Kb&lt;BR /&gt;ytes&lt;BR /&gt;&lt;BR /&gt;VxVM vxconfigd ERROR V-5-1-1589 enable failed: Configuration daemon error 19&lt;BR /&gt;        No such device; aborting&lt;BR /&gt;VxVM vxvm-startup ERROR V-5-2-3655 Vold is not enabled for transactions&lt;BR /&gt;                No volumes started&lt;BR /&gt;WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (0x176c25c) encoun&lt;BR /&gt;tered. This device may be valid, but has not yet been configured in the kernel.&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/varvol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERROR: V-3-25742: sanity check failed: cannot open /dev/vx/dsk/roo&lt;BR /&gt;tdg/varvol: No such device or address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/varvol&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/tmpvol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERRORWARNING: VxVM vxio V-5-0-23 Open on an spurious volume device&lt;BR /&gt; (0x176c25b) encountered. This device may be valid, but has not yet been configu&lt;BR /&gt;red in the kernel.&lt;BR /&gt;: V-3-25742: sanity check failed: cannot open /dev/vx/dsk/rootdg/tmpvol: No such&lt;BR /&gt; device or address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/tmpvol&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/standvol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERROR: V-3-2WARNING: VxVM vxio V-5-0-23 Open on an spurious volume&lt;BR /&gt; device (0x176c258) encountered. This device may be valid, but has not yet been&lt;BR /&gt;configured in the kernel.&lt;BR /&gt;5742: sanity check failed: cannot open /dev/vx/dsk/rootdg/standvol: No such devi&lt;BR /&gt;ce or address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/standvol&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/homevol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERROR: V-3-25742:WARNING: VxVM vxio V-5-0-23 Open on an spurious v&lt;BR /&gt;olume device (0x176c25d) encountered. This device may be valid, but has not yet&lt;BR /&gt;been configured in the kernel.&lt;BR /&gt; sanity check failed: cannot open /dev/vx/dsk/rootdg/homevol: No such device or&lt;BR /&gt;address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/homevol&lt;BR /&gt;WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such&lt;BR /&gt;         file or directory (errno = 2)&lt;BR /&gt;ERROR:   phy_unit_init: Could not open file: /tmp/ign_configure/hw.info: No&lt;BR /&gt;         such file or directory (errno = 2)&lt;BR /&gt;WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such&lt;BR /&gt;         file or directory (errno = 2)&lt;BR /&gt;ERROR:   read_hw_info failed&lt;BR /&gt;WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such&lt;BR /&gt;         file or directory (errno = 2)&lt;BR /&gt;&lt;BR /&gt;         The configuration process has incurred an error, would you like&lt;BR /&gt;         to push a shell for debugging purposes? (y/[n]):</description>
    <pubDate>Fri, 02 Feb 2007 19:17:15 GMT</pubDate>
    <dc:creator>Vanja</dc:creator>
    <dc:date>2007-02-02T19:17:15Z</dc:date>
    <item>
      <title>problem loading Golden Image archive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937532#M288388</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm running hpux 11.23 on itanium boxes. Running VXVM 4.1 and Ignite C.6.7.79. The ignite server is an rx1620 and the systems I'm loading are rx7620s. I am able to create a net recovery archive from a 7620 and load on other 7620 boxes without any issue (changing the mac address under /var/opt/ignite/clients). So there's no issue there.&lt;BR /&gt;&lt;BR /&gt;I'm also able to create a golden image archive with "make_sys_image". After configuring the INDEX and core11.cfg files on the ignite server I'm able to load the archive on another rx7620. However during the first reboot after the load I get the errors below.&lt;BR /&gt;&lt;BR /&gt;I spent a bit of time on troubleshooting and trying to change things around but I don't have a solution yet. Even tried to escape to the shell and install new/valid VXVM license keys for the host I'm loading and then reboot again, but that didn't work either.&lt;BR /&gt;&lt;BR /&gt;I was always able to setup golden image with LVM and even VXVM 3.5 and never really had many issues.&lt;BR /&gt;&lt;BR /&gt;Kind of stuck at this point. Since the network recovery archives are working with vxvm 4.1 I'm assuming the golden image should work but that it's probably some config issue.&lt;BR /&gt;&lt;BR /&gt;Any help appreciated - points will be promptly dealt!&lt;BR /&gt;&lt;BR /&gt;The error is below:&lt;BR /&gt;&lt;BR /&gt;-----------&lt;BR /&gt;&lt;BR /&gt;Loaded ACPI revision 2.0 tables.&lt;BR /&gt;NOTICE: cachefs_link(): File system was registered at index 4.&lt;BR /&gt;NOTICE: nfs3_link(): File system was registered at index 7.&lt;BR /&gt;Boot device's HP-UX HW path is: 0/0/0/3/0.5.0&lt;BR /&gt;igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 0/0/8/1/0/4&lt;BR /&gt;/0&lt;BR /&gt;&lt;BR /&gt;    System Console is on the Built-In Serial Interface&lt;BR /&gt;igelan1: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/1/1/0/4&lt;BR /&gt;/0&lt;BR /&gt;iether2: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-por&lt;BR /&gt;t 1000B-T Combo Adapter at hardware path 1/0/4/1/0/6/0&lt;BR /&gt;iether3: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-por&lt;BR /&gt;t 1000B-T Combo Adapter at hardware path 1/0/4/1/0/6/1&lt;BR /&gt;    Swap device table:  (start &amp;amp; size given in 512-byte blocks)&lt;BR /&gt;        entry 0 - major is 1, minor is 0x1; start = 0, size = 20480000&lt;BR /&gt;Starting the STREAMS daemons-phase 1&lt;BR /&gt;Difference in /dev/vx node values detected.&lt;BR /&gt;UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;unknown_fstyp (no matches)&lt;BR /&gt;UX:vxfs mount: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version&lt;BR /&gt;Root filesystem mounted R/W.&lt;BR /&gt;insf: Unable to lock /etc/ioconfig - : Cannot open /etc/ioconfig with specified&lt;BR /&gt;flags.&lt;BR /&gt;insf: Installing special files for pseudo driver vols&lt;BR /&gt;insf: Unable to lock /etc/ioconfig - : Cannot open /etc/ioconfig with specified&lt;BR /&gt;flags.&lt;BR /&gt;insf: Installing special files for pseudo driver dmp&lt;BR /&gt;insf: Can't make special file vx/dmpconfig: File exists&lt;BR /&gt;rm: /dev/vx/dsk/rootdg/standvol not removed.  Read-only file system&lt;BR /&gt;rm: /dev/vx/rdsk/rootdg/standvol not removed.  Read-only file system&lt;BR /&gt;mknod: File exists&lt;BR /&gt;mknod: File exists&lt;BR /&gt;Nodes in /dev/vx repopulated.&lt;BR /&gt;Starting vxconfigd in boot mode (pre_init_rc).&lt;BR /&gt;VxVM vxconfigd ERROR V-5-1-1589 enable failed: Configuration daemon error 19&lt;BR /&gt;        No such device; aborting&lt;BR /&gt;Checking root file system.&lt;BR /&gt;UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system&lt;BR /&gt;unknown_fstyp (no matches)&lt;BR /&gt;Root check done.&lt;BR /&gt;VxVM vxdctl ERROR V-5-1-460 Cannot get pid for vxconfigd: No such file or direct&lt;BR /&gt;ory&lt;BR /&gt;vxdctl stop returned&lt;BR /&gt;Create STCP device files&lt;BR /&gt;Starting the STREAMS daemons-phase 2&lt;BR /&gt;     $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $&lt;BR /&gt;Memory Information:&lt;BR /&gt;    physical page size = 4096 bytes, logical page size = 4096 bytes&lt;BR /&gt;    Physical: 33512648 Kbytes, lockable: 25367480 Kbytes, available: 29502132 Kb&lt;BR /&gt;ytes&lt;BR /&gt;&lt;BR /&gt;VxVM vxconfigd ERROR V-5-1-1589 enable failed: Configuration daemon error 19&lt;BR /&gt;        No such device; aborting&lt;BR /&gt;VxVM vxvm-startup ERROR V-5-2-3655 Vold is not enabled for transactions&lt;BR /&gt;                No volumes started&lt;BR /&gt;WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (0x176c25c) encoun&lt;BR /&gt;tered. This device may be valid, but has not yet been configured in the kernel.&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/varvol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERROR: V-3-25742: sanity check failed: cannot open /dev/vx/dsk/roo&lt;BR /&gt;tdg/varvol: No such device or address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/varvol&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/tmpvol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERRORWARNING: VxVM vxio V-5-0-23 Open on an spurious volume device&lt;BR /&gt; (0x176c25b) encountered. This device may be valid, but has not yet been configu&lt;BR /&gt;red in the kernel.&lt;BR /&gt;: V-3-25742: sanity check failed: cannot open /dev/vx/dsk/rootdg/tmpvol: No such&lt;BR /&gt; device or address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/tmpvol&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/standvol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERROR: V-3-2WARNING: VxVM vxio V-5-0-23 Open on an spurious volume&lt;BR /&gt; device (0x176c258) encountered. This device may be valid, but has not yet been&lt;BR /&gt;configured in the kernel.&lt;BR /&gt;5742: sanity check failed: cannot open /dev/vx/dsk/rootdg/standvol: No such devi&lt;BR /&gt;ce or address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/standvol&lt;BR /&gt;mountall: cannot fsck /dev/vx/dsk/rootdg/homevol&lt;BR /&gt;mountall: diagnostics from fsck&lt;BR /&gt;UX:vxfs fsck: ERROR: V-3-25742:WARNING: VxVM vxio V-5-0-23 Open on an spurious v&lt;BR /&gt;olume device (0x176c25d) encountered. This device may be valid, but has not yet&lt;BR /&gt;been configured in the kernel.&lt;BR /&gt; sanity check failed: cannot open /dev/vx/dsk/rootdg/homevol: No such device or&lt;BR /&gt;address&lt;BR /&gt;mountall: cannot mount /dev/vx/dsk/rootdg/homevol&lt;BR /&gt;WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such&lt;BR /&gt;         file or directory (errno = 2)&lt;BR /&gt;ERROR:   phy_unit_init: Could not open file: /tmp/ign_configure/hw.info: No&lt;BR /&gt;         such file or directory (errno = 2)&lt;BR /&gt;WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such&lt;BR /&gt;         file or directory (errno = 2)&lt;BR /&gt;ERROR:   read_hw_info failed&lt;BR /&gt;WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such&lt;BR /&gt;         file or directory (errno = 2)&lt;BR /&gt;&lt;BR /&gt;         The configuration process has incurred an error, would you like&lt;BR /&gt;         to push a shell for debugging purposes? (y/[n]):</description>
      <pubDate>Fri, 02 Feb 2007 19:17:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937532#M288388</guid>
      <dc:creator>Vanja</dc:creator>
      <dc:date>2007-02-02T19:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: problem loading Golden Image archive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937533#M288389</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I've tried upgrading Ignite to the latest version C.6.10.97 then reran make_sys_image and configured the server and still got the same error as above after the 1st reboot.&lt;BR /&gt;&lt;BR /&gt;If anybody has seen this problem or has any idea as to how I can go about fixing it -  I'd really appreciate it.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Mon, 05 Feb 2007 12:32:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937533#M288389</guid>
      <dc:creator>Vanja</dc:creator>
      <dc:date>2007-02-05T12:32:26Z</dc:date>
    </item>
    <item>
      <title>Re: problem loading Golden Image archive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937534#M288390</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I can not find, but believe I read reports that there are issues with VxVM 4.1 and Ignite Golden images.&lt;BR /&gt;&lt;BR /&gt;The way to determine this is to try and use an older VxVM 3.5 image on the same hardware and see if it works.&lt;BR /&gt;&lt;BR /&gt;These errors seem to indicate a lack of support for some of the products you have built into the image. &lt;BR /&gt;&lt;BR /&gt;I've run into this problem before with earlier PA-RISC systems.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 05 Feb 2007 13:07:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937534#M288390</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-02-05T13:07:05Z</dc:date>
    </item>
    <item>
      <title>Re: problem loading Golden Image archive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937535#M288391</link>
      <description>Thanks for the follow up. Still can't get it to work with this particular image.&lt;BR /&gt;&lt;BR /&gt;I have since managed to use make_sys_image with this version of ignite with a straight HPUX 11.23 ia64 base vxvm 3.5 install and straight HPUX 11.23 ia64 base vxvm 4.1 install. No issues in creating or loading images.&lt;BR /&gt;&lt;BR /&gt;This system that is failing was originally vxvm3.5 upgraded to full vxvm 4.1. I have since wiped out all traces of 3.5, but still can't get the sys image to work.&lt;BR /&gt;&lt;BR /&gt;From talking to HP support I have gotten different answers but no resolution.&lt;BR /&gt;&lt;BR /&gt;1) SR 8606451706 that Ignite-UX versions C.6.5 or later has an issue handling this and it's documented if you force another reboot, the sergver should boot without issues. --- that didn't work&lt;BR /&gt;&lt;BR /&gt;2) Ignite-UX does NOT support having both vxvm 3.5 and 4.1 in the image.&lt;BR /&gt;&lt;BR /&gt;Anyway hope the info above helps somebody because I just wasn't able to get this particular image to work.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Vanja&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Feb 2007 14:11:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-loading-golden-image-archive/m-p/3937535#M288391</guid>
      <dc:creator>Vanja</dc:creator>
      <dc:date>2007-02-12T14:11:39Z</dc:date>
    </item>
  </channel>
</rss>

