pvdisplay: pvstatus unavailable

[Lee Abell]

I have 3 disks which when I do a pvdisplay on them they have a pvstatus of unavailiable. They are 8.9.0 c0t9d0, 8.10.0 c0t10d0 & 8.11.0 c0t11d0. When I do an ioscan they all show as available.

I am getting these errors in my syslog:

Sep 22 09:55:43 hp41 vmunix: Disk at 8.9.0 is not responding. Check device, power, and cables.
Sep 22 09:55:43 hp41 vmunix: Disk at 8.11.0 is not responding. Check device, power, and cables.
Sep 22 09:55:43 hp41 vmunix: Disk at 8.10.0 is not responding. Check device, power, and cables.


any help would be appreciated. Thanks!

[Pete Randall]

Paula,

What are the results of a diskinfo command against the same PVs? I suspect that they are either bad, or have cabling issues. Try running a "dd if=/dev/rdsk/cXtXdX of=/dev/null bs=1024k" against them and see if you get errors.


Pete

[Vitek Pepas]

Well, did you check power and cables? :)

[RolandH]

Hi Paula,

seems to me that the controller, where these disks are connected to is broken.

Can you do a ioscan -fn and attach the result to your next post, please.

Roland

[Lee Abell]

Here is the output from the diskinfos

hp41:/var/adm/syslog # diskinfo /dev/rdsk/c0t9d0
diskinfo: can't open /dev/rdsk/c0t9d0: No such device or address
hp41:/var/adm/syslog # diskinfo /dev/rdsk/c0t10d0
diskinfo: can't open /dev/rdsk/c0t10d0: No such device or address
hp41:/var/adm/syslog # diskinfo /dev/rdsk/c0t11d0
diskinfo: can't open /dev/rdsk/c0t11d0: No such device or address

Here is the iocan -fn
hp41:/var/adm/syslog # ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
bc 0 root CLAIMED BUS_NEXUS
ext_bus 0 8 scsi3 CLAIMED INTERFACE HP 28696A - Wide SCSI ID=6
target 0 8.9 target CLAIMED DEVICE
disk 0 8.9.0 disc3 CLAIMED DEVICE SEAGATE ST15150W
/dev/dsk/c0t9d0 /dev/floppy/c0t9d0 /dev/rdsk/c0t9d0 /dev/rfloppy/c0t9d0
target 1 8.10 target CLAIMED DEVICE
disk 1 8.10.0 disc3 CLAIMED DEVICE SEAGATE ST15150W
/dev/dsk/c0t10d0 /dev/floppy/c0t10d0 /dev/rdsk/c0t10d0 /dev/rfloppy/c0t10d0
target 2 8.11 target CLAIMED DEVICE
disk 2 8.11.0 disc3 CLAIMED DEVICE HP C2490WD
/dev/dsk/c0t11d0 /dev/floppy/c0t11d0 /dev/rdsk/c0t11d0 /dev/rfloppy/c0t11d0
ext_bus 1 16 scsi3 CLAIMED INTERFACE HP 28696A - Wide SCSI ID=7
target 3 16.5 target CLAIMED DEVICE
disk 3 16.5.0 disc3 CLAIMED DEVICE HP C2490WD
/dev/dsk/c1t5d0 /dev/floppy/c1t5d0 /dev/rdsk/c1t5d0 /dev/rfloppy/c1t5d0
target 4 16.6 target CLAIMED DEVICE
disk 4 16.6.0 disc3 CLAIMED DEVICE HP C2490WD
/dev/dsk/c1t6d0 /dev/floppy/c1t6d0 /dev/rdsk/c1t6d0 /dev/rfloppy/c1t6d0
target 5 16.9 target CLAIMED DEVICE
disk 5 16.9.0 disc3 CLAIMED DEVICE HP C2490WD
/dev/dsk/c1t9d0 /dev/floppy/c1t9d0 /dev/rdsk/c1t9d0 /dev/rfloppy/c1t9d0
target 6 16.12 target CLAIMED DEVICE
disk 6 16.12.0 disc3 CLAIMED DEVICE HP C2490WD
/dev/dsk/c1t12d0 /dev/floppy/c1t12d0 /dev/rdsk/c1t12d0 /dev/rfloppy/c1t12d0
ext_bus 2 52 scsi1 CLAIMED INTERFACE HP 28655A - SE SCSI ID=7
target 7 52.0 target CLAIMED DEVICE
tape 0 52.0.0 tape2 CLAIMED DEVICE HP HP35480A
/dev/diag/rmt/c2t0d0 /dev/rmt/0mn /dev/rmt/c2t0d0BESTb
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c2t0d0BESTn
/dev/rmt/0mb /dev/rmt/c2t0d0BEST /dev/rmt/c2t0d0BESTnb
target 8 52.2 target CLAIMED DEVICE
disk 7 52.2.0 disc3 CLAIMED DEVICE TOSHIBA CD-ROM XM-4101TA
/dev/dsk/c2t2d0 /dev/floppy/c2t2d0 /dev/rdsk/c2t2d0 /dev/rfloppy/c2t2d0
target 9 52.6 target CLAIMED DEVICE
disk 8 52.6.0 disc3 CLAIMED DEVICE SEAGATE ST32550N
/dev/dsk/c2t6d0 /dev/floppy/c2t6d0 /dev/rdsk/c2t6d0 /dev/rfloppy/c2t6d0
lanmux 0 56 lanmux0 CLAIMED INTERFACE LAN/Console
tty 0 56.0 mux4 CLAIMED INTERFACE
/dev/diag/mux0 /dev/diag/tty0p1 /dev/tty0p0
/dev/diag/tty0p0 /dev/mux0 /dev/tty0p1
lan 0 56.1 lan3 CLAIMED INTERFACE
/dev/diag/lan0 /dev/ether0 /dev/lan0
lantty 0 56.2 lantty0 CLAIMED INTERFACE
/dev/diag/lantty0 /dev/lantty0
processor 0 62 processor CLAIMED PROCESSOR Processor
memory 0 63 memory CLAIMED MEMORY Memory

