vgchange: Warning: couldn't query physical volume "/dev/dsk/c10t1d7":

[Les Harrison]

Hello

We had to boot our HP-UX server because it hung (performed TOC from iLO to boot). When the server has come back up I tried to restart a service guard package and it failed because it could activate the volume group:

vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c10t1d7":
I/O error
vgchange: I/O error
vgchange: Activation mode requested for the volume group "/dev/vgcl" conflicts with configured mode
vgchange: Warning: couldn't query physical volume "/dev/dsk/c10t1d7":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c12t1d7":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
root@udox305# vgextend /dev/vgcl /dev/dsk/c10t1d7
vgextend: The volume group "/dev/vgcl" is not active. Only an active
volume group can be extended.

ioscan -funC disk shows the disks are not there. They appear in /etc/lvmtab.

Any ideas?

Thanks

Les

[Rasheed Tamton]

Hi,

Is this disk on SAN.

Can you do

ioscan -fCdisk
insf -e

Rgds.

[Les Harrison]

Yes it's on an EMC SAN:

root@udox305# ioscan -fC disk
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
disk 1 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
disk 2 0/1/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
disk 31 0/3/2/0.101.31.19.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 32 0/3/2/0.101.31.19.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 33 0/3/2/0.101.31.19.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 37 0/3/2/0.101.31.19.0.0.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 38 0/3/2/0.101.31.19.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 39 0/3/2/0.101.31.19.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 40 0/3/2/0.101.31.19.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 59 0/3/2/0.101.31.19.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 61 0/3/2/0.101.31.19.0.1.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 65 0/3/2/0.101.31.19.0.2.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 66 0/3/2/0.101.31.19.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 41 0/3/2/0.101.31.19.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 42 0/3/2/0.101.31.19.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 43 0/3/2/0.101.31.19.0.3.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 44 0/3/2/0.101.31.19.0.3.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 45 0/3/2/0.101.31.19.0.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 46 0/3/2/0.101.31.19.0.10.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 47 0/3/2/0.101.31.19.0.11.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 34 0/4/2/0.98.15.19.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 35 0/4/2/0.98.15.19.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 36 0/4/2/0.98.15.19.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 48 0/4/2/0.98.15.19.0.0.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 49 0/4/2/0.98.15.19.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 50 0/4/2/0.98.15.19.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 51 0/4/2/0.98.15.19.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 60 0/4/2/0.98.15.19.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 62 0/4/2/0.98.15.19.0.1.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 67 0/4/2/0.98.15.19.0.2.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 68 0/4/2/0.98.15.19.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 52 0/4/2/0.98.15.19.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 53 0/4/2/0.98.15.19.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 54 0/4/2/0.98.15.19.0.3.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 55 0/4/2/0.98.15.19.0.3.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 56 0/4/2/0.98.15.19.0.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 57 0/4/2/0.98.15.19.0.10.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 58 0/4/2/0.98.15.19.0.11.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
root@udox305# insf -e
insf: Installing special files for asio0 instance 0 address 0/0/1/0
insf: Installing special files for asio0 instance 1 address 0/0/1/1
insf: Installing special files for hub instance 0 address 0/0/2/0.1
insf: Installing special files for hub instance 1 address 0/0/2/1.1
insf: Installing special files for sdisk instance 0 address 0/0/3/0.0.0.0
insf: Installing special files for sctl instance 0 address 0/0/3/0.0.7.0
insf: Installing special files for sctl instance 1 address 0/0/3/0.1.7.0
insf: Installing special files for sdisk instance 1 address 0/1/1/0.1.0
insf: Installing special files for sctl instance 2 address 0/1/1/0.7.0
insf: Installing special files for sdisk instance 2 address 0/1/1/1.0.0
insf: Installing special files for sctl instance 5 address 0/1/1/1.7.0
insf: Installing special files for sctl instance 6 address 0/3/1/0.7.0
insf: Installing special files for stape instance 1 address 0/3/1/1.6.0
insf: Installing special files for sctl instance 7 address 0/3/1/1.7.0
insf: Installing special files for sdisk instance 31 address 0/3/2/0.101.31.19.0.0.0
insf: Installing special files for sdisk instance 32 address 0/3/2/0.101.31.19.0.0.1
insf: Installing special files for sdisk instance 33 address 0/3/2/0.101.31.19.0.0.4
insf: Installing special files for sdisk instance 37 address 0/3/2/0.101.31.19.0.0.7
insf: Installing special files for sdisk instance 38 address 0/3/2/0.101.31.19.0.1.0
insf: Installing special files for sdisk instance 39 address 0/3/2/0.101.31.19.0.1.1
insf: Installing special files for sdisk instance 40 address 0/3/2/0.101.31.19.0.1.2
insf: Installing special files for sdisk instance 59 address 0/3/2/0.101.31.19.0.1.3
insf: Installing special files for sdisk instance 61 address 0/3/2/0.101.31.19.0.1.6
insf: Installing special files for sdisk instance 65 address 0/3/2/0.101.31.19.0.2.0
insf: Installing special files for sdisk instance 66 address 0/3/2/0.101.31.19.0.2.2
insf: Installing special files for sdisk instance 41 address 0/3/2/0.101.31.19.0.2.7
insf: Installing special files for sdisk instance 42 address 0/3/2/0.101.31.19.0.3.0
insf: Installing special files for sdisk instance 43 address 0/3/2/0.101.31.19.0.3.1
insf: Installing special files for sdisk instance 44 address 0/3/2/0.101.31.19.0.3.2
insf: Installing special files for sdisk instance 45 address 0/3/2/0.101.31.19.0.3.3
insf: Installing special files for sdisk instance 46 address 0/3/2/0.101.31.19.0.10.7
insf: Installing special files for sdisk instance 47 address 0/3/2/0.101.31.19.0.11.3
insf: Installing special files for sctl instance 8 address 0/3/2/0.101.31.255.1.3.0
insf: Installing special files for sdisk instance 34 address 0/4/2/0.98.15.19.0.0.0
insf: Installing special files for sdisk instance 35 address 0/4/2/0.98.15.19.0.0.1
insf: Installing special files for sdisk instance 36 address 0/4/2/0.98.15.19.0.0.4
insf: Installing special files for sdisk instance 48 address 0/4/2/0.98.15.19.0.0.7
insf: Installing special files for sdisk instance 49 address 0/4/2/0.98.15.19.0.1.0
insf: Installing special files for sdisk instance 50 address 0/4/2/0.98.15.19.0.1.1
insf: Installing special files for sdisk instance 51 address 0/4/2/0.98.15.19.0.1.2
insf: Installing special files for sdisk instance 60 address 0/4/2/0.98.15.19.0.1.3
insf: Installing special files for sdisk instance 62 address 0/4/2/0.98.15.19.0.1.6
insf: Installing special files for sdisk instance 67 address 0/4/2/0.98.15.19.0.2.0
insf: Installing special files for sdisk instance 68 address 0/4/2/0.98.15.19.0.2.2
insf: Installing special files for sdisk instance 52 address 0/4/2/0.98.15.19.0.2.7
insf: Installing special files for sdisk instance 53 address 0/4/2/0.98.15.19.0.3.0
insf: Installing special files for sdisk instance 54 address 0/4/2/0.98.15.19.0.3.1
insf: Installing special files for sdisk instance 55 address 0/4/2/0.98.15.19.0.3.2
insf: Installing special files for sdisk instance 56 address 0/4/2/0.98.15.19.0.3.3
insf: Installing special files for sdisk instance 57 address 0/4/2/0.98.15.19.0.10.7
insf: Installing special files for sdisk instance 58 address 0/4/2/0.98.15.19.0.11.3
insf: Installing special files for sctl instance 9 address 0/4/2/0.98.15.255.1.3.0
insf: Installing special files for ipmi instance 0 address 250/0
insf: Installing special files for pseudo driver cn
insf: Installing special files for pseudo driver mm
insf: Installing special files for pseudo driver arp
insf: Installing special files for pseudo driver devkrs
insf: Installing special files for pseudo driver dmp
insf: Installing special files for pseudo driver ptym
insf: Installing special files for pseudo driver ptys
insf: Installing special files for pseudo driver ip
insf: Installing special files for pseudo driver dmem
insf: Installing special files for pseudo driver nuls
insf: Installing special files for pseudo driver rawip
insf: Installing special files for pseudo driver stcpmap
insf: Installing special files for pseudo driver tcp
insf: Installing special files for pseudo driver telm
insf: Installing special files for pseudo driver tels
insf: Installing special files for pseudo driver tlclts
insf: Installing special files for pseudo driver tlcots
insf: Installing special files for pseudo driver tlcotsod
insf: Installing special files for pseudo driver udp
insf: Installing special files for pseudo driver dev_config
insf: Installing special files for pseudo driver strlog
insf: Installing special files for pseudo driver sad
insf: Installing special files for pseudo driver vols
insf: Installing special files for pseudo driver asyncdsk
insf: Installing special files for pseudo driver echo
insf: Installing special files for pseudo driver dlpi
insf: Installing special files for pseudo driver ptm
insf: Installing special files for pseudo driver pts
insf: Installing special files for pseudo driver klog
insf: Installing special files for pseudo driver sy
insf: Installing special files for pseudo driver kepd
insf: Installing special files for pseudo driver diag2
insf: Installing special files for pseudo driver root

