- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- possible problem with mkboot
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
Forums
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
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
05-28-2002 06:12 AM
05-28-2002 06:12 AM
- lvreduced all lvols
- vgremoved the disk from the volume group
- mkboot -v /dev/dsk/c2t2d0
- mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/dsk/c2t2d0
- vgextend /dev/vg00 /dev/dsk/c2t2d0
I get no error back from any of the above. Yet, lnlnboot is not showing that the second disk is now a boot device:
- lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0)
Boot: lvol1 on: /dev/dsk/c1t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0
So, what did I miss?
It appears that the mkboot worked correctly:
- lifls -Cl /dev/dsk/c2t2d0|pg
volume ISL10 data size 7984 directory size 8 99/10/28 15:23:53
filename type start size implement created
===============================================================
ISL -12800 584 240 0 99/10/28 15:23:53
AUTO -12289 824 1 0 99/10/28 15:23:53
HPUX -12928 832 800 0 99/10/28 15:23:53
PAD -12290 1632 1700 0 99/10/28 15:23:54
LABEL BIN 3336 8 0 02/05/28 10:08:10
Any suggestions are appreciated!
mark
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:16 AM
05-28-2002 06:16 AM
Re: possible problem with mkboot
Regards,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:17 AM
05-28-2002 06:17 AM
Re: possible problem with mkboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:17 AM
05-28-2002 06:17 AM
Re: possible problem with mkboot
may you try a lvlnboot -R to update the BDRA.
Fr??d??ric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:19 AM
05-28-2002 06:19 AM
Re: possible problem with mkboot
# pvcreate -B
# mkboot -B
# lvextend -m 1 ???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:20 AM
05-28-2002 06:20 AM
Re: possible problem with mkboot
I had done an ignite tape on it, and then booted the system from an ignite tape from our other L2000 in order to test swaping drives in the SC10 array. Once I was sure I had the correct order of events for doing that, I rebooted it from the original ignite tape in order to restore the system to the original setup. I thought all I'd have to do is reset the mirrors. I guess not.
Thanks for the pointer, I'll let you know how it goes.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 06:40 AM
05-28-2002 06:40 AM
Re: possible problem with mkboot
Frederic: I did not try your suggestion, but it looks like that would work ok as well.
I will say that I am a bit disappointed at the amount of "disconnection" in the various HP-UX commands. I would have liked to have seen an error, or at least a warning, from mkboot or lifls that the device file was not created with a reserved boot area.
mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 12:36 PM
05-29-2002 12:36 PM
Re: possible problem with mkboot
pcvreate -B /dev/rdsk/c_t_d_
vgextend /dev/vg00 /dev/dsk/c_t_d_
lvlnboot -Rv
mkboot /dev/rdsk/c_t_d_
mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p LABEL /dev/rdsk/c_t_d_
lifls -l /dev/rdsk/c_t_d_
mkboot -a "hpux -lq (52.4.0;0)/stand/vmunix" /dev/rdsk/c_t_d_
lifcp /dev/dsk/c_t_d_
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c_t_d_
vi /stand/bootconf to make sure it contains all boot devices.
lvlnboot -Rv to update BDRA...MUST DO
setboot to make sure it knows primar and alternate boot paths.
Good luck