1833978 Members
2512 Online
110063 Solutions
New Discussion

VGSCAN errors:

 
Jimmy N
Occasional Contributor

VGSCAN errors:

Hello,

when I try to vgscan, i get the following: How do i fix it?

Physical Volume "/dev/dsk/c2t6d0" contains no LVM information
Couldn't stat physical volume "/dev/dsk/c7t2d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t3d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t4d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t5d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t6d0":
Invalid argument
Physical Volume "/dev/dsk/c7t6d2" is not part of a Volume Group
Physical Volume "/dev/dsk/c7t6d6" is not part of a Volume Group
Couldn't stat physical volume "/dev/dsk/c7t7d0":

5 REPLIES 5
James R. Ferguson
Acclaimed Contributor

Re: VGSCAN errors:

Hi Jimmy:

I'd try this after (re)reading the man pages for 'vgscan':

Make a good backup copy of your current /etc/lvmtab before you start.

# cp /etc/lvmtab /etc/lvmtab.old

Now, remove the file and issue the 'vgscan' to rebuild it. The idea is that if /etc/lvmtab exists, the information contained in it is used to assist in rebuilding the file, and/but the existing file is updated with the new corrected configuration. So:

# rm /etc/lvmtab
# vgscan -a -v > /tmp/vgscan.log 2>&1

Again, pay attention to the guidelines in the man pages for 'vgscan' regarding alternate links and/or boot devices. Also note from the man pages that after 'vgscan' completes successfully, you should run 'vgimport' on each set of unmatched physical volumes.

...JRF...
Vincenzo Restuccia
Honored Contributor

Re: VGSCAN errors:

What have you with vgdisplay -v ?
Bill McNAMARA_1
Honored Contributor

Re: VGSCAN errors:

If you can remember what PVs are in your VG, the best way is to reconfigure your /etc/lvmtab with vgimport.
vgscan is designed to scan all disks in numerical order looking for LVM headers in order to recreate the lvmtab. Unfortunately the command relies on you knowing what you're doing and being able to examine the /etc/lvmtab
in order to correct thing to do bus traffic management better... using vgreduce and vgextend.

a pvdisplay on the device files showld also give some info.. but only use vgscan if something is screwed up with your /etc/lvmtab.

Later,
Bill
It works for me (tm)
Les Schuettpelz
Frequent Advisor

Re: VGSCAN errors:

Dave Fargo using Les's ITRC login...

Now there are 2 related posts with not enough background info to properly advise. What are we trying to accomplish? Has there been a hardware failure? HBA or storage frame? Have devices been reconfigured, changed Target/LUN, or something like that? Disks added, removed or relocated?

There may be old device files out there that no longer are associated with real hardware and need to be cleaned up? Also, the system may need to discover new device addressing if there have been changes? This would require a reboot or a plain ioscan.

More info of this nature would be helpful in deciding whether your situation requires vgscan, vgimport, or possibly vgreduce -f and then vgextend. Bottom line would be is there data on some devices that needs to be recovered, or are you just trying to get some disks into a volume group?
Roberto Arias
Valued Contributor

Re: VGSCAN errors:

Hi Jimmi:

Had you change the disk? if you have done this, you must be restore the LVM configuration whit vgcfgrestore and make the new FS
The man is your friend