- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- rp5430 vgreduce error/ failed mirror boot disk rep...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2012 06:54 AM
07-12-2012 06:54 AM
rp5430 vgreduce error/ failed mirror boot disk replacement
I am having a problem replacing a failed disk on an rp5430 HP-UX 11.11 system. I have gone through the "When good disks go bad" documentation and other guides on finding the failed disk and removing it from the volume group. I thought that the disk was completely gone and put in a replacement disk but it looks like there may be some remnants of the old disk somewhere. I was able to lvreduce all of the mirrors to the failed disk. The failed disk was at location /dev/dsk/c1t2d0 and the replacement disk showed up in the same location after reboot.
A couple issues I see are as follows:
Ghost Logical Volume:
Vgreduce –f vg00 results in
Not all extents are free. i.e. Out of 4340 PEs, only 3340 are free.
You must free all PEs using lvreduce/lvremove before the PV can be removed.
Example: lvreduce -A n -m 0 /dev/vg01/lvol1.
lvremove -A n /dev/vg01/lvol1
Here's the map of used PEs
--- Logical extents ---
LE LV PE Status 1
0000 lvol9 1591 ???
0001 lvol9 1592 ???
0002 lvol9 1593 ???
0003 lvol9 1594 ???
0004 lvol9 1595 ???
...
I can find no such reference to lvol9 anywhere in the system.
Vgdisplay –v 00 (shows 2 active PV but it looks like there is only one attached to the volume group. Is this because I have not been able to sucessfully reduce the VG?)
root@rupert # vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 2
Act PV 1
Max PE per PV 4350
VGDA 2
PE Size (Mbytes) 8
Total PE 4340
Alloc PE 3655
Free PE 685
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 304
Current LE 38
Allocated PE 38
Used PV 1
LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 512
Allocated PE 512
Used PV 1
LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 400
Current LE 50
Allocated PE 50
Used PV 1
LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 200
Current LE 25
Allocated PE 25
Used PV 1
LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 250
Allocated PE 250
Used PV 1
LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 1000
Allocated PE 1000
Used PV 1
LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 1640
Current LE 205
Allocated PE 205
Used PV 1
LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 4600
Current LE 575
Allocated PE 575
Used PV 1
LV Name /dev/vg00/lvdmp
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 1000
Allocated PE 1000
Used PV 0
LV Name /dev/vg00/lvnodmp
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 1000
Allocated PE 1000
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c2t2d0
PV Status available
Total PE 4340
Free PE 685
Autoswitch On
--- Physical volume groups ---
PVG Name pvg0
PV Name /dev/dsk/c2t2d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2012 07:38 AM
07-13-2012 07:38 AM
Re: rp5430 vgreduce error/ failed mirror boot disk replacement
In reference to my previous post about ghost logical volume (lvol9), it looks like the LE and PEs correspond to the logical volume lvnodmp.
Here is an example:
root@rupert # vgreduce -f vg00
Not all extents are free. i.e. Out of 4340 PEs, only 3340 are free.
You must free all PEs using lvreduce/lvremove before the PV can be removed.
Example: lvreduce -A n -m 0 /dev/vg01/lvol1.
lvremove -A n /dev/vg01/lvol1
Here's the map of used PEs
--- Logical extents ---
LE LV PE Status 1
0000 lvol9 1591 ???
0001 lvol9 1592 ???
0002 lvol9 1593 ???
0003 lvol9 1594 ???
0004 lvol9 1595 ???
0005 lvol9 1596 ???
0006 lvol9 1597 ???
0007 lvol9 1598 ???
0008 lvol9 1599 ???
0009 lvol9 1600 ???
...
root@rupert # lvdisplay -v -k /dev/vg00/lvnodmp
--- Logical volumes ---
LV Name /dev/vg00/lvnodmp
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 8000
Current LE 1000
Allocated PE 1000
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default
--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c2t2d0 1000 1000
--- Logical extents ---
LE PV1 PE1 Status 1
00000 1 01591 current
00001 1 01592 current
00002 1 01593 current
00003 1 01594 current
00004 1 01595 current
00005 1 01596 current
00006 1 01597 current
00007 1 01598 current
00008 1 01599 current
00009 1 01600 current
...
It also looks like I have two dump locations but only lvnodmp is active.
root@rupert # vgdisplay -v vg00
...
LV Name /dev/vg00/lvdmp
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 1000
Allocated PE 1000
Used PV 0
LV Name /dev/vg00/lvnodmp
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 1000
Allocated PE 1000
Used PV 1
root@rupert # lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c2t2d0
Swap: lvol2 on: /dev/dsk/c2t2d0
Dump: lvdmp on: /dev/dsk/c2t2d0, 0
Dump: lvnodmp on: /dev/dsk/c2t2d0, 1
How hard is it to move the dump location to lvdmp and remove the lvnodmp logical volume?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2012 09:21 AM
07-13-2012 09:21 AM
Re: rp5430 vgreduce error/ failed mirror boot disk replacement
Follow the below steps:--
vgreduce -f vg00
lvreduce -A n -m 1 /dev/vg01/lvol1
lvremove -A n /dev/vg01/lvol1
Ajin.S
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2012 01:43 PM
07-13-2012 01:43 PM
Re: rp5430 vgreduce error/ failed mirror boot disk replacement
Thanks for he reply, but unfortunately i have already tried all of these commands previously and they do not correct the issue.
vgreduce -f vg00 < Does not work and errors out. See my previous two posts
lvreduce -A n -m 1 /dev/vg01/lvol1 < Does not work because the volume lvol9 does not exist anywhere
lvremove -A n /dev/vg01/lvol1 < Does not work because the volume lvol9 does not exist anywhere
I am still in need of assistance if anyone can help.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2012 05:51 AM
07-15-2012 05:51 AM
Re: rp5430 vgreduce error/ failed mirror boot disk replacement
The failed disk was at location /dev/dsk/c1t2d0 and the replacement disk showed up in the same location after reboot.------------------------------------->>>>>>>>>Remove the disk Physically from srver .run vgscan -v to recreate the lvm tab .Then connect the disk and pvcreate.
Ajin.S
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
- Tags:
- vgscan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2012 10:26 AM
07-29-2012 10:26 AM
Re: rp5430 vgreduce error/ failed mirror boot disk replacement
I shutdown the server, removed the disk, powered server back on and tried vgscan but it gives the error "
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."
Does anyone have any more ideas?