SCSI tape messages in syslog

[Spike Burkhardt]

All,

I had some problems with my tape drives and found entries in /var/adm/syslog/syslog.log at about the same time as the problems. Find below the specific errors. If you would be so kind as to comment on my questions after the message I would appreciate it.

1. Jan 17 20:13:26 picard vmunix: SCSI: Unexpected Disconnect -- lbolt: 806936176, dev: cd043000, io_id: 4763964
Q: what is a lbolt?

2. Jan 17 20:13:39 picard vmunix: scb->cdb: 17 00 00 00 00 00
Q: This was right after #1 and there were two of them. Any idea what it's trying to say?

3. Jan 17 20:13:39 picard vmunix: SCSI: Target detected parity error -- lbolt: 807002926, dev: cd043000
Q: Does this mean I had a tape parity error?

4. Jan 17 20:24:34 picard vmunix: scb->cdb: 12 00 00 00 80 00
This came right after #3.

5. Jan 17 20:24:35 picard vmunix: SCSI: Resetting SCSI -- lbolt: 807003027, bus: 4
Jan 17 20:24:35 picard vmunix: SCSI: Reset detected -- lbolt: 807003027, bus: 4
Q: Is this a result of the tape errors? I didn't see this 'lbolt' referenced anywhere else

6. Jan 17 20:24:40 tapsflt EMS [2099]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage
/events/tapes/SCSI_tape/0_3_0_0.4.0" (Threshold: >= " 3") Execute the following command to obtain event details:
/opt/resmon/bin/resdata -R 137560128 -r /storage/events/tapes/SCSI_tape/0_3_0_0.4.0 -n 137560077 -a
Q: There isn't a /storage directory. Is this a dynamic directory that gets deleted on reboot or is this a human configuration error?

Thanks for all your help!

spik

[Steven E. Protter]

lbolt
Means its dead, get it replaced.

Its not a configuration error.

Call hardware support.

Try and write a tape

tar /etc/issue

It might work, but you should still replace the drive.

P

[Spike Burkhardt]

Steve & Anil,

Thanks for your responses. Anil, that's great detail and probably more than I wanted but I'll save all for future!
Steve, also thanks. What is the definition of 'lbolt'. I understand that the drive needs to be replaced. On the last question about /storage, how come I don't have one when the message in syslog says to look there?

spike

[A. Clay Stephenson]

LBOLT indicates the number of clock ticks since the box was last booted.

[Eugeny Brychkov]

Spike,
to see details you should simply type at the hpux prompt:
'/opt/resmon/bin/resdata -R 137560128 -r /storage/events/tapes/SCSI_tape/0_3_0_0.4.0 -n 137560077 -a'.
Eugeny

[Spike Burkhardt]

Eugeny,

When I do this I get the messag:
There is no active monitor request for the resource /storage/events/tapes/SCSI_tape/0_3_0_0.4.0 associated with the request id 137560128.

Do the 'active monitor request' get deleted after a reboot?

[Eugeny Brychkov]

Should not. Check correctness of spelling.
Try running stm (mstm for terminals), go to Tools, Utilities, Run, log tool, File, select raw, format raw, view formatted log. You should see details in the output
Eugeny

[Spike Burkhardt]

Eugeny,

Thanks for the info. I didn't know about stm. It looks like a great tool. The interface reminded me of an old DEC utility called vaxsim.
Wonder if the developer moved to HP?

Spike

[avsrini]

Hi Spike,
The /storage is a Event Monitoring System's object. Your system is loaded with EMS to monitor all the hardware's in your servers. Whenever you get any errors from any hardware's it is posted by EMS to syslog.log file.

You can search for EMS white paper for more information.

This is a diagnostic utility helps you to predict hardware failure and informs you the details.

Srini.

[Steven E. Protter]

If you replace a hot swapable disk, you will get an lbolt until you reboot(confirming the click tick answer, though I didn't hink of it).

I suppose you could try booting your box and hope your problem goes away.

Every time I got an lbolt, except the time I switched out a hot swap disk, I ended up replacing hardware

If you are happy with the reponses please hand out points to those who helped.

P

[Angus Crome]

One last possibility;

There were known problems with the EMS and STM versions installed from the Dec 2001, Mar 2002 and Jun 2002 SupportPlus CD. There is a patch to fix the problem on the Sep and Dec 2002 Support CD in the Diagnostics depot. If you want to download it, this is the info from an 11.11 install, there is one for 11.00 also, but I don't have access to an 11.00 system right now.

PHSS_26947 1.0 EMS & HA Monitors (A.03.20.01)