[Rasheed Tamton]

ioscan -fnC|grep t1d7

Does it show now the c10t1d7 or any disks with t1d7

Did you check with the SAN guys whether any changes done from their side or not.

If you have an old inq (syminq) output can you do it again and compare the old ser no with the disk device name.

Rgds.

[Les Harrison]

Hello Rasheed

I can't see the disk using ioscan. Our SAN guys are looking.

In the last few weeks we ran powermt check to clear up redundant paths but these disks were not included. I initially thought that might be the case but apparently not.

Thanks

Les

[Rasheed Tamton]

Hello Les,

powermt display dev=all|grep t1d7

If the physical connection (cable/switch, etc) to EMC is ok and if there are changes at their end, may be, you have to run

powermt check

But consult with your EMC folks.
ioscan might report any hardware connected to the system and in your case you cannot see the disk.

Regards.

[Les Harrison]

Hi Rasheed

Looks like the paths are dead:

root@udox305# powermt display dev=all|grep t1d7
10 0/3/2/0.101.31.19.0.1.7 c10t1d7 FA 10cB active dead 0 0
12 0/4/2/0.98.15.19.0.1.7 c12t1d7 FA 7bA active dead 0 0

[Les Harrison]

Just realized. These disks were removed recently. They were part of a logical volume that we trashed. I can't get rid of them from lvmtab. I tried vgreduce but I still get the same error. Any ideas?

Thanks

Les

[Jeeshan]

then check in your SAN box, may be "powermt restore" can solve your problem.

[Les Harrison]

no joy. The disk is gone. Do I need to restore it to remove it?

[Mridul Shrivastava]

Nothing to worry, execute the vgexport /dev/ command and those entries will be removed from /etc/lvmtab.

I looks like that you are new to forums since you haven't assigned points to anyone so far.

Take some time to assign points for the guys so they gets the credit for the time spent ;)