- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vpar crash after DRD patching
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
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
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
04-22-2013 12:10 AM
04-22-2013 12:10 AM
vpar crash after DRD patching
HI
I used DRD to patch a clone disk and rebooted the vpar (not the first time I have done this).
The vpar has now crashed and won't boot. I have tried to set the ALT path to all paths to boot to the alternate, but nothing.
Even tried to boot from tape, but not working.
It won't even boot to the original root disk.
Any ideas will be most welcome.
Regards
Tariq
- Tags:
- DRD
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2013 09:16 AM
04-22-2013 09:16 AM
Re: vpar crash after DRD patching
What kind of error messages are you getting?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2013 06:24 AM
04-23-2013 06:24 AM
Re: vpar crash after DRD patching
VPAR: sba_info - rc=0 base=0xffffff8020000000 shared=1 cnt=2
VPAR: sba_info - rc=0 base=0xffffff8120000000 shared=1 cnt=2
DoCalllist done
Stored message buffer up to system crash:
ether5: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 1/0/12/1/0
iether6: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 1/0/12/1/1
iether7: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 1/0/14/1/0
iether8: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 1/0/14/1/1
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
AF_INET socket/streams output daemon running, pid 47
LVM: Root VG activated
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0xc0002; start = 0, size = 16777216
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 1, minor is 0x4; start = 1837920, size = 8388608
vconsd: exited
vconsd: exited
VFS_MOUNTROOT error information:
0:(hfs) 22
1:(nfs) 223
9:(vxfs) 28
10:(nfs3) 223
11:(nfs4) 223
12:(autofs) 251
15:(cifs) 223
18:(dnlc_neg_fs) 251
Message buffer contents after system crash:
linkstamp: Fri Apr 19 12:55:01 BST 2013
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
panic: VFS_MOUNTROOT: RDWR: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
PC-Offset Stack Trace (read down, top of stack is 1st):
0x10974040 (panic+0x130)
0x10a1581c (vfs_mountroot+0x46c)
0x1052f190 (im_preinitrc+0x260)
0x10a0bb58 (DoCalllist+0xf0)
0x1052ecf0 (main+0x28)
0x109aef68 ($vstart+0x48)
0x10217838 (istackatbase+0xfc)
End Of Stack
i 0 pfn 0x3000 pages 0x5000
i 1 pfn 0x10000 pages 0x8000
i 2 pfn 0x880000 pages 0x4f8000
i 3 pfn 0xff8000 pages 0x7000
*** Not enough CPUS for a compressed dump ***
*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.
*** The dump will be a SELECTIVE dump with
compression OFF and concurrency OFF: 1942 of 20681 megabytes.
*** To change this dump type, press any key within 10 seconds.
*** Select one of the following dump types, by pressing the corresponding key:
C) Proceed with CURRENT dump configuration.
S) The dump will be a SELECTIVE dump with both compression and
concurrency OFF: 1942 of 20681 megabytes.
P) The dump will be a PARTIAL dump with both compression and
concurrency OFF: 8192 of 20681 megabytes.
(A FULL dump is not possible.)
N) There will be NO DUMP performed.
*** Enter your selection now.
*** Dump disabled. System rebooting.
I had to re-ingite in the end