lbolt errors

[bond007]

Hi All,

Could you explain more about lbolt errors that we face frequently in our system. I know i happens due to some error in SCSI bus/device. Is there any tool/web site that we can use to get more info about any particular lbolt error/code ?

Thanks in advance,

Bond

[T G Manikandan]

lbolt errors are due to improper SCSI termination mostly. OR

might be due to mismatch of SCSI.

Well to find out which device is erring out,you can check the below link to find out your system device

http://www1.itrc.hp.com/service/iv/node.do?source=search&node=prodITRC/WW_Start/N1|11|12|7|2|1|4|1

[Andrew Rutter · Accepted solution]

hi bond,

If your getting alot of lbolt errors it could be bad termination along the bus somewhere.

or if its a large system with many disks you may need to adjust the scsi timeout for the disks

The default timeout is 60 I seem to remember, but this sometimes needs to be inrreased to 120/180 depending upon size of system and disks

this can be changed with
#pvchange -t ??? /dev/dsk/cxtxdx

check this thread for more details

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

Andy

[Steven E. Protter]

Tool or website?

http://forums.itrc.hp.com

If it results from changing a hot swap drive, then it is not serious and can be ignored.

Otherwise its serious and in my experience it means a disk is going to fail. It needs to be dealt with by a thorough check of all hardware and a physical inspection of exposed devices and cabling.

SEP

[LoC_1]

Hi

If your getting lbolt errors as mentioned above it could be due to timeout being too low. lbolts are cause by a scsi not being available during the required timeout.Change the timeout first.

The thing to look for is the dev_t or the pdev. If that keeps changing than the lbolt errors are for different devices. It may be a cable or terminator , hba or controller if the devices are all on the same bus.
If its always on the same device and the timeout has been changed , I would look at replacing the hard drive as soon as possible, in the case of a disk.

[Yogeeraj_1]

hi Bond,

you can also use STM to further query our hardware and locate the problem.

hth.

kind regards
yogeeraj

[Chauhan Amit]

You can use the following information to determine which device
generates the lbolt/timeout errors:

1f 02 6 0 00
__ __ _ _ __
| | | | |
major# | target | flags
| |
bus# lun

information:

- major# (1f) is 31 in decimal, and major number 31 should be
sdisk on your system.

- bus# (02) is the card instance number to which the device is
attached.

- target (6) is the device's scsi id.

- lun (0) is the device's logical unit number.

Therefore, this device maps to /dev/dsk/c2t6d0.

-Amit

[Kent Ostby]

If you see something like: dev=0x1f060000, you can take the last six digits and do:

ll /dev/dsk | grep 060000 and it will show the disk that your system is having trouble talking to.

If the "device" field changes then its probably a bus issue with a bad card or termination.

[bond007]

Thanks a lot for the valuable inputs