Creating a new vPar

[S.Rider]

We have a SuperDome with a couple nPars with vPars under them. We want to avoid taking down the current systems, but want to add another vPar on a new set of disks.
What we tried was dd'ing a functioning root disk from an exsisting vpar to a new disk, then creating a new vpar and booting it. When it trys to bot the copied disk, it panics.
WARNING: ROOT device 0x1f090002 is a non-LVM partition, disallowed on LVM disk.
WARNING: ROOT device 0x1f090002 has been deconfigured (set to 0xffffffff).


-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Non-lvm root on LVM disk
| |
-----------------------------------------------------


panic: LVM: Configuration failure
Stack Trace:
IP Function Name
0xe00000000107e160 lv_boothalt+0x110
0xe000000001085700 lv_check_boot+0x60
0xe0000000010855f0 lvmconf+0x2f0
0xe00000000108b370 im_lvmconf+0x70
0xe0000000014df130 DoCalllist+0x3a0
End of Stack Trace

Any ideas ?
We know we can bring it down to nPar mode and create the vPar there but we're experimenting right now and want to avoid that.

[Torsten.]

Any idea?

Yes!

Create a golden image of an existing vPar and restore it to the "new" vPar's boot disk, adjust the settings (hostname, IP addr. ...) and you are running.

"dd" is a bad idea in this case, because you did something wrong (no LVM_disk message).

[Tim Nelson]

The best way is as mentioned.

Create ignite image of other vPar.

Boot second vpar using vparboot -s ignite_server ( check man page for syntax ) then choose advanced install.

The issue exists that you cannot access the BCH screen unless you reboot the entire nPar.

Ignite cloning note:
in order to clone a system you will need to do the following:

-create /var/opt/ignite/clients/MAC_ADDRESS of new server and link /var/opt/ignite/new_server to this.
-cd to /var/opt/ignite/clients/CLONE_SOURCE and find ./ INDEX recovery ../new_server
( this all is documented in the clone section of the Ignite admin guide ).
-don't forget to include the new server name or IP in the /etc/exports file so Ignite can NFS mount /var/opt/ignite/... during the recovery.