dmesg shows the following

[Ross Zubritski]

Hi,

Are the DVD and DAT functioning properly?

Regards.

RZ

[Helen French]

The SCSI lbolt error message from a MC/SG environment normally comes because of patch issue. Update your system with latest patches!

[Michael Steele_2]

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY

Note first and last date time stamps.

Is last time stamp recent? Within the last hour? Last day?

Is difference from first in hours or days?

For 0/6/0/0 and other targets on 0/6/0/0 how many errors are recorded? (* Integer number in parenthesis next to 0/6/0/0 *)

If errors over, say, 200 then place HW call. If errors in tens then ignore.

[Rita C Workman · Accepted solution]

Remember - dmesg is just a 'roll-over' file of information.
What you are seeing could be from days or even weeks ago.

Ensure your syslog daemon is running properly and recording problems to your log...if there are no problems in your syslog and the system is running fine...then that dmesg is probably just left over info from times gone by.

Rgrds,
Rita

[Steven E. Protter]

I suspect that you have hardware problems and need to deal with them.

lbolts have always led, sooner or later to hardware replacement on my systems.

Usually sooner.

A good way to guage the severity of the problem is to run mstm or xstm(in x windows) and get information on all scsi devices and excercize them as well. This will help you spot problems, but can impact system performance.

SEP

[Colin Topliss]

Looks like a disk playing up. You can find out which one by looking at the device id:

dev = 1f05e000

1f = 31 (raw device)

05e0 translates to the device number:

c<0x05>td<0> = c5t14d0

Check that disk out, and replace if necessary.

[Gene Kornacki_3]

I think Rita was right about this being old information. After using xstm to check the scsi devices I found no errors.

I think this info was related to a cluster issue some time ago. At that time I could issue a cmviewcl -v on one box and get an A-OK back and from the other (the one this dmesg came off) never came back. At that time stopping and restarting inetd didn't help, trying to stop and restart the cluster SW would'nt work. Had to reboot (even though I hated to without knowing the cause). I'm guessing t this dmesg info showed up while the files systems were 'forced' unmounted.

I rarly use dmesg.

Thank all.

Gene