vgdisplay produce error

[Ahmad Munawwar]

Hi,

When running vgdisplay -v /dev/vg01, i got erorrs:

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t11d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg01/data2
LV Status available/syncd
LV Size (Mbytes) 1400
Current LE 1400
Allocated PE 2800
Used PV 4

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t11d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg01/fs1
LV Status available/stale
LV Size (Mbytes) 10500
Current LE 10500
Allocated PE 21000
Used PV 13

How should I look this problem in details.

br,
Munawwar

[Steve Steel · Accepted solution]

Hi

Look at

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdf840cb17a32d5118fef0090279cd0f9,00.html

Especially about rebuilding the lvmtab


Steve steel

[Shahul]

Hi

The error clearly says that it could not get information of c0t11d0. Now U will have to checkup whether vgdisplay is saying right or wrong. This can be traced by ioscan, diskinfo like commands.

#ioscan -fnC disk |grep c0t11d0

Is it listing the HDD, then U are almost thru. U are HDD is detected by system. If it is not listing, something is wrong with HDD, U will have to consult H/W vendor. then

#diskinfo /dev/rdsk/c0t11d0

U should get the details about HDD here. Then

check /var/adm/syslog/syslog.log for possible errors. It sounds like something wrong with HDD. Please trace it.

Best of luck
Shahul

[Nick Wickens]

Looks like you have a disk thats gone walkabouts. Try running the following commands -

diskinfo /dev/rdsk/c0t11d0 (note the "rdsk")

&

ioscan -fnCdisk

Scan through the output of the second command for disk c0t11d0 and check its status.

[Robert Sipe]

Your VG lost a PV. Perhaps it was replaced, failed, who knows. Your users will usually be the first to complain due to some strange I/O error when they attempt to access their files. You can usually see what LV was affected when you run an lvdisplay -v and look for stale or ??? on the PEs. If the disk is still available you can vgextend it back into the VG. If not you will need to add in another disk (assuming you are out of room) and restore from tape. I have had this exact same problem and was able to repair the VG and restore the lost files