storage question

[Ali Imran Abbas]

I am adding SAN storage space to hp ux server by making physical volumes, volume groups and logical volumes. But the physical volume status comes out to be unavailable.
pvdisplay /dev/dsk/c34t3d2
--- Physical volumes ---
PV Name /dev/dsk/c34t3d2
VG Name /dev/vgr025
PV Status unavailable
Allocatable yes
VGDA 2
Cur LV 17
PE Size (Mbytes) 32
Total PE 1078
Free PE 0
Allocated PE 1078
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On
Although I have created LV's in it but its status is still unavailable, Can some one help me in this regard?

[Torsten.]

If it worked before, question is "what is changed"?

Did you already run "ioscan -fn" - can you see any NO_HW status? What type of storage do you use?

[Ali Imran Abbas]

I can see the output using ioscan -fnC disk command. here is a piece of output from the list:

isk 693 2/0/12/1/0/4/0.98.111.19.2.3.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c39t3d2 /dev/rdsk/c39t3d2
disk 695 2/0/12/1/0/4/0.98.111.19.2.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c39t3d3 /dev/rdsk/c39t3d3
disk 698 2/0/12/1/0/4/0.98.111.19.2.3.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c39t3d4 /dev/rdsk/c39t3d4

We are using Symmetrix.
We already have around 24 vgs configured. Here is the output from vgdisplay for the PVS of theexisiting volume group:
PV Name /dev/dsk/c36t2d5
PV Name /dev/dsk/c35t2d5 Alternate Link
PV Name /dev/dsk/c38t2d5 Alternate Link
PV Name /dev/dsk/c34t2d5 Alternate Link
PV Name /dev/dsk/c37t2d5 Alternate Link
PV Name /dev/dsk/c39t2d5 Alternate Link
PV Status available
Total PE 1078
Free PE 0
Autoswitch On

PV Name /dev/dsk/c36t2d6
PV Name /dev/dsk/c35t2d6 Alternate Link
PV Name /dev/dsk/c38t2d6 Alternate Link
PV Name /dev/dsk/c34t2d6 Alternate Link
PV Name /dev/dsk/c37t2d6 Alternate Link
PV Name /dev/dsk/c39t2d6 Alternate Link
PV Status available
Total PE 1078
Free PE 0
Autoswitch On

And here is output for the PVS of the newly created VGS:

PV Name /dev/dsk/c34t3d2
PV Status unavailable
Total PE 1078
Free PE 0
Autoswitch On

PV Name /dev/dsk/c34t3d3
PV Status unavailable
Total PE 1078
Free PE 22
Autoswitch On

Any idea from it?

[Sandman!]

The portion of ioscan output that you have attached is irrelevant. Better if you posted ioscan output of only the relevant PVs.

# ioscan -f /dev/dsk/c34t3d2
# ioscan -f /dev/dsk/c34t3d3

[Francis Noël]

Sandman is right in pointing out that we need to see the ioscan output for the problematic nodes.

If someone played with the zoning in a brutal manner your LUNs might have fallen into a sort of "safe mode" where they are in a read-only state. If this is the case they will be CLAIMED but might be reporting as Unavailable.
See the state of your LUNs in the Symmetrix and set them back to write-enabled if need be. Can be done from the EMC Control Center or through Solutions Enabler on the host.

I would also suggest you get a hold of the Inquiry Tool from the EMC support web site. This little utility maps devices to special files and shows you the LUN serial numbers.

Do you have PowerPath installed on the server ?

[Ali Imran Abbas]

Here is the output:

ioscan -f /dev/dsk/c34t3d2
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 683 2/0/2/1/0.97.118.19.2.3.2 sdisk CLAIMED DEVICE EMC SYMMETRIX

ioscan -f /dev/dsk/c34t3d3
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 685 2/0/2/1/0.97.118.19.2.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX

We have a different SAN engineer here who makes this storage space available for use. He told me that he made these disks available to USUNX and I have to create them volume groups on them.

[Francis Noël]

Thank you for posting the requested information.

Can you do a "diskinfo /dev/rdsk/c34t3d3" please ?

[Michael Steele_2]

If you have solutions enabler please attached:

sympd list
syminq

[Michael Steele_2]

Additionally, this might be a failing disk.

ioscan -fnk (* reread into kernel, check for NO_HW again *)

dd if=/dev/dsk/c34t3d2 of=/dev/null count=1000

If this fails then consider increasing the extent size. The default extent size is 4 mb but can be increased to 8, 16, etc. It may be that the VGDA is too small.

So, this comes down to blowing away your lv's and vgreducing the disk out of your vg and then starting over. When you do this hold off on creating lv's until you're sure the pv is Ok in the vg.