Error Messages for Component ID 0516

AIX Version 4.3 Messages Guide and Reference

Error Messages for Component ID 0516

0516-005 String: The physical volume is already a member of the requested volume group

Possible Causes

You attempted to add a physical volume to a volume group, but you specified a physical volume that is already a member of the volume group.
You attempted to add a physical volume to a volume group, and a discrepancy exists between the volume group descriptor area (VGDA) and the Object Data Manager (ODM).
If the VGDA does not match the ODM, the following error message may display even though the physical volume is actually a member of a volume group:
```
0516-320 String:Physical volume String is not assigned to a 
volume group
```
If you attempt to assign the physical volume to the volume group, error message 0516-005 is displayed.

Procedures for Recovery

Ensure that the physical volume you specified is not already a member of the volume group.
Enter the lsvg -p VolumeGroupName command to list the members of the volume group.

Reenter the extendvg command to add a physical volume to a volume group, and specify a valid physical volume that is not a member of the volume group.
Update the ODM database with information from the VGDA.
If the physical volume is a member of the volume group but error message 0516-320 is displayed anyway, enter the redefinevg -d PhysicalVolumeName VolumeGroupName command to update the ODM database with information from the VGDA. The VGDA contains current information.

0516-010 Volume group must be varied on: use varyonvg command

Possible Causes

You specified a volume group that is currently unavailable on your system.

Procedures for Recovery

Check for misspelling in the volume group name.
Make your volume group available.
1. Use the lsvg command to verify whether your volume group is available.
2. If the volume group is not available, use the varyonvg command to make it available.
See if one of the disks in the volume group is available.
1. You can check to see if the disk is available by using the lspv command.
2. If the disk is not available, issue the mkdev command to make it available and run the varyonvg command to make the volume group available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command. It may be necessary to use the Object Data Manager (ODM).

0516-013 The volume group cannot be varied on because there are no good copies of the descriptor area

Possible Causes

Most of the volume group descriptor area (VGDA) cannot be accessed or is damaged.

Procedures for Recovery

See if one of the disks where the volume group is located is available.
1. Issue the lspv command to see if the disk is available.
2. If the disk is not available, issue the mkdev command to make it available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.
4. If the disk is available, run the odmdelete command to delete the damaged VolumeGroup from the configuration database:
```
odmdelete -q name=VolumeGroupName -o CuAt
```
5. Use the System Management Interface Tool (SMIT) to add a new volume group.
Shut down your system and check for any loose or faulty cables around the fixed- disk area.
1. Check adapters and power sources.
2. Reboot your system and enter your command again.
For volume groups with multiple physical volumes:
1. If the varyon operation reports a missing physical volume, use the chpv -vr command to temporarily remove the volume from the volume group.
2. Reissue your command to make the volume group partially available.
3. Once the problem is corrected and the physical volume is brought back online, issue the chpv -va command to return the physical volume and make it available again to the volume group.
  Note: This procedure should be used as a last resort because data integrity cannot be guaranteed.

0516-022 Illegal parameter or structure value

Possible Causes

The Object Data Management (ODM) database was damaged, and the physical volume ID (pvid) of a disk was listed as None.
One of your Customize Device Configuration database files was damaged, and while you ran your command, the file collected some illegal parameters or structure values.
You attempted to create a logical volume with the System Management Interface Tool (SMIT), or from the command line with the mklv command. The physical volume name specified was not configured.

Procedures for Recovery

Verify that the disk is recognized by the system. From the command line, run:
```
lqueryvg -p hdisk# -At
```

Deactivate the volume group.
1. Use the lsvg -o command to determine if your volume group is active.
2. If it is active, run the varyoffvg command.
3. Remove the definition of the volume group from the system by using the exportvg command.
4. Add the definition of the volume group to the system by using the importvg command.

0516-304 Unable to find device ID in the Device Configuration Database

Possible Causes

One of your Customize Device Configuration database files was damaged, and while you ran your command, this file collected some illegal parameters for the device ID.

Procedures for Recovery

Deactivate the volume group.
Use the lsvg -o command to find out if your volume group is active. If it is active, run the varyoffvg command.
Remove the definition of the volume group from the system by using the exportvg command.
Add the definition of the volume group to the system by using the importvg command.
Activate the volume group by using the varyonvg command.

0516-306 Unable to find VolumeGroupName VolumeGroupDescription in the Device Configuration Database

Possible Causes

You issued one of the following commands:
- extendvg
- getlvodm
- lsvg
and the specified device does not exist in the Object Data Manager (ODM) database.

Note: The getlvodm command is an internal command. InfoExplorer currently contains no information about this command.

Procedures for Recovery

Ensure that the device is defined in the database.
1. Enter the lsdev -C command to display a list of devices defined in the database.
2. If the device is not listed, use one the following methods to define it, depending on the type of device:
  - Define a physical volume using the mkdev command or the SMIT menu option Devices--> Fixed Disk--> Add a Disk.
  - Define a logical volume using the mklv command or the SMIT menu option Physical and Logical Storage--> Logical Volume Manager--> Volume Groups--> Add a Volume Group.

0516-320 ProgramName: Physical volume String is not assigned to a volume group

Possible Causes

You issued one of the following commands:
- getlvodm
- lspv
- lsvg
and the specified physical volume is not assigned to a volume group in the Object Data Manager (ODM) database.

Note: The getlvodm command is an internal command. There is no information available in InfoExplorer about this command.

Procedures for Recovery

