Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New RAID5 Array - making vg

Status
Not open for further replies.

hellsbells

Technical User
Jan 9, 2003
32
GB
Help! I have managed to install new disks into a ssa disk enclosure and created a RAID5 array with a hot spare. However when I have come to create a new volume group I get an error message saying the disk (hdisk2) is already part of a volume group. I have created the volume group with the force option set to yes and this seems to have worked but I am now a little worried that I have done this incorrectly. I now need to create new filesystems for an oracle installation and am not sure what to do next.

Could anyone help a complete novice?

Thanks in advance.
 
Hi!

I have never met it with RAID configuration (maybe because I was using new disks). I met it only on non-raid configuration. When I exported VG (instead of removing it) and wanted add them to different VG (or create new VG) then I got the same error you mentioned. The error description is below:

"0516–005 String: The physical volume is already a member of the requested volume group Problem Determination: 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. User Response: Ensure that the physical volume you specified is not already a member of the volume group by doing the following: 1. Enter the lsvg -p VolumeGroupName command to list the members of the volume group. 2. 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. 3. Update the ODM database with information from the VGDA.Problem Determination: 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 0516-320 error message displays, even though the physical volume is actually a member of a volume group. User Response: If the physical volume is a member of the volume group but error message 0516-320 is displayed anyway, enter the following command to update the ODM database with information from the VGDA. The VGDA contains current information. redefinevg -d PhysicalVolumeName VolumeGroupName"



regards, m.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top