- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- System crashed (rp3410)
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
05-12-2006 09:18 PM
05-12-2006 09:18 PM
System crashed (rp3410)
I have a rp3410. I got the following error and system crash has occurred.The Server is connected to a MSA30-MI.
Please advice what is the problem.
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted.
ISL Revision A.00.43 Apr 12, 2000
ISL booting hpux
Boot
: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix
11104256 + 1835008 + 1469032 start 0x1fdd68
alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
Firmware Version 45.11
Duplex Console IO Dependent Code (IODC) revision 1
Stored message buffer up to panic:
IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 0, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
SCSI Ultra320 0/3/1/0 instance 4: IO Type : MPT Domain Validation IO has timed-out. Target ID: 1, LUN ID: 0. Inquiry Command - CDB: 12 00 00 00 40 00
I/O hardware probe timed out at path 0/3/1/0.7
System Panic:
linkstamp: Fri May 12 23:26:04 MDT 2006
_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 0x003a3308 0x0094247c
0x0003fb18 0x00265710 0x0016b0f4
0x0017d2d8 0x0017a9a4
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.
ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2006 09:23 PM
05-12-2006 09:23 PM
Re: System crashed (rp3410)
Awadhesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2006 09:33 PM
05-12-2006 09:33 PM
Re: System crashed (rp3410)
It seems the problem related to instance 4 of this controller.However instance 4 should be a HDD in MSA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2006 09:34 PM
05-12-2006 09:34 PM
Re: System crashed (rp3410)
Also check cables, connections for that device.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2006 09:47 PM
05-12-2006 09:47 PM
Re: System crashed (rp3410)
Awadhesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2006 09:49 PM
05-12-2006 09:49 PM
Re: System crashed (rp3410)
there are 7 HDDs in MSA30, from bay0 to bay6.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2006 11:41 PM
05-12-2006 11:41 PM
Re: System crashed (rp3410)
The system can boot of internal disk because this is readed: (11104256 + 1835008 + 1469032 start 0x1fdd68 ) but crash until start BCH menu.
I think that the problem is in the controler of external disk or the conecction with the server
best regards