- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Failed to boot to old kernel
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
09-10-2007 01:56 AM
09-10-2007 01:56 AM
Failed to boot to old kernel
I was trying to boot HPUX server into into single user from old kernel but it failed. I would seek your help what these errors mean? and how can i boot it up
ISL> hpux -is /stand/vmunix.prev
Boot
: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix.prev
11886592 + 2342912 + 5998336 start 0x1fdd68
alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
Firmware Version 45.44
Duplex Console IO Dependent Code (IODC) revision 1
Stored message buffer up to panic:
in stm
to determine which I/O subsystem is logging excessive errors.
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
SCSI Ultra320 0/5/2/0 instance 6: IO Type : MPT Domain Validation IO has t
imed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 0
0 40 00
I/O hardware probe timed out at path 0/5/2/0.7
System Panic:
linkstamp: Sun Sep 9 23:51:07 WAST 2007
_release_version: @(#) $Revision: vmunix: vw: -proj selectors:
CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 '
CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: I/O system hang
PC-Offset Stack Trace (read across, top of stack is 1st):
0x00210658 0x0038d128 0x009c58cc
0x0003fa10 0x00265708 0x0016923c
0x0017b180 0x00178b04
End Of Stack
*** 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2007 02:04 AM
09-10-2007 02:04 AM
Re: Failed to boot to old kernel
Check this link out.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1148465
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2007 02:06 AM
09-10-2007 02:06 AM
Re: Failed to boot to old kernel
Are you trying to boot of a SAN?
For whatever reason the kernel is no good. Drivers for the SAN don't appear to be properly compliled into the kernel.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2007 02:08 AM
09-10-2007 02:08 AM
Re: Failed to boot to old kernel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2007 07:22 PM
09-10-2007 07:22 PM
Re: Failed to boot to old kernel
I turned off disc enclosure for this path. How do I boot up without checking this path?