- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Moving root disk
Operating System - HP-UX
1754407
Members
3071
Online
108813
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО12-26-2008 03:35 PM
тАО12-26-2008 03:35 PM
Moving root disk
Hi,
We followed the procedure defined on "When Good Disks Go Bad: Dealing with Disk Failures Under LVM, Appendix F: Moving a Root Disk to a New Disk or Another Disk" on an Itanium rx6600 11.23. We slightly modified the commands used to fit Integrity Servers requirements (mkboot -e -l, etc.). But, once we got to point 6: shutdown and reboot... the machine would not boot any more. It was not even able to boot from a recovery shell (?).
We have made tests on a similar machine with the same results.
We have managed to complete the whole procedure if we do the lvlnboot's BEFORE shutting down.
So, we have two questions:
1. Anybody has done anything similar with good results? (Ignite, Mirror or DRD do not apply to our specific case)
2. Anybody has followed the procedure described in WGTGB for PA-RISC? (WBTGB has been great for us in many occasions, but we don't have a pa-risc machine handy).
In both cases, we would appreciate if anybody could shed us some light on why you have to lvlnboot before / after the reboot. We are really puzzled about it.
Thank you, folks.
We followed the procedure defined on "When Good Disks Go Bad: Dealing with Disk Failures Under LVM, Appendix F: Moving a Root Disk to a New Disk or Another Disk" on an Itanium rx6600 11.23. We slightly modified the commands used to fit Integrity Servers requirements (mkboot -e -l, etc.). But, once we got to point 6: shutdown and reboot... the machine would not boot any more. It was not even able to boot from a recovery shell (?).
We have made tests on a similar machine with the same results.
We have managed to complete the whole procedure if we do the lvlnboot's BEFORE shutting down.
So, we have two questions:
1. Anybody has done anything similar with good results? (Ignite, Mirror or DRD do not apply to our specific case)
2. Anybody has followed the procedure described in WGTGB for PA-RISC? (WBTGB has been great for us in many occasions, but we don't have a pa-risc machine handy).
In both cases, we would appreciate if anybody could shed us some light on why you have to lvlnboot before / after the reboot. We are really puzzled about it.
Thank you, folks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2008 01:23 AM
тАО12-28-2008 01:23 AM
Re: Moving root disk
hello
Please can u elaborate what modifications u did as the platform is INtegrity???
u have to pproperly create the EFI, HPUX and the HPSP partition on the newdisk.
Step3#vgextend /dev/vg00 /dev/dsk/c2t2d2s2
step4# pvmove /dev/dsk/c1t1d1s2 /dev/dsk/c2t2d2s2
step5#vgreduce /dev/vg00 /dev/dsk/c1t1d1s2
The steps that u havemodified do this conform to the above modifications in the steeps as i have given?
please do not forget to assign the points.
Sujit
as far as PV move is concerned i think u need to do that for the /dev/dsk/
Please can u elaborate what modifications u did as the platform is INtegrity???
u have to pproperly create the EFI, HPUX and the HPSP partition on the newdisk.
Step3#vgextend /dev/vg00 /dev/dsk/c2t2d2s2
step4# pvmove /dev/dsk/c1t1d1s2 /dev/dsk/c2t2d2s2
step5#vgreduce /dev/vg00 /dev/dsk/c1t1d1s2
The steps that u havemodified do this conform to the above modifications in the steeps as i have given?
please do not forget to assign the points.
Sujit
as far as PV move is concerned i think u need to do that for the /dev/dsk/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2008 11:43 AM
тАО12-28-2008 11:43 AM
Re: Moving root disk
As Sujit says you have to use idisk to partitioning the system disk.
# vi /tmp/idf
3
EFI 500MB
HPUX 100%
HPSP 400MB
# idisk -f /tmp/idf -w /dev/rdisk/disk2
# insf -eC disk
# pvcreate -B /dev/rdisk/disk2_p2
# vgextend vg00 /dev/disk/disk2_p2
# mkboot -e -l /dev/rdisk/disk2
# mkboot -a "hpux" /dev/rdisk/disk2
The logical volumes on the mirror boot disk must be extended in the same order that they are configured on the original boot disk. Determine the list of logical volumes in the root volume group and their order. For example:
# pvdisplay -v /dev/disk/disk0_p2 | grep 'current.*0000 $'
00000 current /dev/vg00/lvol1 00000
00010 current /dev/vg00/lvol2 00000
00138 current /dev/vg00/lvol3 00000
00151 current /dev/vg00/lvol4 00000
00158 current /dev/vg00/lvol5 00000
00159 current /dev/vg00/lvol6 00000
00271 current /dev/vg00/lvol7 00000
00408 current /dev/vg00/lvol8 00000
# for i in $(pvdisplay -v /dev/disk/disk0_p2 | grep 'current.*0000 $' | awk '{print $3}')
do
lvextend -s ├в m 1 $i /dev/disk/disk2_p2
done
# lvsync -T /dev/vg00/lvol*
This is to update the root volume group information:
# lvlnboot -R /dev/vg00
Use the setboot command to change the primary disk to the new disk now you could use the manual that U mentioned.
and you have to update the /stand/bootconf file to this if that is the disk you use:
# vi /stand/bootconf
l /dev/disk/disk2_p2
# vi /tmp/idf
3
EFI 500MB
HPUX 100%
HPSP 400MB
# idisk -f /tmp/idf -w /dev/rdisk/disk2
# insf -eC disk
# pvcreate -B /dev/rdisk/disk2_p2
# vgextend vg00 /dev/disk/disk2_p2
# mkboot -e -l /dev/rdisk/disk2
# mkboot -a "hpux" /dev/rdisk/disk2
The logical volumes on the mirror boot disk must be extended in the same order that they are configured on the original boot disk. Determine the list of logical volumes in the root volume group and their order. For example:
# pvdisplay -v /dev/disk/disk0_p2 | grep 'current.*0000 $'
00000 current /dev/vg00/lvol1 00000
00010 current /dev/vg00/lvol2 00000
00138 current /dev/vg00/lvol3 00000
00151 current /dev/vg00/lvol4 00000
00158 current /dev/vg00/lvol5 00000
00159 current /dev/vg00/lvol6 00000
00271 current /dev/vg00/lvol7 00000
00408 current /dev/vg00/lvol8 00000
# for i in $(pvdisplay -v /dev/disk/disk0_p2 | grep 'current.*0000 $' | awk '{print $3}')
do
lvextend -s ├в m 1 $i /dev/disk/disk2_p2
done
# lvsync -T /dev/vg00/lvol*
This is to update the root volume group information:
# lvlnboot -R /dev/vg00
Use the setboot command to change the primary disk to the new disk now you could use the manual that U mentioned.
and you have to update the /stand/bootconf file to this if that is the disk you use:
# vi /stand/bootconf
l /dev/disk/disk2_p2
jaton
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP