couldn't query physical volume "/dev/dsk/c4t15d0"

[Darnnell Brown_2]

the following error is output from dmesg:SCSI: Attempt to access partially open device -- dev: bc012000
SCSI: Attempt to access partially open device -- dev: bc012000

vgdisplay, lvdisplay, pvdisplay do not work. The system reports cannot query volume group.

Strings /etc/lvmtab
shows all of the Volume group information. Everything is there.

vgscan -v
vgscan: Warning: couldn't query all of the physical volumes.
vgscan: The physical volume "/dev/dsk/c3t10d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c3t11d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c3t12d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c3t13d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c4t12d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c4t13d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c4t14d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c4t15d0" is already recorded in the "/etc/lvmtab" file.


What are these errors indicating? I assume that we are having some disk issues, however my ioscan -fnC disk output reports all of my hardware as claimed. Any information would be greatly appreciated.

[Vincenzo Restuccia]

diskinfo,STM.

[Ajitkumar Rane]

This is how u can find out.
dev: bc012000

convert "bc" to decimal this is the major number check the lsdev to find out to which device this refers to. ie 188.so its a disk "sdisk"
"01" is the controller no. ie c1
"2" is the target id.t2

that means your disk a c1t2d0 is bad.

Also check the loogtool in stm.that should help you to find which disks are giving I/O errors.
Somtimes you will find the disk as claimed in ioscan and also diskinfo will show the disk size as well but the LVM structures may be corrupt dur to bad tracks.It happend to me recently.

Hope this helps
Good luck

[John Pyle]

I'm having the same trouble and did not get this answer when I placed my call. Thank you for you answer to this question.

John Pyle
pyle@wapa.gov

[Shahul]

Hi

Check up whether anything is logged in syslog.log. I think one of ur disk is invisible to system now.

Confirm this by using
#ioscan -fnC disk
#diskinfo /dev/rdsk/cxtxdx

Before doing vgscan
#mv /etc/lvmtab /etc/lvmtab.old
#vgscan

Now do #strings /etc/lvmtab

Compare old output and newoutput, If not same ur HDD has got some problem.

Best of luck
Shahul

[Bill McNAMARA_1]

The message "already recorded..." is not a problem, it just means that those disks are already configured in LVM Volumes.

strings /etc/lvmtab
to see in which ones.

If you have lvm problems and vgdisplay doesn't work. Follow this flow:


ioscan -fnkCdisk
should see all the disks seen in
strings /etc/lvmtab as CLAIMED
vgchange -a y vg01
or whatever volume group you want activated
should say something to the effect of VG
activated and not can't query physical
device lalalala.
If it does say can't query physical device
mark down the device file, ioscan -fnkC
disk to make sure its CLAIMED, if it is
(or replaced) vgcfgrestore headers to disk
and reactivate the vg.
vgchange -a y -q n vgname
If you want to activate the VG with less
than 51% (quorum) of the PVs in the VG
available
vgdisplay -v vgname
should work once the vg is activated.
You should look at Physical Volume
information to make sure all is good.
At the top of the Output you should see Curr
PV and Act PV indicating how many PVs are
working and how many should be working.
mount -a
to mount the filesystems on the lvols in the
vg you just activated.
Repeat for all vgs defined in the etc/lvmtab

What you want to do in your case if disk
c4t15d0 is unqueryable, is to find out on which h/w path it's on.
ioscan -fnkCext_bus
mark down the hw address of the c4
the t15 will either be scsi id 15 or fc loop id in hex 0F, 1F, 2F, 3F, 4F, 5F ..

Make sure you have the corresponding device turned on and haven't changed it's id since configuring the VG initially.

Avoid as much as possible using vgscan because it's going to create your lvmtab in numerical order that it sees the disks in. This is more than likely not the way you want to configure it... because on vg activation all your io will bottleneck a single controller and all your ha alternate links will be configured going down a bus that no traffic will go to until something fails.. bit of a waste.. but at least vgscan will recover your lvmtab if you accidently removed it or had it corrupted.

Later,
Bill

[Roberto Arias]

Hello, please check that scsi bus is closed.
I attached file for check disk.

best regards