Re: Forgot to put old_rootvg to sleep before reboot - How to Wake

Found the following at http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp

I'm not sure if it directly addresses your problem but it should point
you in the right direction.



Commands Reference, Volume 1, a - c
alt_rootvg_op Command
Purpose

Performs operations on existing alternate rootvg volume groups.
Syntax

To determine Volume Group Boot Disk (-q):

alt_rootvg_op -q -d disk [-D]

To rename Alternate Disk Volume Group (-v):

alt_rootvg_op -v new volume group name -d disk [-D]

To wake up Volume Group (-W):

alt_rootvg_op -W -d disk [-D]

To put to sleep Volume Group (-S):

alt_rootvg_op -S [-tD]

To clean up Alternate Disk Volume Group (-X):

alt_rootvg_op -X [volume group] [-D]

To customize Alternate Disk Volume Group (-C):

alt_rootvg_op -C [-R resolv_conf] [-s script] [-b bundle_name] [-I
installp_flags] [-l images_location] [-f fix_bundle] [-F fixes] [-w
filesets] [-DV]
Description

The alt_rootvg_op command can be used to determine which disk is the
boot disk for a specific volume group. Use the -q flag to determine
the boot disk. This can be useful when a volume group is comprised of
multiple disks and a change in the bootlist is necessary.

This command can also be used to rename the alternate disk volume
groups. This is especially useful when creating multiple alternate
disks, on multiple volume groups, and name identification is
necessary.

If data access is necessary between the current rootvg and an
alternate disk, use the alt_rootvg_op command to perform a volume
group "wake-up" (using the -W flag) on the nonbooted volume group. The
"wake-up" puts the volume group in a post phase 1 state (that is, the /
alt_inst file systems will be mounted). The customize operation (-C
flag) can be executed at this time.

The running system's operating system must be a version greater than
or equal to the operating system version of the volume group that
undergoes the "wake-up." This might mean that it is necessary to boot
from the altinst_rootvg and "wake up" the old_rootvg.

The alt_rootvg_op command does not allow a "wake-up" to occur on a
volume group with a greater operating system version, unless the FORCE
environment variable is set to Yes.
Notes:

1. The volume group that experiences the "wake-up" is renamed
altinst_rootvg.
2. Do not execute phase 3 on the volume group that experiences the
"wake-up."
3. Do not reboot the system if there is a volume group in the
"wake" state. This can cause damage or data loss to the volume group
that is in the "wake" state. Volume groups in the "wake" state can be
put to "sleep" with the -S flag.

When data access is no longer needed, the alt_rootvg_op command can be
used to put to sleep the volume group in the "wake" state, using the -
S flag. The boot image on the target alternate rootvg can be rebuilt
if necessary with the -t flag. The sleep operations revert the
alternate volume group to an inactive state.

When cleaning up the alternate disk volume group, the alt_rootvg_op
command uses the -X flag to remove the altinst_rootvg volume group
definition from the ODM database. If the target volume group is varied
off at the time this operation is executed, only the ODM definitions
associated with the target volume group are removed. The actual volume
group data is not removed. If the volume group is bootable, you can
still reboot from that volume group, by setting the bootlist to a boot
disk in this volume group. The -X flag accepts a volume group name as
an argument and acts on the altinst_rootvg volume group by default.

The customize operation of the alt_rootvg_op command (using the -C
flag) can be used to perform the following functions on an active
alternate root volume group:

* Install software and software updates. Apply this operation only
to alternate volume groups created with the rootvg copy operation.
* Execute customization script.
* Copy resolve.conf files.

Flags
-b bundle_name Path name of optional file with a list of packages or
filesets that will be installed after a rootvg clone. The -l flag must
be used with this option.
-C Performs the customization operation on the active rootvg volume
group.
-d target_disk Specifies a space-delimited list of the name or names
of the target disks that will be targets of the given operation.
-D Turns on debug (sets -x output).
-f fix_bundle Optional file with a list of APARs to install after a
clone of rootvg. The -l flag must be used with this option.
-F fixes Optional list of APARs (for example, IY123456) to install
after a clone of rootvg. The -l flag must be used with this option.
-I installp_flags The flags to use when updating or installing new
filesets into the cloned alt_inst_rootvg. The default flag is -acgX.
The -l flag must be used with this option.
-l images_location Location of installp images or updates to apply
after a clone of rootvg. This can be a directory full path name or
device name (like /dev/rmt0).
-q Determines the volume group boot disk.
-R resolv_conf The resolv.conf file to replace the existing one in
the rootvg. You must specify a full path name.
-s script Optional customization script to be executed during the
customization phase. This file must be executable. This script is
called on the running system before the /alt_inst file systems are
unmounted, so files can be copied from the running system to the /
alt_inst file systems before the reboot.
-S Puts to sleep the alternate root volume group that experienced the
previous "wake" operation.
-t Rebuilds the alternate boot image before putting the volume group
to "sleep." This flag is only valid for alternate root volume groups
created with the clone or copy install operation. The -t flag requires
the -S flag.
-v Name Renames an alternate disk volume group to the name specified
with the Name parameter.
-V Turn on verbose output.
-w filesets List of filesets to install after cloning a rootvg. The -
l flag must be used with this option.
-W Performs a wake-up on the root volume group located on the
target_disk.
-X Removes the altinst_rootvg volume group definition from the ODM
database.
Exit Status
0 All alt_rootvg_op related operations completed successfully.
0 An error occurred.
Examples

