HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
cancel
Showing results for 
Search instead for 
Did you mean: 

vg00 lv recovery

 
SOLVED
Go to solution
scoooot
Frequent Advisor

vg00 lv recovery

I am going to try and give as much information as I can here. Forgive me if I've left anything out. I've also done some looking around in ITRC without being able to resolve my issue.

I have a 11.23 v2 ia64 hp server rx5670 and had 4 x 36GB internal root drives. It was LVM mirroring with 2 in each of 2 mirror sets.

One of the root drives failed and it turned out the LIF info wasn't on the mirror and I booted the recovery DVD and was able to get the machine up and running on the secondary mirror set. This was after I unplugged both the disk in the primary set.

So now the machine is up and running, without any issues. Except now I wanted to clean up the root VG of the 2 missing drives.

This is not a cluster.

I have run a few commands here to show output and hopefully paint a picture and perhaps someone knows how I can get these root disk back into the lvmtab. This system is currently up and running just fine. I don't have an ignite tape so that's not an option.

I did a #vgreduce -f /dev/vg00 which seemed to work except it didn't.

I rename my /etc/lvmtab and did a vgscan -v

#vgscan -v
vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg00 failed.

#vgdisplay -v vg00
vgdisplay: Volume group "/dev/vg00" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "vg00".

#ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 2 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c0t2d0 /dev/dsk/c0t2d0s2 /dev/rdsk/c0t2d0 /dev/rdsk/c0t2d0s2
/dev/dsk/c0t2d0s1 /dev/dsk/c0t2d0s3 /dev/rdsk/c0t2d0s1 /dev/rdsk/c0t2d0s3

#ll /dev/rdsk
total 0
crw-r--r-- 1 bin sys 188 0x000000 Apr 7 09:02 c0t0d0
crw-r--r-- 1 bin sys 188 0x002000 Apr 13 2008 c0t2d0
crw-r--r-- 1 bin sys 188 0x002001 Sep 14 2006 c0t2d0s1
crw-r--r-- 1 bin sys 188 0x002002 Nov 9 2007 c0t2d0s2
crw-r--r-- 1 bin sys 188 0x002003 Sep 14 2006 c0t2d0s3
crw-r--r-- 1 bin sys 188 0x013000 Sep 14 2006 c1t3d0
crw-r--r-- 1 bin sys 188 0x032000 Sep 14 2006 c3t2d0
crw-r--r-- 1 bin sys 188 0x032001 Sep 14 2006 c3t2d0s1
crw-r--r-- 1 bin sys 188 0x032002 Nov 9 2007 c3t2d0s2
crw-r--r-- 1 bin sys 188 0x032003 Sep 14 2006 c3t2d0s3


#dd if=/dev/rdsk/c0t2d0 of=/dev/null bs=64k count=1000
1000+0 records in
1000+0 records out

#dd if=/dev/rdsk/c0t2d0s1 of=/dev/null bs=64k count=1000
1000+0 records in
1000+0 records out



That which doesn't kill us makes us stronger.
13 REPLIES
Steven E. Protter
Exalted Contributor

Re: vg00 lv recovery

Shalom,

Great information. I can not find the question.

rx5670.

Good box. Does it have a P400 hardware raid card?

If so, I would use that to maintain the mirror,not mirror/ux

If it doesn't have a hardware raid card, I'd invest in one.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
scoooot
Frequent Advisor

Re: vg00 lv recovery

#vgscan -v
vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg00 failed.
That which doesn't kill us makes us stronger.
Torsten.
Acclaimed Contributor
Solution

Re: vg00 lv recovery

>> "rx5670.

Good box. Does it have a P400 hardware raid card?"


No, not possible. This good box does not have any PCIe slots.


@scoooot:

Do you want to replace the failed disk?

What does "vgdisplay -v vg00" says?

Consider to bring lvmtab back in place first.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
scoooot
Frequent Advisor

Re: vg00 lv recovery

#vgdisplay -v vg00
vgdisplay: Volume group "/dev/vg00" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "vg00".
That which doesn't kill us makes us stronger.
Torsten.
Acclaimed Contributor

Re: vg00 lv recovery

Do you want to replace the failed disk or continue unmirrored?

Bring lvmtab back in place first.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
scoooot
Frequent Advisor

Re: vg00 lv recovery

Sorry Torston, yes I do want to ultimatly replace the mirror set of 2 disks but thought it would be a good idea to get this back to a solid state on the current ones and then mirror them to new ones.

Or should I even bother and just go with replacing the failed mirror disk and going about it that way?
That which doesn't kill us makes us stronger.
Torsten.
Acclaimed Contributor

Re: vg00 lv recovery

I'm not exactly sure what the current situation is, but I would consider to replace the disk.

If your lvmtab is still valid - why trying a vgscan?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Jeff Schussele
Honored Contributor

Re: vg00 lv recovery

I think your lvmtab file is bazook.
Remove..it..rename..it...just rerun...FOR SURE.

Then let's see what happens...
MY $0.02,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
scoooot
Frequent Advisor

Re: vg00 lv recovery

lvmtab is toast. I did a rename. I did a rescan and you can see from the output above the vgscan -v.
That which doesn't kill us makes us stronger.
Torsten.
Acclaimed Contributor

Re: vg00 lv recovery

What's wrong with the old lvmtab?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
scoooot
Frequent Advisor

Re: vg00 lv recovery

I'm getting somewhere here now :-)

I plugs the new pair of drives in. I then ioscan, insf all that and the new drives are there.
I then move my lvmtab.bak to lvmtab and then vgdisplay and you can see the results here.

Question now is...how do I clean this up?

#vgdisplay -v vg00

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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 8
Open LV 8
Max PV 16
Cur PV 4
Act PV 2
Max PE per PV 4350
VGDA 4
PE Size (Mbytes) 8
Total PE 8568
Alloc PE 6260
Free PE 2308
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 256
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 24576
Current LE 3072
Allocated PE 6144
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 256
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 2048
Current LE 256
Allocated PE 512
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 6144
Current LE 768
Allocated PE 1536
Used PV 2

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 4000
Current LE 500
Allocated PE 1000
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 5120
Current LE 640
Allocated PE 1280
Used PV 1

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
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/stale
LV Size (Mbytes) 6144
Current LE 768
Allocated PE 1536
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c0t2d0s2
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 4228
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c0t0d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t2d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c3t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 4340
Free PE 2308
Autoswitch On
Proactive Polling On

That which doesn't kill us makes us stronger.
scoooot
Frequent Advisor

Re: vg00 lv recovery

Ok once I plugged in the new drives and restored lvmtab I was able to clean up, get the new disk efi partitioned and bootable and they are mirroring at this very moment.

Cheers
That which doesn't kill us makes us stronger.
scoooot
Frequent Advisor

Re: vg00 lv recovery

Thanks again for the help torsten
That which doesn't kill us makes us stronger.