Ensure that the physical volume is defined in your system and its name is spelled correctly in the ODM database.
1. Enter the lsvg command to list all the volume groups defined in your system.
2. Enter the lsvg -p VolumeGroupName command to list all the physical volumes in the specified volume group.
3. Ensure that the physical volume name is spelled correctly. For information on editing the ODM database, see "Object Data Manager (ODM) Overview" in in AIX General Programming Concepts: Writing and Debugging Programs.
4. If the physical volume is undefined or its name misspelled, add the correct physical volume in one of the following ways:
With the System Management Interface Tool (SMIT), use the Physical and Logical Storage--> Define a Fixed Disk to the Operating System menu option to add the physical volume to the volume group. Then select one of the following three menu options to add the definition of the physical volume to a volume group:
- Add a Fixed Disk to an Existing Group
- Add a Fixed Disk without Data to a New Group
- Add a Fixed Disk with Data

From the command line, use one of the following commands:

mkvg
	Creates a new volume group containing the physical volume.
extendvg
	Defines a physical volume to an existing volume group.
importvg
	Imports a new volume group definition from a set of physical volumes. Note: Use the importvg command only if the volume group definition was previously exported using the exportvg command.

0516-366 Volume group VolumeGroupName is locked. Try again

Possible Causes

You ran a command that tried to access a Configuration Object Data Management file that was in use or was closed incorrectly.
The installation of a software product was interrupted, causing the system to lock the root volume group.

Procedures for Recovery

Log in as the root user and run the odmdelete command to remove the lock from the configuration database:
```
odmdelete -q "name=VGname and attribute=lock" -o CuAt
```
Issue your command again.

0516-404 Not enough resources available to fulfill allocation

Possible Causes

You used the mklv or extendlv command, specifying a physical volume without enough partitions (free space) to fulfill the requested logical volume size.
You used the mklv or extendlv command without specifying a physical volume, and the volume group specified does not have enough free partitions (free space) to fulfill the requested logical volume size.

Procedures for Recovery

Allocate enough disk space by specifying different characteristics. Do one of the following:
- Enter the mklv or extendlv command and specify a different physical volume, ensuring that the physical volume specified includes enough free partitions to fulfill the requested logical volume size.
- Enter the mklv or extendlv command specifying fewer partitions to be allocated for the logical volume.
- Do not specify a physical volume. If you do not specify a physical volume, the command uses all the physical volumes available in the volume group.
Add or create more disk space. Do one of the following:
- Add another physical volume (fixed disk) to the volume group.
- Delete an unused logical volume.

0516-787 extendlv: Maximum allocation for logical volume Name is Value

Possible Causes

Using the System Management Interface Tool (SMIT), you specified a value in the Number of ADDITIONAL logical partitions field to try to increase the logical volume size beyond the maximum number of logical partitions.
From the command line, you used the extendlv command (or the chfs command, which calls the extendlv command) to try to increase the logical volume size beyond the maximum number of logical partitions.

Procedures for Recovery

Use SMIT to change the logical volume.
Use the SMIT Physical and Logical Storage--> Logical Volume Manager--> Logical Volumes--> Set Characteristic of a Logical Volume--> Change a Logical Volume menu option to specify a new number of logical partitions in the MAXIMUM NUMBER of LOGICAL PARTITIONS field.
Use the chlv command to change the logical volume.
1. Increase the maximum number of logical volume partitions for the named logical volume with the chlv command, as follows:
```
chlv -x MaximumLogicalPartitions LogicalVolumeName
```
2. Rerun the chfs command or the extendlv command.
  Note: In both cases, you must change the logical volume before you can extend or increase it.

0516-794 String not configured. Please configure the disk before trying this command again

Possible Causes

You used the System Management Interface Tool (SMIT) to add an undefined physical volume to the volume group, but the physical volume specified is not defined or installed on the system, or does not exist.
From the command line, you used the mkvg or the extendvg command to add an undefined physical volume to the volume group.

Procedures for Recovery

Use SMIT to add a disk.
Use the Devices--> Fixed Disk--> Add a Disk menu option to define the disk.
Use the mkdev command to define a disk.
Once the disk is defined, you can add it to an existing volume group or use it to create a new volume group.

Note: These commands are for disks without data. If the disk contains data, use the importvg command rather than the mkvg command or the extendvg command.

0516-822 Unable to create logical volume

Possible Causes

You specified a logical volume name that already exists.
You specified a volume group that currently does not have enough disk space for your logical volume.
You specified a volume group that is currently unavailable on your system.

Procedures for Recovery

Name your logical volume to a name not already in use.
1. List all of the current logical volumes by issuing the following command:
```
lsvg -o| lsvg -i -1
```
2. Rerun your command with the correct logical volume name.
Check the disk space in your volume group.
1. Run the lsvg command to check how many free partitions you have available in your volume group.
2. Repeat your command with the correct number of partitions or correct volume name.
Verify that your volume group is available.
See if one of the disks in the volume group is available.
1. Check to see if the disk is available by using the lspv command.
2. If the disk is not available, issue the mkdev command to make it available and run the varyonvq command to make the volume group available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.

0516-952 Unable to vary on volume group uvgl

Possible Causes

You specified a volume group that is currently unavailable on your system.

Procedures for Recovery

Check for misspelling in the volume group name you specified.
See if one of the disks in the volume group is available.
1. Check to see if the disk is available by using the lspv command.
2. If the disk is not available, issue the mkdev command to make it available and run the varyonvq command to make the volume group available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.