1. To remove the original rootvg ODM database entry, after booting
from the new alternate disk:

alt_rootvg_op -X old_rootvg

2. To cleanup the current alternate disk install operation:

alt_rootvg_op -X

3. To determine the boot disk for a volume group with multiple
physical volume:

alt_rootvg_op -q -d hdisk0

Illustrated Example

# lspv

hdisk0 00006091aef8b687 old_rootvg
hdisk1 00076443210a72ea rootvg
hdisk2 0000875f48998649 old_rootvg

# alt_rootvg_op -q -d hdisk0

hdisk2

4. To execute phases 2 and 3 on an existing alternate rootvg and
reboot the system on successful completion:

alt_disk_copy -d hdisk1 -P23 -r

In this case, the boot disk for old_rootvg is actually hdisk2.
Therefore, you could reset your bootlist to hdisk2 and reboot to the
original rootvg volume group.
5. To modify an alt_disk_install volume group name:

alt_rootvg_op -v alt_disk_530 -d hdisk2

Illustrated Example

# lspv

hdisk0 00006091aef8b687 rootvg
hdisk1 00000103000d1a78 rootvg
hdisk2 000040445043d9f3 altinst_rootvg
hdisk3 00076443210a72ea altinst_rootvg
hdisk4 0000875f48998649 None
hdisk5 000005317c58000e None

# alt_rootvg_op -v alt_disk_432 -d hdisk2

#lspv

hdisk0 00006091aef8b687 rootvg
hdisk1 00000103000d1a78 rootvg
hdisk2 000040445043d9f3 alt_disk_432
hdisk3 00076443210a72ea alt_disk_432
hdisk4 0000875f48998649 None
hdisk5 000005317c58000e None

6. To "wake up" an original rootvg after booting from the new
alternate disk:

alt_rootvg_op -W -d hdisk0

7. To "put to sleep" a volume group that had experienced a "wake-
up" and rebuild the boot image:

alt_rootvg_op -S -t

8. To update the alternate rootvg to the latest fileset levels
available in /updates and install them into the alternate root volume
group.

alt_rootvg_op -d "hdisk3 hdisk4" -b update_all -l /updates

Location

/usr/sbin/alt_rootvg_op
Files
/usr/sbin/alt_rootvg_op Contains the alt_rootvg_op command.
Related Information

alt_disk_copy Command, alt_disk_mksysb Command, bootlist Command,
bosboot Command.

The lspv in AIX 5L Version 5.3 Commands Reference, Volume 3.

The nim, nimadm command in AIX 5L Version 5.3 Commands Reference,
Volume 4.

.

Relevant Pages

  • Re: Cant remove hdisk from rootvg
    ... Run the following command to see what the disk actually knows about the ... This will read the vgda on the disk .. ... Disk VGDA says hdisk1 is IN the volume group and ODM says the disk is ... Can't remove hdisk from rootvg ...
    (AIX-L)
  • Re: Replace a rootvg hard disk with different capacity
    ... Easiest way to do this would be to clone the rootvg to the new disk and then ... just reboot from there and remove the old one. ... new disk and a "lsvg" command will show you 2 vg's and it will be very ...
    (comp.unix.aix)
  • Re: disk cant be used for vg (forgot to exportvg)
    ... When using mkvg you will receive an error when a disk has been ... You can add the command line flag of "-f" to force the creation of the ...
    (comp.unix.aix)
  • Re: New HDD Installation
    ... "John John" wrote: ... a single partition disk. ... confirm or change the active flag of the partition using the FDISK command. ... There are other ways to mark the partition active, either with a Windows ...
    (microsoft.public.windowsxp.general)
  • PC8477 Demo Program
    ... The PC8477 Demo Program is designed to allow access to all software commands and registers of National Semiconductor's PC8477 Advanced Floppy Disk Controller. ... The left center indicates the number of bytes transferred during the last command issued. ...
    (comp.sys.ibm.ps2.hardware)