- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Changed alt boot patch
Operating System - HP-UX
1755659
Members
3733
Online
108837
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
Go to solution
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
02-04-2005 10:20 AM
02-04-2005 10:20 AM
I have mirrored my root drive and have just tested it by interrupting the boot sequence and booting from the alternate path. This spawned some pretty nasty error messages.
I have discovered that the hardware address for the second drive was wrong. I have corrected it using setboot -a with the correct address.
I used docid LVMKBRC00005103 as a guide and notice that the setboot portion is in step 3. As I said above I completed the mirror process, then discovered my error. When I issue setboot now everything lists as expected.
Since I have corrected the address, do I have to redo all of the lvextends, (or do I need to start the entire process over) etc in the rest of the document, or is the order of that step not critical?
Thank you,
Robb
I have discovered that the hardware address for the second drive was wrong. I have corrected it using setboot -a with the correct address.
I used docid LVMKBRC00005103 as a guide and notice that the setboot portion is in step 3. As I said above I completed the mirror process, then discovered my error. When I issue setboot now everything lists as expected.
Since I have corrected the address, do I have to redo all of the lvextends, (or do I need to start the entire process over) etc in the rest of the document, or is the order of that step not critical?
Thank you,
Robb
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2005 10:59 AM
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