- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Phys. Vol in Root Vol Group isn't "Boot Disk"?
Operating System - HP-UX
1753354
Members
5130
Online
108792
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
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
тАО07-07-2005 08:51 AM
тАО07-07-2005 08:51 AM
I've been working my way thru several existing servers. Ran lvlnboot -v on one of them and got the results shown:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (10/0.5.0)
/dev/dsk/c0t4d0 (10/0.4.0) -- Boot Disk
/dev/dsk/c0t3d0 (10/0.3.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c0t4d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c0t4d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c0t4d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
Note tha c0t5d0 is not marked "Boot Disk". I looked a little further and found it contains parts of /opt and /home, is mirrored, and syncd.
So, is this a problem, and if so, how do I fix it (never seen this case before)
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (10/0.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (10/0.5.0)
/dev/dsk/c0t4d0 (10/0.4.0) -- Boot Disk
/dev/dsk/c0t3d0 (10/0.3.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c0t4d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c0t4d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c0t4d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
Note tha c0t5d0 is not marked "Boot Disk". I looked a little further and found it contains parts of /opt and /home, is mirrored, and syncd.
So, is this a problem, and if so, how do I fix it (never seen this case before)
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2005 09:09 AM
тАО07-07-2005 09:09 AM
Solution
Well the first thing I note is that although 3 disks are marked as boot disks (meaning pvvreate -B and mkboot was run on them) only 1 is actually a valid boot disk. If this were me, I would run vgdisplay -v and lvdisplay to see what actual extents are mirrored.
The important thing to note is that the only required LVOL's on the boot disk itself are /stand, /, and primary swap. The other LVOL's (like /usr, /opt, and /home) can be on another physical disk in the vg. This was a quite common setup when using smaller (2GB and 4GB disks). After getting these two disks setup as you want, you would then mirror onto 2 more disks and setup the alternate boot paths.
It appears that your system wasn't quite done correctly becaause we ought to see 2 boot disks each with Boot, Root, and Swap configured. I would carefully examine lvdisplay -v's and vgdisplay -v's and then lvreduce to remove the mirrors and vgreduce to get rid of the extra PV's and then start the boot mirror creation process in the right order.
The important thing to note is that the only required LVOL's on the boot disk itself are /stand, /, and primary swap. The other LVOL's (like /usr, /opt, and /home) can be on another physical disk in the vg. This was a quite common setup when using smaller (2GB and 4GB disks). After getting these two disks setup as you want, you would then mirror onto 2 more disks and setup the alternate boot paths.
It appears that your system wasn't quite done correctly becaause we ought to see 2 boot disks each with Boot, Root, and Swap configured. I would carefully examine lvdisplay -v's and vgdisplay -v's and then lvreduce to remove the mirrors and vgreduce to get rid of the extra PV's and then start the boot mirror creation process in the right order.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2005 09:11 AM
тАО07-07-2005 09:11 AM
Re: Phys. Vol in Root Vol Group isn't "Boot Disk"?
most probably this disk got replaced since the OS was installed and nobody bothered to run an mkboot on this device.
In my opinion, with 3 boot devices out of 4, you are in pretty good shape but it would not hurt to run :
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c0t5d0
mkboot -l /dev/rdsk/c0t5d0
mkboot -b updatediaglif2 -p ISL -p AUTO -p HPUX -p LABEL /dev/rdsk/c0t5d0
(if your OS is 32 bit version, please replace "updatediaglif2" with "updatediaglif")
In my opinion, with 3 boot devices out of 4, you are in pretty good shape but it would not hurt to run :
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c0t5d0
mkboot -l /dev/rdsk/c0t5d0
mkboot -b updatediaglif2 -p ISL -p AUTO -p HPUX -p LABEL /dev/rdsk/c0t5d0
(if your OS is 32 bit version, please replace "updatediaglif2" with "updatediaglif")
________________________________
UNIX because I majored in cryptology...
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2005 09:18 AM
тАО07-07-2005 09:18 AM
Re: Phys. Vol in Root Vol Group isn't "Boot Disk"?
Hmmm....
I was afraid of that. I guess I know what I'll be doing tomorrow
Thanks all
scott m
I was afraid of that. I guess I know what I'll be doing tomorrow
Thanks all
scott m
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