HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Boot disk query - LIF
Operating System - HP-UX
1834636
Members
3468
Online
110069
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
Forums
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
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
05-31-2005 11:24 PM
05-31-2005 11:24 PM
Question 1:
On a server I find that the boot disk on the alternate bootpath has "LABEL" only (I see that with lifls -v /)
To correct the situation I was thinking of the following:
# mkboot -a "hpux -lq" /
# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /
(64 bit system. The boot disk on primary path has the diagnostics loaded.)
# lvlnboot -R
Please suggest me if my above mentioned steps would solve the problem. I would really appreciate if you would let me know if I am missing something or some other approach is desired.
===============================================
Question 2:
On another server lvlnboot -v output shows that there are 3 "Boot Disks" in /dev/vg00 (total 4 disks - 2 PVGs and mirrored.) On listing the disks with lifls I find that only 2 of the disks have the LIF area.
Why is lvlnboot listing a disk as "Boot Disk" when it does not show a LIF area (lifls on the disk returns: not a LIF volume)?
Would lvlnboot -R solve this ? Or, any thing more is required to fix the issue?
On a server I find that the boot disk on the alternate bootpath has "LABEL" only (I see that with lifls -v /
To correct the situation I was thinking of the following:
# mkboot -a "hpux -lq" /
# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /
(64 bit system. The boot disk on primary path has the diagnostics loaded.)
# lvlnboot -R
Please suggest me if my above mentioned steps would solve the problem. I would really appreciate if you would let me know if I am missing something or some other approach is desired.
===============================================
Question 2:
On another server lvlnboot -v output shows that there are 3 "Boot Disks" in /dev/vg00 (total 4 disks - 2 PVGs and mirrored.) On listing the disks with lifls I find that only 2 of the disks have the LIF area.
Why is lvlnboot listing a disk as "Boot Disk" when it does not show a LIF area (lifls on the disk returns: not a LIF volume)?
Would lvlnboot -R solve this ? Or, any thing more is required to fix the issue?
Think, think and think...before you jump
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2005 11:35 PM
05-31-2005 11:35 PM
Solution
First question:
An easy way to get them in sync is the following:
mkboot -b /dev/rdsk/ /dev/rdsk/
This will copy all the boot programs from the first disk to the second disk.
Second question:
My understanding is that you only need a "boot disk" for your primary and alternate boot disks. Any other disk in the volume group does not need this. It was probably created with pvcreate -B to reserve space for the boot programs.
An easy way to get them in sync is the following:
mkboot -b /dev/rdsk/
This will copy all the boot programs from the first disk to the second disk.
Second question:
My understanding is that you only need a "boot disk" for your primary and alternate boot disks. Any other disk in the volume group does not need this. It was probably created with pvcreate -B to reserve space for the boot programs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2005 12:41 AM
06-01-2005 12:41 AM
Re: Boot disk query - LIF
As you have created the disk with pvcreate I think you have forgett the -B switch.
# pvcreate -fB /dev/rdsk/cXdYtZ
So if it is just a mirror disk, then you should redo the procedure for the mirror.
Roland
# pvcreate -fB /dev/rdsk/cXdYtZ
So if it is just a mirror disk, then you should redo the procedure for the mirror.
Roland
Sometimes you lose and sometimes the others win
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2005 01:41 AM
06-01-2005 01:41 AM
Re: Boot disk query - LIF
You do need to check to see if it's set up to handle boot files otherwise you'll need to re-mirror it after doing the pvcreate -B.
If you didn't do the pvcreate -B then none of the above will help you out since there wont be space on the physical device that is set aside for boot files.
You may need to:
unmirror each lvol
vgreduce disk out of vg
pvcreate -B disk
add disk to vg
remirror lvols
Best regards,
Kent M. Ostby
If you didn't do the pvcreate -B then none of the above will help you out since there wont be space on the physical device that is set aside for boot files.
You may need to:
unmirror each lvol
vgreduce disk out of vg
pvcreate -B disk
add disk to vg
remirror lvols
Best regards,
Kent M. Ostby
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP