Operating System - HP-UX
1752565 Members
4996 Online
108788 Solutions
New Discussion юеВ

Re: lvdisplay Could not query physical volume

 
SOLVED
Go to solution
Norville Cole
Advisor

lvdisplay Could not query physical volume

I was able to get my disk to boot up, but now I have another problem while booting up it complain about not being able to see the mirror disk that I had removed /dev/dsk/c0t5d0. I have tried vgreduce and it worked fine but when I went to rebuilt the lvmtab file with vgscan it coredump on me
Memory Fault:coredump
3 REPLIES 3
V. Nyga
Honored Contributor
Solution

Re: lvdisplay Could not query physical volume

Hi,

what does 'vgdisplay -v' says?
Also you should do 'lvreduce -m 0 /dev/vgxx/lvoly' before vgreduce.
'vgxx' is your volume group, 'lvoly' the different logical volumes.

Maybe also some infos/help here:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1193862

HTH
Volkmar
*** Say 'Thanks' with Kudos ***
Torsten.
Acclaimed Contributor

Re: lvdisplay Could not query physical volume

I assume this is related to
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1193807

If you removed the disk in a proper way, all information should be gone.
But likely you did something wrong. What actions you did?

If you still want to mirror the disk, start over.

The right procedure depends on your type of hardware (HP9000 or Integrity).
See the manual for the how-to.

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf

If you have a HP9000 system, see appendix A - How to mirror the root volume (PA-RISC servers).


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Mridul Shrivastava
Honored Contributor

Re: lvdisplay Could not query physical volume

Why do you want to run vgscan if you have properly reduced the disk from the VG. If it is still present in lvmtab that means u have not executed vgreduce command for that disk.

After lvreduce for all LVs vgreduce has to be executed to remove the disk from VG.
Time has a wonderful way of weeding out the trivial