cancel
Showing results for 
Search instead for 
Did you mean: 

panic reboot

farahon
Occasional Visitor

panic reboot

Hello Experts,

Could you please have a look to below logs which we collected them from our dumps.Actually I would like to find the root cause of panic reboot.
Anybody experienced same situation? or any idea about this issue?

HP-UX bnmi1 B.11.11 U 9000/800 3721944873

The system had been up for 46.34 minutes (278028 ticks).
Load averages: 0.00 0.00 0.00.

System went down at: Tue Jul 21 19:27:04 2009

+--------------------------------------------+
| Message Buffer |
+--------------------------------------------+

sg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
msgcnt 4021 vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
SCSI Ultra320 0/1/1/0 instance 2: IO Type : SCSI IO has timed-out. Target ID: 1, LUN ID: 0. Rea
d Command - CDB: 28 00 01 4b 00 88 00 00 08 00
SCSI Ultra320 0/1/1/0 instance 2: An IO timeout condition was detected. Condition cleared, no interve
ntion required.
SCSI Ultra320 0/1/1/1 instance 3: Driver is being taken offline, reason code 3 Reason codes:
1 => Adapter initialization failed. 2 => Firmware download failed. 3 => Unrecoverable hardw
are/firmware error. 4 => SCSI ID change request failed.
SCSI Ultra320 0/1/1/0 instance 2: Driver is being taken offline, reason code 3 Reason codes:
1 => Adapter initialization failed. 2 => Firmware download failed. 3 => Unrecoverable hardw
are/firmware error. 4 => SCSI ID change request failed.
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

Thanks in advance for you help.

Br,
Farahon
4 REPLIES
Steven E. Protter
Exalted Contributor

Re: panic reboot

Shalom,

This is probably one of the following:

1) SCSI controller problem
2) SCSI cable problem
3) SCSI termination issue, missing bad terminator something like that.

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
farahon
Occasional Visitor

Re: panic reboot

Hi SEP,

server was up and running since 2 years ago and this is first time we experience this issue.
From syslog I can see /tmp got full and one of our script try and try to write something on /tmp, do you think it might be the reason?
Actually I found that in SUN server when we have 100% usage of /tmp it can cause server rebooting.
What is your idea?

Farahon
SoorajCleris
HPE Pro

Re: panic reboot

Hi Farahon,

As you can see in the log lvol4 is full, this may cause issues.

But here it is giving solid clues like your SCSI interface has some issues.

After reboot, is the system working fine ?
Could you find a ts99?

Regards,
Sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie
Venkatesh BL
Honored Contributor

Re: panic reboot

> From syslog I can see /tmp got full and one of our script try and try to write something on /tmp, do you think it might be the reason?

/tmp getting full may cause application issues, but, would not lead to system panic situation. Looks like some SCSI issue.