Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy.
Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Operating Systems. Any redpapers for this procedure?
After that you can remirror to the disks that had the old rootvg if you like. John Yard Posted December 13, 0 Comments. Donn Wolf Posted December 13, 0 Comments. Lamar Saxon Posted December 14, 0 Comments. Anonymous Posted December 14, 0 Comments. Thanks for all replies. Donn Wolf Posted December 14, 0 Comments. Prasanna01 Posted December 21, 0 Comments. Has anyone faced this problem before? Regards Prasanna. Robert Weinmann Posted December 21, 0 Comments.
Register or Login. Welcome back! Sign in with Email. Reset Your Password We'll send an email with a link to reset your password. Stay ahead! Note: The level of mksysb that you are installing must match the level of the bos. At this time, only 4. When cloning the rootvg volume group, a new boot image is created with the bosboot command. When installing a mksysb image, a boot image for the level of mksysb and platform type is copied to the boot logical volume for the new alternate rootvg.
When the system is rebooted, the bosboot command is run in the early stage of boot, and the system is rebooted once again. This is to synchronize the boot image with the mksysb that was just restored. The system then boots in normal mode. If varied on, it shows as owning no logical volumes, but it does indeed contain logical volumes, but they have been removed from the ODM because their names now conflict with the names of the logical volumes on the running system.
When the system reboots from the new disk, the former rootvg does not show up in a lspv listing. The disks that were occupied by the rootvg show up as not having a volume group. But, you can still use the bootlist command to change the bootlist to reboot from the old rootvg if necessary.
This is how they should be accessed if using a customization script. See the NIM Guide for more information. The AIX 4. The install is broken into three phases, the default being to do all three phases. You can run each phase separately, run Phases 1 and 2 together, or run Phases 2 and 3 together.
Phase 2 can be run multiple times before Phase 3 is run. You must run Phase 3 to get a volume group that is a usable rootvg. The bootlist , nim , lspv , and bosboot commands. Runs any specified customization script, installs updates, new filesets, fixes or bundles cloning only , copies a resolv.
It sets the bootlist and reboots if specified. If set, then -r flag cannot be used. Note: -d and -C are mutually exclusive. Optional image. The image. The default value would be the platform of the running system obtained with the bootinfo -T command on AIX version 4. This flag is only valid for mksysb installs -d flag.
Valid values are: 1, 2, 3, 12, 23, or all. This file must be executable.
0コメント