errors with vparboot -I

[Peter Heinemann]

Here's the config:
# vparstatus -M
pa2tora1:Up:Dynamic,Autoboot:/stand/vmunix::4/4;1.10,1.11,1.12,1.13;;:1.0.0,1.0.8,1.0.0.2.0.6.0.0.0.0.0 BOOT:;4096:N
pa2tapp1:Up:Dynamic,Autoboot:/stand/vmunix::2/2;2.10,2.11;;:1.0.10,1.0.14,1.0.10.0.0.100.71.19.0.3.4 BOOT:;2048:N
pa2qapp2:Down:Dynamic,Autoboot:/stand/vmunix::2/2;2.12,2.13;;:1.0.12,1.0.4,1.0.4.0.0.100.16.19.0.3.5 BOOT:;2048:N

When I specify vparboot, various errors:
# vparboot -p pa2qapp2 -I 10.76.206.69,/opt/boot/ignite/WINSTALL
vparboot: Booting pa2qapp2. Please wait...
vparboot: Internal error: Cannot boot virtual partition pa2qapp2. (Code 2,21)

If I leave off the path, a slightly different "Code":
# vparboot -p pa2qapp2 -I 10.76.206.69
vparboot: Booting pa2qapp2. Please wait...
vparboot: Internal error: Cannot boot virtual partition pa2qapp2. (Code 2,4)

Anyone have any ideas? The ignite server is in the same subnet (it's actually the "host" vpar).
...thx
...Peter

[Peter Heinemann]

additional info:
just for grins, I tried non-install boot (expecting failure, as the disk doesn't yet have hp-ux):

# vparboot -p pa2qapp2
vparboot: Booting pa2qapp2. Please wait...

root@pa2tora1:/root
# Failed to open (1/0/4/0/0.100.16.19.0.3.5;)/stand/vmunix
Failed to load (1/0/4/0/0.100.16.19.0.3.5;)/stand/vmunix

It would appear that the vpar config is ok for this new system -- it could in fact go out and touch the assigned boot disk.

[Kevin_31]

I've got the exact same errors on my vPar. Seems I've screwed up the boot sector, on the vPar boot disk, but I'm really surprised that I can't reignite the vPar from scratch. I've tried rebooting the entire machine and vparremoving and re-vparcreating the dodgy vPar--to no avail.

I see this was posted in January, did you find the solution yourself? Did you get it fixed by logging a support call with HP?

I'd love to learn more from anyone about this error.

cheers,
Kevin

[Kevin_31]

At first attempt HP say the error message is to do with resolving name/ip address. Since we both are using IP address and the name doesn't need resolving that's ovbiously bogus.

The next thing HP said was that it was to do with contacting the ignite server. I verified I could do that from this server, so now the call is being passed around internally within HP.

[Peter Heinemann]

We're running vpars vers A.02; HP indicates it's a version problem and works in A.03. we'll test it out once we get a test system freed up.

[Michelle Weiss]

Any resolution updates on this case? What worked for you?

[Peter Heinemann]

After upgrading to vpars A.03, we're much farther along -- it's able to boot into the interactive script, and now I just need to solve some garden-variety Ignite setup issues.

So the A.03 upgrade is definitely the right step, if you can locate the install/upgrade CD. We've been having a heck of a time locating an "official" copy from HP, even though we purchased full support for vpars, and had to used borrowed ones.

[Michelle Weiss]

Thank you Peter, and thanks for the quick response time!

[Peter Heinemann]

Restore successful but VERY slow. Hoping to get some more info. out of this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=594453

Make sure you follow the steps in the A.03 version of the manual. They changed from the earlier versions.

Points would be nice, too...

[Michelle Weiss]

I really appreciate your info Peter - it absolutely worked for me! Unfortunately since I'm not the author on this post I can't assign points, sorry...