Problem with vgscan

[Ralf Buchhold]

Hello
when I use vgscan, I get this message (with vg01 and vg02)

Any idea ?
Ralf

vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg01".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg02".
vgscan: The physical volume "/dev/dsk/c3t2d0s2" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c4t8d0s2" is already recorded in the "/etc/lvmtab" file.
Couldn't stat physical volume "/dev/dsk/c0t0d0":
Invalid argument

vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg01 failed.

vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg02 failed.

[Peter Godron]

Ralf,
why are you using the vgscan command ?
See thread:
http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1015344

[Ninad_1]

Ralf,

Do all the disks show in
ioscan -fnC disk ?
after ioscan -fnC disk - try
insf -e
for some of the disks try diskinfo /dev/dsk/diskname
Any errors in syslog reported ?

For disks /dev/dsk/c3t2d0s2 and /dev/dsk/c4t8d0s2 , they seem to be there in some other VG - check strings /etc/lvmtab - under which VG they appear.

Regards,
Ninad

[LiPEnS]

Hi
mv /etc/lvmtab /etc/lvmtab.old
and
vgscan -av

Regards LiPEnS

[Chan 007]

Ralf,

I guess, when you exported disk from one system to other you have not done vgexport /dev/vg01 after vgchange -a n /dev/vg01.

All you need to do is just move the /etc/lvmtab and run vgscan.

Once you have done that this will create a new lvmtab. Then you carry on.

Chan

[Mridul Shrivastava]

This kind of errors indicate there is a mismatch b/w ioscan and lvmta device files. either the device path has changed and vg configuration is not updated or someone may have destroyed the LVM header information so if you execute vgdisplay there will be some error messages.
If device path's got changed then I will suggest you to update the vg configuration using the following command:
# vgcfgrestore -n -o

do this for all the disk then u'll not get these error messages. So better to restore the configuration instead of running vscan.
vgscan may cause some issues if u execute on the systems where some storage is connect.