/etc/lvmtab

[Stuart Lloyd_2]

My lvmtab is completely hosed. How do I create a new one?

[Helen French]

Try this:

# mv /etc/lvmtab /etc/lvmtab.old
# vgscan -a

[Ken Penland_1]

remove it, then do a vgscan -a

[Stuart Lloyd_2]

Couldn't stat physical volume "dev/dsk/c0t9d0":
Invalid argument
Physical Volume "/dev/dsk/c1t2d0" contains no LVM information

The Volume Group /dev/vg03/group was not matched with any Physical Volumes.

# more lvmtab
^CM-h^/dev/vg00
x
M-^K8M-@^Ky^A/dev/dsk/c0t5d0
/dev/vg01
x
Memory fault(coredump)

[Jeff Schussele]

Hi Stuart,

Make sure you remove the old file or at least move it out of /etc. vgscan will refer to the file & use it as a template therefore recreating the same problems you had before.

Rgds,
Jeff

[Stuart Lloyd_2]

Did that. Got the same results.

[A. Clay Stephenson]

What is your definition of a hosed lvmtab? You are using "more" on a binary file that happens to contain some string data. It's always (very statistically speaking, highly probable) that lvmtab will contain non-ASCII characters. A better technique is "strings /etc/lvmtab" to produce much more human readable text although occasionally some seemingly strange characters will appear because strings looks for sequences of 3 or more printable ASCII characters in secession for output.

[John Dvorchak]

The /etc/lvmtab file was not meant to be read directly with the pg or more commnand. Would you please post the results of:

# strings /etc/lvmtab

Then maybe we can get a hint as to the problem you are having.

John

[Stuart Lloyd_2]

# strings lvmtab
/dev/vg00
/dev/dsk/c0t5d0
/dev/vg01
/dev/dsk/c0t8d0
/dev/vgOra9
/dev/dsk/c1t5d0



It doesn't show my other disk with vg03.

[Patrick Wallek]

If you notice the error message in one of your replies, vgscan states that it could not stat physical volume /dev/dsk/c0t9d0. That indicates to me that the disk is dead.

Do an 'ioscan -fnC disk' and see if c0t9d0 shows up as NO_HW. If so, it is definitely dead and needs to be replaced.

[Stuart Lloyd_2]

target 0 8/4.5 tgt CLAIMED DEVICE
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
target 1 8/4.7 tgt CLAIMED DEVICE
ctl 0 8/4.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
target 2 8/4.8 tgt CLAIMED DEVICE
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
target 3 8/4.9 tgt NO_HW DEVICE
disk 2 8/4.9.0 sdisk NO_HW DEVICE SEAGATE ST39175LC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0

target 6 8/16/5.5 tgt CLAIMED DEVICE
disk 4 8/16/5.5.0 sdisk CLAIMED DEVICE QUANTUM ATLAS IV 36 SCA
/dev/dsk/c1t5d0 /dev/rdsk/c1t5d0

[Mel Burslan · Accepted solution]

this here is your dead ringer :

disk 2 8/4.9.0 sdisk NO_HW DEVICE SEAGATE ST39175LC

NO_HW, hence, the disk hardware is bad.

[Patrick Wallek]

Yep, it appears you have got a quite dead 9GB at c0t9d0. If you have an HP support contract, call HP and have them replace it.