Operating System - HP-UX
1836442 Members
2478 Online
110100 Solutions
New Discussion

Failed to boot to old kernel

 
Lexxx
Advisor

Failed to boot to old kernel

Dears,

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.
4 REPLIES 4
Fabian Briseño
Esteemed Contributor

Re: Failed to boot to old kernel

hello lexx.

Check this link out.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1148465


Knowledge is power.
Steven E. Protter
Exalted Contributor

Re: Failed to boot to old kernel

Shalom,

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
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
tkc
Esteemed Contributor

Re: Failed to boot to old kernel

boot back up from the existing kernel and check out what device is on h/w path 0/5/2/0. it may be due to the old kernel do not have appropriate driver or patches for the i/o device in this h/w path. you can try removing the adapter on 0/5/2/0 or device connecting to this path if you wanna try booting from the previous kernel.
Lexxx
Advisor

Re: Failed to boot to old kernel

How do I restart without checking this 0/5/2/0?? i remember in the config these are vg01,02,03.
I turned off disc enclosure for this path. How do I boot up without checking this path?