lvlnboot -v error

[Suraj K Sankari]

Hi HP Guru's,

We are not able to take Ignite Backup due to below lvlnboot error. storage person did a mistake he assign this physical path to another system because we are no longer using those vg’s so we have been, removed all those vg’s with rm –Rf command .
Still we are getting this error when firing lvlnboot

As per HP engineer suggestion we have rebooted the server but it won’t helpus

Please anyone suggest how to remove these paths which are no longer in the system.

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t0d0s2 (0/0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t0d0s2 (2/0/1/1/0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t0d0s2
/dev/dsk/c2t0d0s2
Root: lvol3 on: /dev/dsk/c0t0d0s2
/dev/dsk/c2t0d0s2
Swap: lvol2 on: /dev/dsk/c0t0d0s2
/dev/dsk/c2t0d0s2
Dump: lvol2 on: /dev/dsk/c0t0d0s2, 0
Dump: lvol9 on: /dev/dsk/c0t0d0s2, 1

lvlnboot: "/dev/vg_sapdata16/group": not a character device.
lvlnboot: "/dev/vg_sapdata17/group": not a character device.
lvlnboot: "/dev/vg_sapdata18/group": not a character device.
lvlnboot: "/dev/vg_sapdata19/group": not a character device.
lvlnboot: "/dev/vg_sapdata20/group": not a character device.
lvlnboot: "/dev/vg_sapdata21/group": not a character device.
lvlnboot: "/dev/vg_sapdata22/group": not a character device.
lvlnboot: "/dev/vg_sapdata23/group": not a character device.
lvlnboot: "/dev/vg_sapdata24/group": not a character device.
lvlnboot: "/dev/vg_sapdata25/group": not a character device.
lvlnboot: "/dev/vg_sapdata26/group": not a character device.
lvlnboot: "/dev/vg_sapdata27/group": not a character device.
lvlnboot: "/dev/vg_sapdata28/group": not a character device.
lvlnboot: "/dev/vg_ora_logC/group": not a character device.
lvlnboot: "/dev/vg_ora_logD/group": not a character device.
lvlnboot: "/dev/vg_ora_mlogC/group": not a character device.
lvlnboot: "/dev/vg_ora_mlogD/group": not a character device.
#

Any suggestion......
Suraj

[Ivan Krastev]

These group files are part from volume groups. If the groups was removed feel free to remove it.

regards,
ivan

[Ganesan R]

Hi Suraj,

It's because those volume groups were not properly exported or removed. So those entries still exist on lvmtab file

What you could try is move the /etc/lvmtab file and recreate it using vgscan.

[Suraj K Sankari]

Hi Ivan,
We already removed those vg's from the system.

# ls -l "/dev/vg_sapdata16/group"
/dev/vg_sapdata16/group not found
# ls -l /dev/vg_sapdata16
/dev/vg_sapdata16 not found
# ls -l /dev | grep vg_sapdata16


Suraj

[Suraj K Sankari]

Hi Ganesen,
I already tried this, what I did I move the old lvmtab and I did vgscan after creating the new /etc/lvmtab.
If I give the lvlnboot â v again I am getting error see the below.

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t0d0s2 (0/0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t0d0s2 (2/0/1/1/0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t0d0s2
/dev/dsk/c2t0d0s2
Root: lvol3 on: /dev/dsk/c0t0d0s2
/dev/dsk/c2t0d0s2
Swap: lvol2 on: /dev/dsk/c0t0d0s2
/dev/dsk/c2t0d0s2
Dump: lvol2 on: /dev/dsk/c0t0d0s2, 0
Dump: lvol9 on: /dev/dsk/c0t0d0s2, 1

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


Suraj

[TTr]

>We already removed those vg's from the system.
How did you do that? By deleting the /dev/vg_sapdata??/lv* files?
Post the output of "strings /etc/lvmtab"

[Suraj K Sankari]

Hi,

We removed those directory by rm â Rf /dev/vg_sapdata16 like this we remove all other vgâ s also.

Please see the attached strings output.

Suraj

[Ganesan R]

Hi Suraj,

So now you are out of that initial error.

The new error indicates that "/dev/dsk/c62t0d0" disk is part of some VG and currently not accessible by the system.

Find out the VG name in which this disk belongs to and the status of the disk by ioscan command. Fix the disk issue if you are using that VG. If not using remove the VG from the system.

[Ganesan R]

Hi Suraj,

There is another scenario for this error.
Sometime ioscan and diskinfo will show the disk is in good condition.

Reason is that when a system is rebooted or the volume group is
activated with a disk(s) or a path missing. The disk or path is later restored
but the volume group is unaware of this change until it is re-activated.

Reactive it using vgchange

[James R. Ferguson · Accepted solution]

Hi:

> We removed those directory by rm ...

Then you did this incorrectly. You should have 'vgexport'ed the volume groups you didn't want. This would have cleaned up the device files *and* corrrectly removed them from the '/etc/lvmtab'.

Do:

# mv /etc/lvmtab /etc/lvmtab.old
# vgscan -av
# vgchange -a y
# lvlnboot -R

You may want to check the order of your 'pvlinks' afterwards to insure that your primary and alternate paths to each volume group are as you choose.

Regards!

...JRF...

[TTr]

> We removed those directory by rm â  Rf /dev/vg_sapdata16 like this we remove all other vgâ  s also.
Have you heard of vgexport?
Is the lvmtab you posted before or after you did the vgscan process? The system still has the configuration of the volume groups and the disks that belong to them. I would try "vgexport" and if it fails I would try recreating the "lv" and "rlv" device files in the /dev/vg???? directory and try vgexport again.

[Suraj K Sankari]

When we tried vgexport we got error like physical path not available then we decided to remove those directory by rm â R command.

Suraj

[Torsten.]

NEVER remove a VG with "rm" only.

You will have a lot of problems later.

What do you get from

# ll /etc/lvmconf/

and

# strings /etc/lvmtab

Are there still informations about the "removed" VGs?

[Suraj K Sankari]

Yes, removed vg's information are there under /etc/lvmconf and /etc/lvmtab also, i have tried to create the new lvmtab but after creating the new lvmtab if i do vgdiaplay -v then i am getting error for every vg.

Attached file is the output of ll /etc/lvmconf and strings /etc/lvmtab.


Suraj

[Torsten.]

Nothing attached.

Please show the error from vgdisplay too.

[Suraj K Sankari]

Sorry Sorry here is the attached file

[Ganesan R]

Hi Suraj,

Your attachment shows that the information still exist on the lvmtab file. Note that the original lvmtab file should not be there when you run vgscan command. If exists it will read that file instead of scanning the entire disks.

Have you moved or renamed lvmtab file before run vgscan?

[Suraj K Sankari]

Yes, before vgscan I have moved the /etc/lvmtab.

if new lvmtab file will be there then vgdisplay is giving lots of errors thats why I moved the old one again.

Suraj

[Ganesan R]

Its strange then. You need to do ground work now. I believe the system is still able to see some of the disks which you mention as "assign the physical path to another system". if system is able to see those disks then those vg info also will be imported to lvmtab. Compare the ioscan with new lvmtab file.