HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Booting a vPar from a replicated EVA disk of an nP...
Operating System - HP-UX
1834628
Members
3051
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
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
12-07-2006 11:30 AM
12-07-2006 11:30 AM
Booting a vPar from a replicated EVA disk of an nPar
Hi everyone!
I have a HP 9000 Superdome nPar booting from a Vdisk (A) of an EVA 5000, replicated to another Vdisk (B) on a different EVA via Continous Access.
After simulating a system failure (bringing the nPar down) we are trying to boot a vPAR with the replicated Vdisk (B).
When the vPar was starting up, HP-UX couldn't mount/find /vg00/ so boot failed.
Then we tried booting the vPar in Logical Volume Maintenance mode (with /stand/vmunix -lm) and relocating the root disk, but the result was the following:
==============================================
Host is virtual System Console slave
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 31, minor is 0x170003; start = 0, size = 8388608
read_ss_nvm: Cannot validate NVM - -2
Starting the STREAMS daemons-phase 1
System Console is virtual
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 1048576 Kbytes, lockable: 661852 Kbytes, available: 770524 Kbytes
/sbin/ioinitrc:
fsck: /dev/vg00/lvol1: possible swap device (cannot determine)
fsck SUSPENDED BY USER.
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted
INIT: Overriding default level with level 's'
INIT: SINGLE USER MODE
INIT: Running /sbin/sh
#
==============================================
As you can see, /vg00/lvol2 and lvol3 are ok, but in the last lines of the log, HP-UX can't mount /vg00/lvol1 where /stand is. I'm stuck here!
- Is this approach/configuration possible?
- If I get this to work, will HP support this configuration (boot a vPar from a replicated disk from an nPar)?
- Do you suggest a different environment?
Thanks in advance for your help!
I have a HP 9000 Superdome nPar booting from a Vdisk (A) of an EVA 5000, replicated to another Vdisk (B) on a different EVA via Continous Access.
After simulating a system failure (bringing the nPar down) we are trying to boot a vPAR with the replicated Vdisk (B).
When the vPar was starting up, HP-UX couldn't mount/find /vg00/ so boot failed.
Then we tried booting the vPar in Logical Volume Maintenance mode (with /stand/vmunix -lm) and relocating the root disk, but the result was the following:
==============================================
Host is virtual System Console slave
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 31, minor is 0x170003; start = 0, size = 8388608
read_ss_nvm: Cannot validate NVM - -2
Starting the STREAMS daemons-phase 1
System Console is virtual
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 1048576 Kbytes, lockable: 661852 Kbytes, available: 770524 Kbytes
/sbin/ioinitrc:
fsck: /dev/vg00/lvol1: possible swap device (cannot determine)
fsck SUSPENDED BY USER.
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted
INIT: Overriding default level with level 's'
INIT: SINGLE USER MODE
INIT: Running /sbin/sh
#
==============================================
As you can see, /vg00/lvol2 and lvol3 are ok, but in the last lines of the log, HP-UX can't mount /vg00/lvol1 where /stand is. I'm stuck here!
- Is this approach/configuration possible?
- If I get this to work, will HP support this configuration (boot a vPar from a replicated disk from an nPar)?
- Do you suggest a different environment?
Thanks in advance for your help!
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