SCSI: Reset detected -- lbolt

[Mary Ann Lipa]

Hi,
I have hundreds if not thousands of lines like these on my syslog.log and dmesg:
vmunix: SCSI: Reset detected -- lbolt: 485638206, bus: 0

they appear line after line almost every second... and no other details aside from that...
how do i know where my problem lies?

please help......
Thank you very much!!
ann

[Rajeev Shukla]

Hi Have a look at the /var/adm/syslog/syslog.log file that should contain more information about the hardware address etc..

[T G Manikandan]

The SCSI lbolt errors occur because of

1.A device not responding to SCSI requests or bad
2.SCSI connections not OK,check SCSI termination
3.Also you can try increasing the timeout on the device.

Just add your syslog.log file.we can find out the device creating problems

[Mary Ann Lipa]

thanks for the reply guys!!! appreciated it!
i doubt that its a disk....
usually a disk has something like dev=1f... etc..
but my syslog.log only shows one liners that contain the lbolt/scsi reset message...
on an N4000, it could either be the core io or the system board...
any ideas if a scsi patch can fix it?


thanks!
ann

[Mary Ann Lipa]

Here's the last entries on the logs...

Jan 7 08:45:30 scpauc1b vmunix: SCSI: Reset detected -- lbolt: 469037973, bus: 0
Jan 7 08:45:30 scpauc1b vmunix: SCSI: Reset detected -- lbolt: 469038024, bus: 0
Jan 7 08:45:31 scpauc1b vmunix: SCSI: Reset detected -- lbolt: 469038083, bus: 0
Jan 7 08:45:31 scpauc1b vmunix: SCSI: Reset detected -- lbolt: 469038134, bus: 0

no other details.. thats all there is...=(
help....
my ioscan also is hanging...
Thanks!!!

[T G Manikandan]

dev=1f..

will determine that disk.

attach your syslog all entries reg. scsi lbolt errors.only then we can diagonise

[T G Manikandan]

For example if you have dev=1f020000

1f converting to decimal is 31

#lsdev -b 31
will give you the device that should be disk

Ex.Just do a

#ll /dev/dsk|grep 020000

That should give you the disk


Then do a

#diskinfo

revert

[Vincent Farrugia]

Hello,

If your ioscan is hanging then one of your devices in one of your SCSI chains is faulty.

Try to type:

ioscan -fnkC ext_bus

The one that gives you instance 0 (underneath I) is the hardware path of the SCSI controller reporting the errors. When you know this, you should try to see what devices are attached to this SCSI controller.

ioscan -fnkC ext_bus shouldn't hang since you are only requesting a kernel scan, not a hardware scan of the actual machine.

HTH,
Vince

[G. Vrijhoeven]

Hi Ann,

Did you install OnlineDiag. You can have a look at your scsi chain and disk using stm.

Gideon

[John Carr_2]

Hi ann

If you use ODE then use xstm its more visually friendly than cstm or mstsm.

John.