VPAR failed to boot after Data Migration

[Shukor]

Hi,

Our RP8400 running vpar and hpux v11.11. it's SAN boot disk (vg00) and after HDS done data migration, the vpar failed too boot up with below error. I believe the boot path was changed and how to set the new one and bring up the vpar1? Thanks..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# vparboot -p vpar1
vparboot: Booting vpar1. Please wait...
#
[vpar1]
Failed to open (0/0/8/0/0.1.58.0.0.0.0;)/stand/vmunix
Failed to load (0/0/8/0/0.1.58.0.0.0.0;)/stand/vmunix
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Torsten.]

data migration?

Ask them what changed (switch port, LUN number, etc.)

[Michael Steele_2]

HI

I'd like to verify your terminology first. You migrated data from one Hitachi disk array to another with a disk array application?

Question: Are you using SAN boot disks? If so, then their hardpaths have changed and you'll need to find them.

[freddy_21]

i think device path disknya already changes.

you must update boot disk path in vpar with vparmodify.


Regards
Freddy

[SoorajCleris]

Hi,

It seems like bootpath changed.
Mention the boot path at Vpmon prompt.

Regards,
Sooraj

[Shukor]

Hi experts,

During reseting the problem vpar, we can see new disk path (0/0/8/0/0.62.253.0.0.0.0;)

as waiting response form storage team for your questions (torsten, micheal), how we gonna set/vparboot/vparmodify to new boot path as said above?

[Torsten.]

If this is your new path, use vparmodify to delete the old boot device and add the new, e.g.

vparmodify -p ... -a io:0/0/8/0/0.62.253.0.0.0.0:BOOT

[Shukor]

Torsten,

I did but returned with this error. more details please see attached file.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.

[Torsten.]

Looks like the path is still wrong:

Either no physical volumes are attached or no valid VGDAs were found on the physical volumes.
Quorum not present, or some physical volume(s) are missing

[Torsten.]

Forgot to say - once the path is corrected, boot into single user mode and vgexport/import vg00 to reflect the changes.