Thanks!

[Lee Abell]

Here is the output from the dd commands. thanks!

dd if=/dev/rdsk/c0t9d0 of=/dev/null bs=1024k
/dev/rdsk/c0t9d0: No such device or address
dd: cannot open /dev/rdsk/c0t9d0
hp41:/var/adm/syslog # dd if=/dev/rdsk/c0t10d0 of=/dev/null bs=1024k
/dev/rdsk/c0t10d0: No such device or address
dd: cannot open /dev/rdsk/c0t10d0
hp41:/var/adm/syslog # dd if=/dev/rdsk/c0t11d0 of=/dev/null bs=1024k
/dev/rdsk/c0t11d0: No such device or address
dd: cannot open /dev/rdsk/c0t11d0
hp41:/var/adm/syslog #

[Ravi_8]

Hi paula

check the power connections to these cables.
#ioscan -fnC disk
if this shows all 3 disks are claimed,
#diskinfo /dev/rdsk/cXtXdX
if this results disk size 0 (zero) then problem in disks, sometimes this (diskinfo) shows the real size of disks even though disks are in problem. to conclude do dd on all disks
#dd if=/dev/rdsk/cXtXdX of=/dev/null bs=1024k

if yiu get any I/O error then disks are in problem which needs replacement

[Pete Randall]

Paula,

Have you ensured that the cabling, termination and power are all connected properly?


Pete

[Stefan Farrelly]

pvdisplay requires a much higher level of connectivity to a disk than ioscan. ioscan just checks for power and if the device is advertising on the scsi bus. pvdisplay actually interrogates a disk itself - to get size, model number etc.

so if ioscan can see them but not pvdisplay then the connectivity is there, just not complete. Either these 3 drives have had their power interrupted at some point which can cause LVM to think they are not available anymore, or perhaps one disk of the 3 is failing and broadcasting scsi errors which makes all 3 look unavailable.
You could try a reboot, this will allow LVM to restart and cleanup any past connection problems. Check stm (LOGTOOL) to see if any hardware errors being broadcast - this may show that one disk is logging lots of errors and causing your problem.

I would shutdown, restart to single user mode, then ioscan, and if ok then pvdisplay on each. If same problem then remove the disks one at a time to see if one is causing all of them to be unavailable.

[RolandH]

Paula,

have you just added these controller and disks. I wondering why the controller where these disks belonging to has id=6 and not id=7. Perhaps you have also a disk, which has id=6 on this controller and you get a scsi conflict.

Roland

[Bhuvaneswari Selvaraj]

Hi,

Did you try rebooting the system... LVM will do the initialization again and then check whether there is still come error.
Try using EMS and check the status of the pvstatus. EMS gives you a detailed description of the problem if any.