file system check failure, aborting ...

[sreedhar2u]

# pvdisplay -v /dev/dsk/c5t0d0
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t0d0":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t2d0":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t4d0":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query all of the physical volumes.
pvdisplay: Couldn't retrieve the names of the physical volumes
belonging to volume group "/dev/vg01".
pvdisplay: Cannot display physical volume "/dev/dsk/c5t0d0".

[Bill Hassell]

> Local CPU ID = 1761581075, hex value=0x68ff9813

So your computer ID is 0x68ff9813 (in hex).

> /dev/rdsk/c5t0d0:
CPUID=0x68ff9813 (1761581075), VGID 0x4194a5e6, PVID 0x4194a5cb

So these 3 disks do belong to your computer and they are all part of the same volume group (VGID=0x4194a5e6). And you can read the LVM header with no problems. Run this command:

# strings /etc/lvmtab

I suspect that vg01 has different disks listed in lvmtab. The fix will be to:

# ll /dev/vg01/group
(this will show you the current group minor number, probably 0x010000)

# vgexport -s -m vg01.map vg01
# mkdir /dev/vg01
# mknod /dev/vg01/group c 64 0x010000
(0x010000 is from the previous ll command)

# vgimport -s -m vg01.map vg01
# vgchange -a y vg01

Now you should be able to run: mount -a
fsck as necessary.

[sreedhar2u]

I have files in /dev/vg01. will it create any problem if run the above commands?

# cd /dev/vg01
# ls -lrt
total 0
cr--r--r-- 1 root sys 64 0x010000 Nov 12 2004 group
br--r----- 1 root sys 64 0x010001 Nov 15 2004 lvol11
cr--r----- 1 root sys 64 0x010001 Nov 15 2004 rlvol11
cr--r----- 1 root sys 64 0x010003 Nov 23 2004 rlvol13
br--r----- 1 root sys 64 0x010003 Nov 23 2004 lvol13
br--r----- 1 root sys 64 0x010004 Nov 23 2004 lvol14
cr--r----- 1 root sys 64 0x010004 Nov 23 2004 rlvol14
br--r----- 1 root sys 64 0x010005 Nov 23 2004 lvol15
cr--r----- 1 root sys 64 0x010005 Nov 23 2004 rlvol15

[Bill Hassell]

Those files are pointing to non-existent disks. It would be better to run this command and post the results:

# strings /etc/lvmtab

vgexport will remove the directory /dev/vg01 and all the files. These are device files and they no longer work correctly. vgimport (as part of the above commands) will recreate these files and connect them with the correct disks.

[Torsten.]

@Bill:

Its posted earlier in this thread:

HP-UX-root}# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c2t0d0
/dev/vg01
/dev/dsk/c5t0d0
/dev/dsk/c5t2d0
/dev/dsk/c5t4d0
/dev/vg02
/dev/dsk/c2t1d0

[Deeos]

Hi ,


Could you do following stepsand give output once more:

#more /etc/mnttab

#mv /etc/lvmtab /etc/lvmtab.oldd

#vgscan -v

#vgdisplay -v

#vgdisplay -v vg01

#mount -a

#more /etc/mnttab


Regards
Deeos

[Deeos]

after

#vgscan -v

#strings /etc/lvmtab

[sreedhar2u]

Hi Bill,

I am getting the below error, while running vgimport

# vgimport -s -m vg01.map vg01
vgimport: Couldn't open MAPFILE "vg01.map".
vgimport: vg01.map: No such file or directory

[sreedhar2u]

Hi Bill,

came to the same stage, where we started.

# vgimport -s -m vg01.map vg01
# cd /dev/vg01
# ls
group lvol13 lvol15 rlvol13 rlvol15
lvol11 lvol14 rlvol11 rlvol14
# vgchange -a y vg01
vgchange: Couldn't activate volume group "vg01":
Quorum not present, or some physical volume(s) are missing.

# mount -a
vxfs mount: Cannot open /dev/vg01/lvol15: No such device or address
vxfs mount: Cannot open /dev/vg01/lvol14: No such device or address
mount: /dev/vg02/lvol201 is already mounted on /oradumps2
vxfs mount: Cannot open /dev/vg01/lvol13: No such device or address
vxfs mount: Cannot open /dev/vg01/lvol11: No such device or address
mount: /dev/vg00/lvol9 is already mounted on /apps
mount: /dev/vg00/lvol8 is already mounted on /var
mount: /dev/vg00/lvol7 is already mounted on /usr
mount: /dev/vg00/lvol6 is already mounted on /opt
mount: /dev/vg00/lvol5 is already mounted on /tmp
mount: /dev/vg00/lvol4 is already mounted on /local
mount: /dev/vg02/tarot2_2 is already mounted on /tarot2_2
mount: /dev/vg00/lvol1 is already mounted on /stand

[Bill Hassell]

> # vgimport -s -m vg01.map vg01
> vgimport: Couldn't open MAPFILE "vg01.map".
> vgimport: vg01.map: No such file or directory

There was a missing step. Normally, the system administrator will create map files for all the current volume groups. This must be done manually and I suspect that there aren't any map files in /etc/lvmconf.

So you'll need to create one. From your listings above, it appears that vg01 has 4 lvols numbered 11 12 13 and 14. Ans since we can see the serial number information from showLVMinfo, you can create the map file which will look like this:

cat /etc/lvmconf/vg01.map
VGID 0x68ff98134194a5e6
1 lvol11
2 lvol13
3 lvol14
4 lvol15

DISCLAIMER: I am assuming that this was the order of the lvols when they were first created. Without a map file, I am just guessing. After you use vgimport, vgchange and mount -a, you'll need to verify that the files are in the correct mount points.

Now you should be able to use vgimport:

(create /dev/vg01 and /etc/vg01/group with nothing else in the directory)
vgexport -s -m vg01.map vg01
vgchange -a y
mount -a

If the mount point names have the wrong files, make a list of which lvol has the required files for the destination mount point, then change /etc/fstab and remount the volumes.