problem loading Golden Image archive

[Vanja]

Hi,

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.

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.

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.

I was always able to setup golden image with LVM and even VXVM 3.5 and never really had many issues.

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.

Any help appreciated - points will be promptly dealt!

The error is below:

-----------

Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
Boot device's HP-UX HW path is: 0/0/0/3/0.5.0
igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 0/0/8/1/0/4
/0

System Console is on the Built-In Serial Interface
igelan1: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/1/1/0/4
/0
iether2: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-por
t 1000B-T Combo Adapter at hardware path 1/0/4/1/0/6/0
iether3: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-por
t 1000B-T Combo Adapter at hardware path 1/0/4/1/0/6/1
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 1, minor is 0x1; start = 0, size = 20480000
Starting the STREAMS daemons-phase 1
Difference in /dev/vx node values detected.
UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system
unknown_fstyp (no matches)
UX:vxfs mount: ERROR: V-3-20012: not a valid vxfs file system
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
Root filesystem mounted R/W.
insf: Unable to lock /etc/ioconfig - : Cannot open /etc/ioconfig with specified
flags.
insf: Installing special files for pseudo driver vols
insf: Unable to lock /etc/ioconfig - : Cannot open /etc/ioconfig with specified
flags.
insf: Installing special files for pseudo driver dmp
insf: Can't make special file vx/dmpconfig: File exists
rm: /dev/vx/dsk/rootdg/standvol not removed. Read-only file system
rm: /dev/vx/rdsk/rootdg/standvol not removed. Read-only file system
mknod: File exists
mknod: File exists
Nodes in /dev/vx repopulated.
Starting vxconfigd in boot mode (pre_init_rc).
VxVM vxconfigd ERROR V-5-1-1589 enable failed: Configuration daemon error 19
No such device; aborting
Checking root file system.
UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system
unknown_fstyp (no matches)
Root check done.
VxVM vxdctl ERROR V-5-1-460 Cannot get pid for vxconfigd: No such file or direct
ory
vxdctl stop returned
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 33512648 Kbytes, lockable: 25367480 Kbytes, available: 29502132 Kb
ytes

VxVM vxconfigd ERROR V-5-1-1589 enable failed: Configuration daemon error 19
No such device; aborting
VxVM vxvm-startup ERROR V-5-2-3655 Vold is not enabled for transactions
No volumes started
WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (0x176c25c) encoun
tered. This device may be valid, but has not yet been configured in the kernel.
mountall: cannot fsck /dev/vx/dsk/rootdg/varvol
mountall: diagnostics from fsck
UX:vxfs fsck: ERROR: V-3-25742: sanity check failed: cannot open /dev/vx/dsk/roo
tdg/varvol: No such device or address
mountall: cannot mount /dev/vx/dsk/rootdg/varvol
mountall: cannot fsck /dev/vx/dsk/rootdg/tmpvol
mountall: diagnostics from fsck
UX:vxfs fsck: ERRORWARNING: VxVM vxio V-5-0-23 Open on an spurious volume device
(0x176c25b) encountered. This device may be valid, but has not yet been configu
red in the kernel.
: V-3-25742: sanity check failed: cannot open /dev/vx/dsk/rootdg/tmpvol: No such
device or address
mountall: cannot mount /dev/vx/dsk/rootdg/tmpvol
mountall: cannot fsck /dev/vx/dsk/rootdg/standvol
mountall: diagnostics from fsck
UX:vxfs fsck: ERROR: V-3-2WARNING: VxVM vxio V-5-0-23 Open on an spurious volume
device (0x176c258) encountered. This device may be valid, but has not yet been
configured in the kernel.
5742: sanity check failed: cannot open /dev/vx/dsk/rootdg/standvol: No such devi
ce or address
mountall: cannot mount /dev/vx/dsk/rootdg/standvol
mountall: cannot fsck /dev/vx/dsk/rootdg/homevol
mountall: diagnostics from fsck
UX:vxfs fsck: ERROR: V-3-25742:WARNING: VxVM vxio V-5-0-23 Open on an spurious v
olume device (0x176c25d) encountered. This device may be valid, but has not yet
been configured in the kernel.
sanity check failed: cannot open /dev/vx/dsk/rootdg/homevol: No such device or
address
mountall: cannot mount /dev/vx/dsk/rootdg/homevol
WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such
file or directory (errno = 2)
ERROR: phy_unit_init: Could not open file: /tmp/ign_configure/hw.info: No
such file or directory (errno = 2)
WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such
file or directory (errno = 2)
ERROR: read_hw_info failed
WARNING: Could not open default log file: /tmp/ign_configure/log_file: No such
file or directory (errno = 2)

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]):

[Vanja]

Hi,

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.

If anybody has seen this problem or has any idea as to how I can go about fixing it - I'd really appreciate it.

Thanks!

[Steven E. Protter · Accepted solution]

Shalom,

I can not find, but believe I read reports that there are issues with VxVM 4.1 and Ignite Golden images.

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.

These errors seem to indicate a lack of support for some of the products you have built into the image.

I've run into this problem before with earlier PA-RISC systems.

SEP

[Vanja]

Thanks for the follow up. Still can't get it to work with this particular image.

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.

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.

From talking to HP support I have gotten different answers but no resolution.

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

2) Ignite-UX does NOT support having both vxvm 3.5 and 4.1 in the image.

Anyway hope the info above helps somebody because I just wasn't able to get this particular image to work.

Thanks,
Vanja