topic lbolt error in Operating System - HP-UX

lbolt error

christobahl — Tue, 05 Aug 2003 16:12:27 GMT

Is there a way to decode the lbolt number that precedes the dev number. For instance, vmunix: SCSI: Request Timeout -- lbolt: 192380138, dev: 1f000000

I know how to decode the dev # but how can I decode the lbolt #.

Thanks
Chris

Re: lbolt error

Stuart Abramson_2 — Tue, 05 Aug 2003 16:21:54 GMT

1. Get the "dev:" entry from the lbolt:

# dmesg | grep lbolt | grep dev:

SCSI: Abort -- lbolt: 18346341, dev: e7015000, io_id: 122e9a3
SCSI: Request Timeout -- lbolt: 18351441, dev: e7015000
SCSI: Abort -- lbolt: 18351441, dev: e7015000, io_id: 122e9be
SCSI: Request Timeout -- lbolt: 18356641, dev: e7015000
SCSI: Abort -- lbolt: 18356641, dev: e7015000, io_id: 122e9cf
SCSI: Request Timeout -- lbolt: 18362141, dev: e7015000
SCSI: Abort -- lbolt: 18362141, dev: e7015000, io_id: 122e9e0
SCSI: Request Timeout -- lbolt: 74105435, dev: 1f000000
SCSI: Abort Tag -- lbolt: 74105435, dev: 1f000000, io_id: 4ead34

Here we have two:

1f
e7

2. This is the major number of the device in question. Convert the first
two digits of the device from hex to decimal:

# printf "%#d\n" 0x1f
31

3. find out what driver this major number is. It tells us the type of
device:

# lsdev 31

Character Block Driver Class
188 31 sdisk disk

So, this is probably a disk !

4. Find the device file entry from the remainder of the lbolt error:

SCSI: Abort Tag -- lbolt: 74105435, dev: 1f000000, io_id: 4ead34

This is the minor number for the device that is failing.

a. Block device:

# ll -R /dev/ | grep 31 | grep 0x000000

brw-r----- 1 bin sys 31 0x000000 Jul 15 16:25 c0t0d0

Or:

b. Character Device:

# ll -R /dev/ | grep 188 | grep 0x000000
crw-r----- 1 bin sys 188 0x000000 Oct 11 07:15 c0t0d0

5. Find the Hardware Address:

# lssf /dev/dsk/c0t0d0
sdisk card instance 0 SCSI target 0 SCSI LUN 0 section 0
at address 0/0/0.0.0 /dev/dsk/c0t0d0

6. Find the type of device:

# diskinfo /dev/rdsk/c0t0d0# diskinfo /dev/rdsk/c0t0d0
SCSI describe of /dev/rdsk/c0t0d0:
vendor: DGC
product id: C2300WDR1
type: direct access
size: 4102875 Kbytes
bytes per sector: 512

So, we have a Nike disk at hardware address 0/0/0.0.0, device file
/dev/dsk/c0t0d0

Re: lbolt error

Jeff Schussele — Tue, 05 Aug 2003 16:23:35 GMT

Hi Chris,

Not 100% sure, but I believe lbolt is simply clock ticks since the last boot.
See /usr/include/sys/strenv.h | grep lbolt

HTH,
Jeff

Re: lbolt error

A. Clay Stephenson — Tue, 05 Aug 2003 16:25:14 GMT

The 'lbolt' is simply the number of clock ticks since the last boot. The device part is done like this. The 1st 2 hex digits 1f (31 decimal) refer to the major device number. Do an lsdev and you will note that Block Major 31 is a SCSI disk. The remaining hex digits comprise the minor device number. The next two hex digits (00)refer to the instance number: c0. The next hex digit (0) is the SCSI target ID (t0). The hex digit (0) is the LUN d0. The remaining hex digits are device driver specific.

In your case 0x1f000000 refers to /dev/dsk/c0t0d0. Do an ls -l of /dev/dsk/c0d0t0 and you should see a very good correlation to the 'LBOLT' device.

Re: lbolt error

Stuart Abramson_2 — Tue, 05 Aug 2003 16:25:47 GMT

Chris:

I reread your message. You already know how to decode the "dev" field.

In regard to the lbolt: I never cared. If you have a problem, call a CE. Something is wrong. (I suppose if you have a tape, you could have a bad spot on the tape, or a head that needs to be cleaned, but mine were always disks, which usually require CE action.)

Re: lbolt error

Jeff Schussele — Tue, 05 Aug 2003 16:40:43 GMT

So let's take a guess:

(L)ast (B)oot (O)n(L)ine (T)icks

maybe....

Later,
Jeff

Re: lbolt error

Steven E. Protter — Tue, 05 Aug 2003 16:58:24 GMT

I have gotten lbolts from two causes:

1) I pulled a hot swap disk out of the box and replaced it. It went away after booting the box.
2) When a disk, tape or cd drive was getting ready to fail. Each and every time this happened, I ended up with a hardware call shortly thereafter.

SEP

Re: lbolt error

Phillip Renner — Tue, 05 Aug 2003 17:05:45 GMT

Just a fyi, when I see these lbolt messages the first thing I do is change the pvtimeout value on the disk in question to 180. They're usually set to the default which is 40ms and if the scsi bus gets real nbusy this will result in lbolt errors. The 180ms timeout value usually keeps these lbolts in the genie bottle.. To see the value do a pvdisplay /dev/dsk/cxtxdx and to change it do pvchange -t 180 cxtxdx.