Regarding VG Error

[Kavita Poonia]

Hello Techies,

I am getting below mentioned error on one of my HP-UX server. The VG /dev/vg12 is not existing now on this server but its group file is still there. Please let me know how to resolve this error.

vgdisplay: Volume group "/dev/vg12" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "vg12".
expr: Syntax error

/usr/local/bin/Disk-stat.sh.ctms[254]: ( ( 0 * 1000 ) / 0 + 5 ) / 10 : Cannot divide by zero.


Thanks & regards,
Kavita

[Pete Randall]

Try vgexport.


Pete

[Michal Kapalka (mikap)]

hi,

use a advice from Pete,

vgexport.

mikap

[Steven E. Protter]

Shalom,

strings /etc/lvmtab

ioscan -fnC disk

Look for any matches.

I think you will have to vgexport and recreate the volume group, but it would be nice to know what the system expects.

SEP

[James R. Ferguson]

Hi Kavita:

So what are you trying to do? Do you _want_ to regain vg12? Did you want to remove vg12?

If you want'ed only to rid yourself of vg12 at this point you can simply 'rm' the '/dev/vg12/group' file and '/dev/vg12' directory.

Regards!

...JRF...

[Sharma Sanjeev]

Hi kavita

You can remove group file for vg12 /dev/vg12/group or use vgexport

Regards
Sanjeev

[Vishu]

Hi Kavita,

what you trying to do from here now. Like, if you have that VG and it is not listed in lvmtab, then do

# vgscan -av

if you want to get rid of that VG, you can simply remove the group file and its directory.

if you want to regain that VG and having its map file, you can do vgimport then

# vgimport -m /dev/vg12

[Sharma Sanjeev]

Vishu,

I would never suggest vgscan, if there are hundreds of disks and if any one faulty than .......

Regards
Sanjeev

[Kavita Poonia]

Hello All,

We have removed that VG sometime back but now we are getting this error. So, I think to remove this error, I need to remove the group file and directory existing for this VG, right?

Thanks & regards,
Kavita

[Torsten. · Accepted solution]

Yes, remove the group file.



I'm sure you did the VG removal wrong, not by vgremove but by a "rm" only. This is always a reason for trouble.