1752480 Members
5447 Online
108788 Solutions
New Discussion юеВ

VG00 /lvlnboot

 
SOLVED
Go to solution
DAVID99_1
Advisor

VG00 /lvlnboot

Dear Experts ,

unfortunately i deleted Three file in my /dev/vg00 with
#rm -rf -i /vg00
Here i pressed Y Three times
after that i checked with below commands
#bdf===> in this iam not getting /stand
#vgdisplay
it cannot display the information
after that i created
#mknod /dev/vg00/group c 64 0x0000
after this vg diplay command is giving below output

root@sap#vgdisplay
vgdisplay: LVM group file has an invalid minor number. Use the format: 0xNN0000.
vgdisplay: Warning: couldn't query physical volume "/dev/disk/disk13_p2":
Inappropriate ioctl for device - the command was attempted on a
logical volume device rather than the control device.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c11t0d0s2":
Inappropriate ioctl for device - the command was attempted on a
logical volume device rather than the control device.
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 10
Open LV 9
Max PV 16
Cur PV 2
Act PV 0
Max PE per PV 4384
VGDA 0
PE Size (Mbytes) 32
Total PE 0
Alloc PE 0
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 2192g
VG Max Extents 70144
==================
and #lvlnboot -v is giving
lvlnboot: LVM group file has an invalid minor number. Use the format: 0xNN0000.
lvlnboot: Couldn't query physical volume "/dev/disk/disk13_p2":
Inappropriate ioctl for device - the command was attempted on a
logical volume device rather than the control device.

i have a ignite back-up and we are using
rx8640-hp-ux 11i v3

advance thanks for urs reply
David
7 REPLIES 7
Michal Kapalka (mikap)
Honored Contributor

Re: VG00 /lvlnboot

hi,

the mknod should be :

mknod /dev/vg00/group c 64 0x000000

and them recreate also the files for Lvol[1-x]

# ll /dev/vg00
total 0
crw-r----- 1 root sys 64 0x000000 Jun 29 08:34 group
brw-r----- 1 root sys 64 0x000001 Jun 29 08:34 lvol1
brw-r----- 1 root sys 64 0x000002 Jun 29 08:34 lvol2
brw-r----- 1 root sys 64 0x000003 Jun 29 08:34 lvol3
brw-r----- 1 root sys 64 0x000004 Jun 29 08:34 lvol4
brw-r----- 1 root sys 64 0x000005 Jun 29 08:34 lvol5
brw-r----- 1 root sys 64 0x000006 Jun 29 08:34 lvol6
brw-r----- 1 root sys 64 0x000007 Jun 29 08:34 lvol7
brw-r----- 1 root sys 64 0x000008 Jun 29 08:34 lvol8
crw-r----- 1 root sys 64 0x000001 Jun 29 08:34 rlvol1
crw-r----- 1 root sys 64 0x000002 Jun 29 08:34 rlvol2
crw-r----- 1 root sys 64 0x000003 Jun 29 08:34 rlvol3
crw-r----- 1 root sys 64 0x000004 Jun 29 08:34 rlvol4
crw-r----- 1 root sys 64 0x000005 Jun 29 08:34 rlvol5
crw-r----- 1 root sys 64 0x000006 Jun 29 08:34 rlvol6
crw-r----- 1 root sys 64 0x000007 Jun 29 08:34 rlvol7
crw-r----- 1 root sys 64 0x000008 Jun 29 08:34 rlvol8

mikap
Matti_Kurkela
Honored Contributor
Solution

Re: VG00 /lvlnboot

> #rm -rf -i /vg00

This is unlikely to be the command you actually ran. On a normal HP-UX system, there should be nothing named "vg00" in the root directory, so the command should have ended harmlessly with a "No such file or directory" error message. Was there some strange local customization or did you actually do something else? (Check the shell's command history!)

/dev/vg00/group is the "LVM group file" the error messages are talking about. So the first thing would be to see what it looks like currently:

ll /dev/vg00/

Please show the output.

> mknod /dev/vg00/group c 64 0x0000

Hmm... I would have expected this command to require six hex digits for the minor number (i.e. 0x000000). Perhaps the wrong length of the number caused it to do something strange. The output of "ll /dev/vg00/" should clear the mystery.
MK
Bijeesh
Respected Contributor

Re: VG00 /lvlnboot

Hi,
>>unfortunately i deleted Three file in my /dev/vg00 <<
If so the deleted files may be,

crw-r----- 1 root sys 64 0x000000 Aug 12 06:51 group
brw-r----- 1 root sys 64 0x000001 Aug 12 06:51 lvol1
brw-r----- 1 root sys 64 0x000002 Aug 12 06:51 lvol2

Like Matti mentioned,check the output of #ll /dev/vg00
Then try to create the vggroup file using
#mknod /dev/vg00/group c 64 0x000000

Also you need to create the block device files for the LVs lvol1 and lvol2.(confirm then do)..,
#mknod /dev/vg00/lvol1 b 64 0x000001
#mknod /dev/vg00/lvol2 b 64 0x000002

Hope this will work.
DAVID99_1
Advisor

Re: VG00 /lvlnboot

hi kurkela/Brijeesh
first of all thanks for your quick reply

i created group file and block devicefile

it all ok but
# cd /dev/vg00
#ll
total 0
crw-r--r-- 1 root sys 64 0x000000 Sep 23 12:37 group
brw-r--r-- 1 root sys 64 0x000001 Sep 23 12:46 lvol1
brw-r----- 1 root sys 64 0x00000a Jul 20 10:18 lvol10
brw-r----- 1 root sys 64 0x000002 Dec 1 2009 lvol2
brw-r----- 1 root sys 64 0x000003 Dec 1 2009 lvol3
brw-r----- 1 root sys 64 0x000004 Dec 1 2009 lvol4
brw-r----- 1 root sys 64 0x000005 Dec 1 2009 lvol5
brw-r----- 1 root sys 64 0x000006 Dec 1 2009 lvol6
brw-r----- 1 root sys 64 0x000007 Dec 1 2009 lvol7
brw-r----- 1 root sys 64 0x000008 Dec 1 2009 lvol8
brw-r----- 1 root sys 64 0x000009 Dec 1 2009 lvol9
crw-r----- 1 root sys 64 0x00000a Jul 20 10:18 rlvol10
crw-r----- 1 root sys 64 0x000002 Dec 1 2009 rlvol2
crw-r----- 1 root sys 64 0x000003 Dec 1 2009 rlvol3
crw-r----- 1 root sys 64 0x000004 Dec 1 2009 rlvol4
crw-r----- 1 root sys 64 0x000005 Dec 1 2009 rlvol5
crw-r----- 1 root sys 64 0x000006 Dec 1 2009 rlvol6
crw-r----- 1 root sys 64 0x000007 Dec 1 2009 rlvol7
crw-r----- 1 root sys 64 0x000008 Dec 1 2009 rlvol8
crw-r----- 1 root sys 64 0x000009 Dec 1 2009 rlvol9
in above out put we didn't get lvol1's charecter device file
i tried to create this
it says mknod:already exists.
and in
# bdf
/stand is not present
Bijeesh
Respected Contributor

Re: VG00 /lvlnboot

hi,
Did you tried with
#mknod /dev/vg00/rlvol1 c 64 0x000001

I guess you may type lvol1 instead of rlvol1.
DAVID99_1
Advisor

Re: VG00 /lvlnboot

hi bijeesh

finally i got it .
your quick responsce is Appriciatable.

ThanQ bye
DAVID99_1
Advisor

Re: VG00 /lvlnboot

I have found a solution to this question from our forum mates.