- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Replacing a Primary Boot Drive in a RP7410
Operating System - HP-UX
1753819
Members
8783
Online
108805
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
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
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
08-05-2010 02:13 PM
08-05-2010 02:13 PM
Replacing a Primary Boot Drive in a RP7410
Could someone tell me if the below procedure is what is needed to replace a Mirror'ed Primary Boot Drive in a rp7410.
.......
Save the hardware paths to the disk.
# ioscan –m lun /dev/disk/disk14
0/1/1/1.0x3.0x0
/dev/disk/disk14 /dev/rdisk/disk14
/dev/disk/disk14_p1 /dev/rdisk/disk14_p1
/dev/disk/disk14_p2 /dev/rdisk/disk14_p2
/dev/disk/disk14_p3 /dev/rdisk/disk14_p3
**LUN instance number is 14, the LUN hardware path is 64000/0xfa00/0x0, and the lunpath hardware path is 0/1/1/1.0x3.0x0.
# pvchange -a N /dev/disk/disk14_p2 (non-hp9000)
# pvchange -a N /dev/disk/disk14 (hp9000)
Replace the drive
If the system was not rebooted:
# scsimgr replace_wwid –D /dev/rdisk/disk14
This command allows the storage subsystem to replace the old disk’s LUN World-Wide-Identifier (WWID) with the new disk’s LUN WWID. The storage subsystem creates a new LUN instance and new device special files for the replacement disk.
Determine the new LUN instance number for the replacement disk.
For example:
# ioscan –m lun
Class I Lun H/W Path Driver S/W State H/W Type Health Description
========================================================================
disk 14 64000/0xfa00/0x0 esdisk NO_HW DEVICE offline HP MSA Vol
/dev/disk/disk14 /dev/rdisk/disk14
/dev/disk/disk14_p1 /dev/rdisk/disk14_p1
/dev/disk/disk14_p2 /dev/rdisk/disk14_p2
/dev/disk/disk14_p3 /dev/rdisk/disk14_p3
...
disk 28 64000/0xfa00/0x1c esdisk CLAIMED DEVICE online HP MSA Vol
0/1/1/1.0x3.0x0
/dev/disk/disk28 /dev/rdisk/disk28
In this example, LUN instance 28 was created for the new disk, with LUN hardware path 64000/0xfa00/0x1c, device special files /dev/disk/disk28 and /dev/rdisk/disk28, at the same lunpath hardware path as the old disk, 0/1/1/1.0x3.0x0. The old LUN instance 14 for the old disk now has no lunpath associated with it.
Assign the old instance number to the replacement disk.
# io_redirect_dsf -d /dev/disk/disk14 -n /dev/disk/disk28
Restore LVM configuration information to the new disk.
# vgcfgrestore -n /dev/vg00 /dev/rdisk/disk14_p2 (non-hp9000)
# vgcfgrestore -n /dev/vg00 /dev/rdisk/disk14 (hp9000)
Restore LVM access to the disk.
# pvchange –a y /dev/disk/disk14_p2 (non-hp9000)
# pvchange –a y /dev/disk/disk14 (hp9000)
Place boot utilities in the boot area as follows:
# mkboot /dev/rdisk/disk4
Add an autoboot file to the disk boot area as follows:
# mkboot -a "hpux" /dev/rdisk/disk4
.......
Save the hardware paths to the disk.
# ioscan –m lun /dev/disk/disk14
0/1/1/1.0x3.0x0
/dev/disk/disk14 /dev/rdisk/disk14
/dev/disk/disk14_p1 /dev/rdisk/disk14_p1
/dev/disk/disk14_p2 /dev/rdisk/disk14_p2
/dev/disk/disk14_p3 /dev/rdisk/disk14_p3
**LUN instance number is 14, the LUN hardware path is 64000/0xfa00/0x0, and the lunpath hardware path is 0/1/1/1.0x3.0x0.
# pvchange -a N /dev/disk/disk14_p2 (non-hp9000)
# pvchange -a N /dev/disk/disk14 (hp9000)
Replace the drive
If the system was not rebooted:
# scsimgr replace_wwid –D /dev/rdisk/disk14
This command allows the storage subsystem to replace the old disk’s LUN World-Wide-Identifier (WWID) with the new disk’s LUN WWID. The storage subsystem creates a new LUN instance and new device special files for the replacement disk.
Determine the new LUN instance number for the replacement disk.
For example:
# ioscan –m lun
Class I Lun H/W Path Driver S/W State H/W Type Health Description
========================================================================
disk 14 64000/0xfa00/0x0 esdisk NO_HW DEVICE offline HP MSA Vol
/dev/disk/disk14 /dev/rdisk/disk14
/dev/disk/disk14_p1 /dev/rdisk/disk14_p1
/dev/disk/disk14_p2 /dev/rdisk/disk14_p2
/dev/disk/disk14_p3 /dev/rdisk/disk14_p3
...
disk 28 64000/0xfa00/0x1c esdisk CLAIMED DEVICE online HP MSA Vol
0/1/1/1.0x3.0x0
/dev/disk/disk28 /dev/rdisk/disk28
In this example, LUN instance 28 was created for the new disk, with LUN hardware path 64000/0xfa00/0x1c, device special files /dev/disk/disk28 and /dev/rdisk/disk28, at the same lunpath hardware path as the old disk, 0/1/1/1.0x3.0x0. The old LUN instance 14 for the old disk now has no lunpath associated with it.
Assign the old instance number to the replacement disk.
# io_redirect_dsf -d /dev/disk/disk14 -n /dev/disk/disk28
Restore LVM configuration information to the new disk.
# vgcfgrestore -n /dev/vg00 /dev/rdisk/disk14_p2 (non-hp9000)
# vgcfgrestore -n /dev/vg00 /dev/rdisk/disk14 (hp9000)
Restore LVM access to the disk.
# pvchange –a y /dev/disk/disk14_p2 (non-hp9000)
# pvchange –a y /dev/disk/disk14 (hp9000)
Place boot utilities in the boot area as follows:
# mkboot /dev/rdisk/disk4
Add an autoboot file to the disk boot area as follows:
# mkboot -a "hpux" /dev/rdisk/disk4
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2010 03:11 PM
08-05-2010 03:11 PM
Re: Replacing a Primary Boot Drive in a RP7410
Hi:
See:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911837/c01911837.pdf
Regards!
...JRF...
See:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911837/c01911837.pdf
Regards!
...JRF...
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