topic Re: understand error in syslog file in Operating System - HP-UX

understand error in syslog file

Shirley Zhang — Thu, 27 Oct 2005 11:23:24 GMT

Hi,

I had SCSI error in the syslog :

SCSI: io_id: 178d4ae8
Oct 27 01:06:28 hpux188 vmunix: lbolt: 4219261
Oct 27 01:06:28 hpux188 vmunix: bp: 00000000497cf400
Oct 27 01:06:28 hpux188 vmunix: dev: bc172600 (1/0/2/1/0.1.4.0.0.2.6)
Oct 27 01:06:28 hpux188 vmunix: tag: fe (untagged)
Oct 27 01:06:28 hpux188 vmunix: cdb: 15 10 00 00 20 00
Oct 27 01:06:28 hpux188 vmunix: addr: 0000000050d95e00
Oct 27 01:06:28 hpux188 vmunix: retry_cnt: 1
Oct 27 01:06:28 hpux188 vmunix: data out: 00 00 00 08 00 7f cb b2 00 00 02 00 08 12 00 00
Oct 27 01:06:28 hpux188 vmunix: status: (400) None -- Incomplete
Oct 27 01:06:28 hpux188 vmunix: Retry count exceeded!

Can you explain what's wrong? Also can you tell me what lbolt means and the status of "incomplete" means.

Thanks,

Shirley

Re: understand error in syslog file

Geoff Wild — Thu, 27 Oct 2005 11:33:56 GMT

lbolt usually means a harware error on a SCSI attached drive (disk or tape) - can be cause by moving a SCSI cable as well.

You need to test the device at (1/0/2/1/0.1.4.0.0.2.6)

try diskinfo as well as a dd:

dd if=/dev/dsk/ of=/dev/null

Rgds...Geoff

Re: understand error in syslog file

Shirley Zhang — Thu, 27 Oct 2005 11:42:54 GMT

what does lbolt stand for? what does the number 4219261 followed lbolt mean? I'd like to know the meaning of all the words such as: lbolt/bp/tag/cdb/addr/status.

Thanks,

Shirley

Re: understand error in syslog file

Hanwant Verma_1 — Thu, 27 Oct 2005 11:46:35 GMT

The lbolt errors usually mean a SCSI bus error which could be caused by the tape drive.

Check your terminators and cable connections for snugness.

Looking at the message again you have ONE device reporting lbolt error
the dev bc172600

You can be confident that lbolt errors (parity errors, etc) are definitely
hardware,not software. Note that bad tapes and dirty heads will cause these errors
too.DDS3 is an older technology so replacement drives are cheap and if the drive
is used daily, about 2 years is all you can expect for reliable operation.

Hanwant

Re: understand error in syslog file

Jeff Schussele — Thu, 27 Oct 2005 11:49:53 GMT

Hi Shirley,

Well bc=188 & 188 is the character major number for a SCSI disk.
Now you can decode just what disk from 172600

where c=17 (hex) so c23 (decimal)
t=2 and
d=6

So it should be /dev/rdsk/c23t2d6 that reported the problem.
I'd advise you check that disk with a diskinfo command
diskinfo /dev/rdsk/c23t2d6
If it reports accurate info check it with a dd command or even the STM diags.

HTH,
Jeff

Re: understand error in syslog file

Geoff Wild — Thu, 27 Oct 2005 11:50:05 GMT

Check out this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1093012932131+28353475&threadId=219110

And this doc:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf

Rgds...Geoff

Re: understand error in syslog file

marie-noelle jeanson_1 — Thu, 27 Oct 2005 12:08:51 GMT

Shirley,

lbolt is just the number of ticks (or 10msec) that passed since system was booted. It is another type of timestamp used sometimes internally.

Marie.

Re: understand error in syslog file

Shirley Zhang — Thu, 27 Oct 2005 12:18:31 GMT

Thanks, all.

Can anybody tell me the entry: stataus: (400)None-Incomplete and Retry count exceeded mean?

Shirley

Re: understand error in syslog file

Jeff Schussele — Thu, 27 Oct 2005 12:41:27 GMT

It means that the disk had an I/O query that could not be filled even after the max amount of retries.

Rgds,
Jeff

Re: understand error in syslog file

Shirley Zhang — Thu, 27 Oct 2005 12:54:18 GMT

Thanks, Jeff,

You mention the max_retry, how many times is the default maximum? Cause sometimes I see retry_cnt is 1, sometimes it's 45, sometimes it's 72.

Shirley