Ignite restore error when configuring disks

[Todd Bowden]

Im using Ignite 3.3.116 for my ignite server and did a make_net_recovery to another server that completed successfully. Im trying to restore this same server across the network to do a restore, but it doesnt seem to work. So I threw in an HPUX 11.0 CD to boot off so I could then connect to the Ignite server to do the restore. I see strange problems when I try to do the restore, and they are as follows:

1. The first issue I see is the version of Ignite on the CD is different from Ignite version running on the server (I dont care, or should I care?). The error message I receive is :

ERROR: The version of Ignite-UX on the server you are using (B.3.3.116) is
different than the version of Ignite-UX that the client booted
(B.2.7.89). The versions must match in order to ensure correct
behavior. You may need to update the device you booted from with the
components found on the server.
Continuing the installation with a server version mismatch is likely
to cause indeterminate problems. Do you want to continue anyway? (y/[n]):
*
Response was: y

At this time I bring up the Ignite GUI on the server and the icon for this paticular system is red and I do not get the option to do a New Install (grayed out). I started thinking that there is a client_status file. I found and edited where it gave an error and changed it to complete, like so:

Boot_Client/Discover_System Complete
Boot_Client/Discover_System Complete (did say Error)
Waiting_To_Install Active

After this was changed the Icon turned gray and I could then proceed with an Install.

After I click on GO it bombs on "Configuring Disks" with this error message:

ERROR: Could not mount VxFS "/dev/vg00/lvol3" at "/d_cfg_mnt_sb61/": Invalid
argument (errno = 22).

I have never seen this problem before, has anyone else? I have done many ignite restores and this is the first that Ive see with this error. Usually I do a make_tape_recovery, but thought I would test with make_net_recovery to an Ignite Server to make the restore a little bit quicker. Obviously its a taking a little longer than expected.

Ignite Server is running HP-UX 11 with Ignite 3.3.116.

Any help is appreciated.

Todd Bowden

[Sandip Ghosh]

Actually it updates all the clients to the same version as the Ignite Server are , when it connect to the client first time.

I also heard the instances where the SCSI Instance get changed during the Ignite restore. And for that the device name also get changed and the ignite backup became unusable. Better use the latest ignite SW 3.6.xx and try it out. HP also knows about this problem. Can you please check the logs and see whether it is creating the same devices during Ignite installation?

Sandip

[Todd Bowden]

If we upgrade Ignite to 3.6.x on the cell server can we still use the backup that was created with 3.3.116?

Todd

[Todd Bowden]

Found this on HP's website:


Ignite recovery gets "Invalid argument (errno = 22)" error. DocId: UIUXKBRC00009260 Updated: 3/12/02 5:50:00 AM

PROBLEM
During an Ignite install of a recovery archive, this error is displayed
after loading the mini system and building the disk layout:

ERROR: Could not mount VxFS "/dev/vg00/lvol3" at "/d_cfg_mnt_sb61/":
Invalid argument (errno = 22).

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


RESOLUTION
This problem turned out to be an Ignite-UX version problem
with the boot helper and the Ignite-UX server.

The system was booted using an install cd as the boot
helper. It was then configured to use the built-in lan card
to boot from the server and the install proceeded without
error. Another option that would have worked would be to
either create a boot tape using make_boot_tape(1M)
or create another cd with the same revision of Ignite-UX
that the server has installed. To create a custom boot cd
the make_medialif -m -l LIF_FILE command could be used
and then the LIF_FILE could be burned onto a cd.