Question about boot order after changing root disk with vgreduce in vpar enviroment(11.31)??

[Sumin_1]

Hi,

I'm using vpar(A.05.02) which is running on 11.31 in HP Superdome(sx2000). As fas as i know, vpar can't support online i/o change without shuting down the o/s until now.
My question is that when i repalce the primary root disk with vgreduce unfornately, and after replacement, I do mirror it as a alternative root disk so that result in a mismatch with the vpar setting like below

## this is a hypothesis

1. current vpar configuration
# vparstatus -p test02 -v|more
[IO Details]
1.0.1.1.0.0.0.0.0.0.0 BOOT <== faulty disk that should be replaced
1.0.8.1.0.0.0.0.0.0.0,ALTBOOT

2. After replacing primary root disk, I mirrored it as a alternative root disk like disk20_p2

#lvdisplay -v /dev/vg00/lvol1 |more

--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 /dev/disk/disk5_p2 00000 current /dev/disk/disk20_p2 00000 current


3. After completing mirror process, let's compare with vpar config and mirrored config.
under this situation, whenever i reboot the vpar, it will be brought up with using alternative root disk(disk20_p2) because the setting in vpar. So i wonder if i could change the boot setting in vpar while online
I tried to change it using vparmodify however, it failed.


Should i shutdown the o/s and modify the vpar boot setting in another vpar?

This might be the enhancement of vpar in the future release. But i would like to know about it.

Thank you for reading my long story

[SoorajCleris]

Hi Sumin,

I feel like you are facing some other issue becasue if you want to modify boot path it is not a big deal. Operations where the source and target virtual partition are the same are always supported. No need to shutdown the OS.

What is the current output of vparstatus?
How did you try to change the boot path , what is the syntax you used?

Regards,
Sooraj