topic Re: error message in Operating System - HP-UX

error message

M. Tariq Ayub — Sun, 29 May 2005 19:39:07 GMT

I am getting the following message. What is the reason. From SAM i saw that only c3t6d0 is in vg00.

[root@sydsux2] vgdisplay -v vg00
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 1
Max PE per PV 4350
VGDA 2
PE Size (Mbytes) 4
Total PE 4340
Alloc PE 4340
Free PE 4340
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 84
Current LE 21
Allocated PE 21
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 256
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 140
Current LE 35
Allocated PE 35
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 128
Allocated PE 128
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 128
Allocated PE 128
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 256
Current LE 64
Allocated PE 64
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 128
Allocated PE 128
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 672
Current LE 168
Allocated PE 168
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 13648
Current LE 3412
Allocated PE 3412
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Physical volumes ---
PV Name /dev/dsk/c3t6d0
PV Status available
Total PE 4340
Free PE 0

Re: error message

Bill Hassell — Sun, 29 May 2005 20:44:31 GMT

You have a failed disk in vg00. It appears that this volume group is mirrored so your system will still run OK. If you look in syslog, you'll probably see disk failure messages. How you replace the bad disk and re-mirror the replacement depends on the computer you're using, where the disk is located and the version of HP-UX you are running.

Re: error message

M. Tariq Ayub — Sun, 29 May 2005 21:07:21 GMT

I am using HPUX 11.0. The thing happened before my joining. In ioscan my system shows c3t5d0 and c3t6d0. Now i want to mirror it. Do i need to take additional care or jsut start doing mirroring in normal procedure.

Re: error message

Bill Hassell — Sun, 29 May 2005 22:02:30 GMT

The vgdisplay message implies that c3t5d0 was already added to the volume group (using vgextend). vgdisplay will have to display without the error message before you mirror the disks. If necessary, you may have to remove the c3t5d0 disk (lvreduce -m0 and vgreduce) to eliminate the error message, then re-add the disk to the volume group. vgdisplay should show the 2 disks with no errors.

Now mirror just one lvol:

lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c3t5d0

If there are no errors, sync the mirror:

lvsync /dev/vg00/lvol1

To see that it was mirrored successfully:

lvdisplay -v /dev/vg00/lvol1

If all the above is OK, repeat the lvextend -m 1 and lvsync commands for each lvol.

Re: error message

M. Tariq Ayub — Sun, 29 May 2005 22:42:27 GMT

Can you give me the exacts syntext or command for excluding c3t5d0 from vg00.

Re: error message

Suraj Singh_1 — Mon, 30 May 2005 00:26:45 GMT

Hi,

1. Check if disk at c3t5d0 is actually faulty:
# diskinfo /dev/rdsk/c3t5d0
# dd if=/dev/null of=/dev/rdsk/c3t5d0 bs=512

2. Check if the root disk is/was mirrored:
# lvlnboot -v

3. Check the condition of mirrors:
# lvdisplay -v /dev/vg00/lvol1
NOTE: Look for stale words.

4. To remove the mirrors:
# lvreduve -m 0 /dev/vg00/lvol /dev/dsk/c3t5d0 ; See man lvreduce (You might have to use -f option)

5. Reduce Volume Group:
# vgreduce /dev/vg00 /dev/dsk/c3t5d0

6. Add the new disk at the same target id, and create PV
# pvcreate /dev/rdsk/c3t5d0
7. # vgextend /dev/vg00 /dev/dsk/c3t5d0
8. # lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c3t5d0

Do this for all the lvols in vg00.

Hope this helps..

Regards

Re: error message

M. Tariq Ayub — Mon, 30 May 2005 00:36:44 GMT

[root@sydsux2] diskinfo /dev/rdsk/c3t5d0
SCSI describe of /dev/rdsk/c3t5d0:
vendor: SEAGATE
product id: ST318416N
type: direct access
size: 17783240 Kbytes
bytes per sector: 512
[root@sydsux2] dd if=/dev/null of=/dev/rdsk/c3t5d0 bs=512
0+0 records in
0+0 records out
[root@sydsux2] lvlnboot -v

lvlnboot: Couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group

Re: error message

Suraj Singh_1 — Mon, 30 May 2005 02:33:16 GMT

Hi,

Your root disk was mirrored indeed.

Refer to my response above, you may go ahead with point no. 4 onwards.

Regards

Re: error message

Bill Hassell — Mon, 30 May 2005 07:55:13 GMT

You wrote:

>> root@sydsux2] dd if=/dev/null of=/dev/rdsk/c3t5d0 bs=512
>> 0+0 records in
>> 0+0 records out

>> [root@sydsux2] lvlnboot -v

>> lvlnboot: Couldn't query physical volume "/dev/dsk/c3t5d0": The specified path does not correspond to physical volume attached to this volume group

The dd commadn indicates that there is something seriously wrong with the disk c3t5d0. Although diskinfo (a low-level SCSI ID request) reporst a valid 18Gb disk, dd cannot read a single block--the disk reports that it is zero-length to a read request. The lvlnboot command indicates that the disk does not have valid LVM information on it even though it has been identified as part of the boot/swap/dump volumes.

Start by removing the disk from your volume group:

vgreduce vg00 /dev/dsk/c3t5d0

There should be no errors with this command. If the command reports that there are extents in use on the disk, run the command:

pvdisplay /dev/dsk/c3t5d0

and see what Curr LV says. It should be 0 and Stale PE should be greater than 0. Post the output of the above pvdisplay command.

Re: error message

