physical volume --PV status -unavailable

[Bunty....]

#vgdisplay -v /dev/vg03
::
::
::
--- Physical volumes ---
PV Name /dev/dsk/c19t7d6
PV Name /dev/dsk/c18t7d6 Alternate Link
PV Status unavailable
Total PE 1151
Free PE 265
Autoswitch On

PV Name /dev/dsk/c19t7d7
PV Name /dev/dsk/c18t7d7 Alternate Link
PV Status unavailable
Total PE 1151
Free PE 0
Autoswitch On

PV Name /dev/dsk/c19t8d0
PV Name /dev/dsk/c18t8d0 Alternate Link
PV Status unavailable
Total PE 1151
Free PE 0
Autoswitch On


how to make them PV Status available...
please suggest.

[melvyn burnard]

I would check the syslog file, is there anything in there about a path failing? Looks like you have lost a connection to the discs in my opinion

[Sivakumar TS]

Dear Bunty,

1. Is the disks appear CLAIMED in ioscan -fnCdisk

if so

2. Could you do #diskinfo on any onf the disk and get info.

3. try pvdisplay on any of the disks.

Mostly it would be a connectivity issue as this is a alternate link and AS the VG is OK.

With Regards,

Siva.

[Torsten.]

Your PVs are LUNs stored on an array. Usually there are more than one path to the LUN (Alternate Link). So your second path tothe array seems to be broken. Check the connection (SCSI or FC cable, switch, HBA...).

[Bunty....]

# pvdisplay /dev/dsk/c19t8d0
--- Physical volumes ---
PV Name /dev/dsk/c19t8d0
PV Name /dev/dsk/c18t8d0 Alternate Link
VG Name /dev/vg03
PV Status unavailable
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 32
Total PE 1151
Free PE 0
Allocated PE 1151
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On


# diskinfo /dev/dsk/c19t8d0
diskinfo: Character device required

# diskinfo /dev/rdsk/c19t8d0
diskinfo: can't SIOC_INQUIRY /dev/rdsk/c19t8d0: I/O error

#ioscan -fnC disk
::
::
disk 165 0/0/10/1/0.11.15.0.0.8.0 sdisk CLAIMED DEVICE DGC CX700WDR10
/dev/dsk/c19t8d0 /dev/rdsk/c19t8d0
disk 166 0/0/10/1/0.11.15.0.0.8.1 sdisk CLAIMED DEVICE DGC CX700WDR10
/dev/dsk/c19t8d1 /dev/rdsk/c19t8d1
::
::



please suggest what to do?
it too urgent

[Deoncia Grayson_1 · Accepted solution]

The fact that you can't do a diskinfo to this disk means the disk is no longer available even though when you do an ioscan it shows up claimed. If you try to do a dd to that disk, I'm pretty sure that won't work as well, but you can try it:

dd if=/dev/rdsk/c19t8d0 of=/dev/null bs=512

if you get no response, then your disk needs to be replaced as soon as possible.

[melvyn burnard]

Ok, so that indicates you cannot talk top that disk. As it has an Alternate Link, what happens if you try the diskinfo to the c18 device?
If that responds, you have a problem with the hardware in path c19, if it fails, you have a problem in your disc array
In either case, you have a hardware issue.

[Bunty....]

same problem with c18:

# diskinfo /dev/dsk/c18t9d2
diskinfo: Character device required

# diskinfo /dev/rdsk/c18t9d2
diskinfo: can't SIOC_INQUIRY /dev/rdsk/c18t9d2: I/O error

please suggest soon

[melvyn burnard]

Get a hardware call placed for your disk array, it appears to be faulty

[Torsten.]

Since the devices are CLAIMED in ioscan but not accessible, this looks like any kind of security problem. Did you (or somebody else) change the security (zoning) settings of the array, switch or SAN?

[vaman]

If you have vg configuration saved in /etc/lvmconf/ , you can try restore one of the disk by the following command.
vgchange -a n vg03.
vgcfrestore -n /dev/vg03 /dev/rdsk/c19t7d6
vgchange -a y vg03
& see vgdisplay -v vg03 & look for c19t7d6
If it is working ( disk is available) you can proceed with rest of disks.

GoodLuck!
V.

[Shameer.V.A]

Hi Bunty,
I'm also suspecting there is some zoning /security setting , which is disturbed; else you are having some problem with array controller.

Which is the storage array you have?? Check the array logs for any error (armlog, logprn, armdsp for VA series ).for Controller failure/Link disturbance.

Have you connected more than one server to Storage in your SAN??. Try to access the LUNs for other servers on the storage. There may be some issue with the array controller.

Also try through
#fcmsutil /dev/tdx
where tdx is the fibre adapter device file.

Please post the result

shameer