topic Re: Syslog Error in Operating System - HP-UX

Syslog Error

santosh jha — Thu, 19 Feb 2004 23:21:46 GMT

Feb 20 09:17:41 krishna vmunix:
Feb 20 09:17:41 krishna vmunix: SCSI: Request Timeout; Abort -- lbolt: 1444308518, dev: e7056000, ie.

I Am unable to determine which device is this.
Please help.

Regards
Santosh Jha

Re: Syslog Error

Joseph Loo — Thu, 19 Feb 2004 23:32:38 GMT

hi,

maybe you like to show from the start of the error?

e.g. bp->b_dev: cb000000,
CB=203dec
then do a lsdev|grep 203
look for the class.
then ioscan -fnC |grep "class"

or refer to :

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

regards.

Re: Syslog Error

T G Manikandan — Thu, 19 Feb 2004 23:34:47 GMT

echo "0xe7=D"|adb
which is 231

#lsdev -b 231

Re: Syslog Error

James Murtagh — Thu, 19 Feb 2004 23:34:59 GMT

Hi Santosh,

I'm not familiar with the driver associated to e7 but this command should show you :

# lsdev | grep $(echo 0xe7=D | adb)

If you also attach the "ioscan -fn" output I should be able to determine the device.

Cheers,

James.

Re: Syslog Error

James Murtagh — Thu, 19 Feb 2004 23:42:33 GMT

Of course I could have checked.....

# grep 231 /usr/conf/master.d/core-hpux
schgr 29 231

So it looks like it could be your robotic tape loader.

- jm.

Re: Syslog Error

santosh jha — Fri, 20 Feb 2004 00:08:40 GMT

Thankyou verymuch icould find out the device.

It was autoch.

By the can you tell me what e7056000 number is called.

Re: Syslog Error

santosh jha — Fri, 20 Feb 2004 00:15:46 GMT

Yes it is my tapes robotic arm but this error messege is comming as backups are going on properly.

Regards
Santosh Jha

Re: Syslog Error

James Murtagh — Fri, 20 Feb 2004 00:24:03 GMT

The dev id is composed of two parts - the major and minor numbers. Here e7 is the major - converted to decimal is 231, the rest is the minor number. If you have located the directory for the robotic device file, an "ls -l" will show you how this corresponds to the device, 5th field is the major, 6th is the minor number.

The error indicates a timeout on the bus - its possible the backup was stressing it a bit much hence a request will have timed out. Well written software will handle the error and re-queue the request.

- jm.

Re: Syslog Error

T G Manikandan — Fri, 20 Feb 2004 00:25:21 GMT

The lbolt errors are propped up due to

1.Improper scsi cabling & termination
2.Latest scsi patches not installed.

Make sure you update your system with latest patch bundles.

by the way

e7056000

pick up the e70560
e7-->major number
05-->Bus instance number
6-->scsi target id
0--Lun id
The last two digits indicate some flags

Re: Syslog Error

santosh jha — Fri, 20 Feb 2004 00:41:17 GMT

Where do i get technical documentation for this.

Regards
Santosh Jha

Re: Syslog Error

James Murtagh — Fri, 20 Feb 2004 00:49:42 GMT

You could try the "I/O Addressing" chapter from this book :

http://us-support3.external.hp.com/iv/data/documents/DE_SW_UX_swrec_EN_01_E/Introduction.pdf

There is also loads of information on the net about it too - its fairly standard across all unix varients.

- jm.