M. Tariq Ayub — Mon, 30 May 2005 18:24:55 GMT

I am getting the following out put

[root@sydsux2] vgreduce vg00 /dev/dsk/c3t5d0
vgreduce: Couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group

Re: error message

Senthil Kumar .A_1 — Mon, 30 May 2005 20:52:22 GMT

Hi Tariq,

I suspect that ur Block device file must be missing...for c3t6d0..

Why don't you check it out by..

ll /dev/dsk/c3t6d0

If its missing...

Then do the following to restore it..

ioscan -fnC disk.

Then take note the hardware path..

Then insf -e -H

HW_PATH should be something like 0/2/1/1.0.4

Then check if the file is restored..
if restored..

Check vgdisplay -v /dev/vg00..

If it looks healthy..

do vgsync or lvsync to restore mirror..

Or could start from the scratch..by vgreducing and following Suraj's method..

Regards.

Re: error message

Devender Khatana — Mon, 30 May 2005 21:00:57 GMT

Hi,

Use -f option of vgreduce to force reduce from missing physical volumes. From the man pages of vgreduce.
===============================================
-f vg_name force reduction of missing physical volume(s) in a given volume group. This option does not require a physical volume (PV) to be supplied on the command line. vgreduce obtains the name of each physical volume (PV) belonging to the volume group from the file /etc/lvmtab. It then reads the LVM structures from each PV and compares these with that held by the kernel to work out which PVs are missing. PVs which are missing will be candidates for removal. If all the physical extents on the missing PV are free then it will be removed from the volume group. Otherwise vgreduce will report the physical to logical extent mapping. For missing PVs, which have extents in use, you must free up all the extents by using lvreduce(1M) or lvremove(1M) and re-run vgreduce with the -f option. This option is most commonly used when the vgdisplay(1M) command shows "Cur PV" higher than "Act PV" and all of the PVs belonging to the volume group are attached. This option only works on PVs and not on links.
==========================================
So you do a check wheather it works straight away by
#vgreduce -f /dev/vg00
If it reports error them do a lvreduce for all lvols by

#lvreduce -m 0 /dev/vg00/lvol1 /dev/dsk/c3t5d0

Then repeat this for all lvols in vg00. Once done check through vgdisplay -v vg00 for error.

Also what does your lvdisplay -v /dev/vg00/lvol* displays regarding mirror status currently?

Then replace disk and recreate mirror.

HTH,
Devender

Re: error message

M. Tariq Ayub — Mon, 30 May 2005 21:14:47 GMT

[root@sydsux2] ll /dev/dsk/c3t5d0
brw-r----- 1 bin sys 31 0x035000 Jul 16 2002 /dev/dsk/c3t5d0
[root@sydsux2]
[root@sydsux2] vgreduce -f /dev/vg00
vgreduce: Couldn't query physical volume "/dev/dsk/c3t5d0":
The specified path does not correspond to physical volume attached to
this volume group
[root@sydsux2] lvreduce -m 0 /dev/vg00/lvol1 /dev/dsk/c3t5d0
lvreduce: "MirrorCopies" parameter "0" is not smaller than existing number "0";
therefore no mirrors are removed.

Re: error message

Devender Khatana — Mon, 30 May 2005 21:31:13 GMT

Hi,

It means your mirroring is allready removed and your disk is not accessible. Can you also post current output of

#strings /etc/lvmtab
#vgdisplay -v /dev/vg00
#pvdisplay -v /dev/dsk/c3t5d0

HTH,
Devender

Re: error message

Senthil Kumar .A_1 — Tue, 31 May 2005 09:44:59 GMT

Hi Tariq,

I meant to check the block file of c3t5d0 instead of c3t6d0... anyway u got it right..

I'm just working out to simulate your situation in my test box, i will chwck whether i can find a workaround or not..

Till then,

...Best of luck in your endevour...

Re: error message

Senthil Kumar .A_1 — Tue, 31 May 2005 11:31:58 GMT

Hi Tariq,

Good news, I was able to create the same situation in my test machine as you are facing...

I can see two issues..

either there is a device file problem for accessing your disk.

or the second HDD c3t5d0 is gone bad.

Assuming that the HDD is fine, I'm attaching a file of the experimentation i conducted in my test box,... and finally i have show in it how i recovered.. go through the entire stuff..

If the HDD is gone bad.. i will get back to u on how to replace the disk..

First check my attachment...

Regards.

Re: error message

M. Tariq Ayub — Tue, 31 May 2005 18:43:15 GMT

Hi Kumar,

I am confused about the vgcfgrestore

vgcfgrestore -n vg00 -o /dev/rdsk/c2t1d0 /dev/rdsk/c3t2d0
Volume Group configuration has been restored to /dev/rdsk/c3t2d0

we should restore c3t2d0 information to c2t2d0 as c2t2d0 is having problem.

Please clarify.

Re: error message

Steven E. Protter — Tue, 31 May 2005 20:03:32 GMT

This command is supposed to restore the volume group configuration to both disks in the command.

vgcfgrestore -n vg00 -o /dev/rdsk/c2t1d0 /dev/rdsk/c3t2d0

strings /etc/lvmtab

Perhaps c2t1d0 or c1t2d0 are not part of vg00.

Or the command should have been written thus:

vgcfgrestore -n vg00 -o /dev/rdsk/c2t2d0 /dev/rdsk/c3t2d0

SEP

Re: error message

M. Tariq Ayub — Tue, 31 May 2005 20:07:35 GMT

I have solved the problem by only restoring vg information on the fail disk.

Thanks everyone for helping me.