Troubleshooting
Problem
Rootvg volume group attribute to "no" after upgrading your vios from 2.2.6.x to 3.1.x.x using viosupgrade using alt_disk method
Please find the below example:
On vios 2.2.6.x before viosupgrade :-
On vios 3.1.x.x after viosupgrade :-
Cause
viosupgrade from 2.2.6.x to 3.1.x.x is actually not traditional update like "updateios" but more a migration ,where we are upgrading vios 2.2.6.x(Built on AIX 6.1) to vios 3.1.x.x(Built on AIX 7.2).
So its actually a fresh install of vios 3.1.x.x where "viosupgrade" automates following steps. .
1. VIOS Metadata Backup - viosbr -backup
2. New VIOS Image Installation - Install
3. VIOS Metadata Restore - viosbr -restore
So any other attributes are not automatically carried forward
Resolving The Problem
Purpose of "Auto On" is that "The Volume Group will be automatically varied on during boot .
This attribute plays a key role in a non-rootvg volume group for automatically varying on a Volume group . For rootvg will be varied on regardless of this attribute . So this would not have any impact .
This is set to "No" by "alt_disk_copy -d" used by viosupgrade underneath and purpose is that in case you revert back to 2.2.6.x , the altinst_rootvg should not be varied on automatically .
Now that you are on 3.1.x.x you can use the below command to set it back to "yes"
$ oem_setup_env
# chvg -a y rootvg
# chvg -a y rootvg
This commands will not need a reboot and will change on runtime
Document Location
Worldwide
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"VIOS 2.2 and 3.1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Was this topic helpful?
Document Information
Modified date:
20 October 2021
UID
ibm16253797