Operating System - Tru64 Unix
1748126 Members
3143 Online
108758 Solutions
New Discussion юеВ

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

 
whiteSox
Frequent Advisor

Digital Unix 5.0 issues SCSI errors i am not sure what they are

cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 0 lun 0
ss_perform_timeout
Reached max abort count, scheduled bus reset
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0 target 2 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error
cam_logger: SCSI event packet
cam_logger: bus 0
psiop_hardintrptidec5)
Bus reset detected
cam_logger: SCSI event packet
cam_logger: bus 0 target 2 lun 0
ss_perform_timeout
timeout on disconnected request
Active CCB at time of error

Does any one know what those scsi errors are i am getting these errors on Digital 5.0 Hp true 64 system ...running on Alpha 2000..

thanks for your help ..
16 REPLIES 16
cnb
Honored Contributor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

Looks like one of the devices on SCSI bus 0 is causing device timeouts across the scsi chain. Could be controller, faulty device, loose cable or termination. Check the connections.

Take a look at the error log or post it here.

Do you have DecEvent installed if not uerf may help to get an idea of what is happening.

Have you changed any device configuration?

Post #scu show edt

hth

whiteSox
Frequent Advisor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

i am unable to login ...
Steven Schweda
Honored Contributor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

> i am unable to login ...

I am unable to guess why. Fingers broken?
Keyboard filled with super-glue?

Perhaps you could describe what you did, what
you did it with, and what happened when you
did it. Or else consult a psychic?
whiteSox
Frequent Advisor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

scu show edt

CAM Equipment Device Table (EDT) Information:

Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W
-------------- ----------- ------ --------- ---------------- -------- ---
0 0 0 Direct SCSI-2 DEC RZ29B (C) DEC 0016 W
0 1 0 Direct SCSI-2 DEC RZ29B (C) DEC 0016 N
0 2 0 Direct SCSI-2 DEC RZ1DF-CB (C) DEC 0371 W
0 5 0 Sequential SCSI-2 DEC TLZ09 (C)DEC 0167 N
0 6 0 CD-ROM SCSI-2 DEC RRD45 (C) DEC 0436 N
1 0 0 Direct SCSI-2 DEC RZ1DF-AB (C) DEC 0372 N
1 2 0 Direct SCSI-2 DEC RZ1DF-AB (C) DEC 0372 N
1 3 0 Direct SCSI-2 DEC RZ1DF-AB (C) DEC 0372 N
whiteSox
Frequent Advisor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

please take loook at the attachment
cnb
Honored Contributor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are


WhiteSox:

Well mixing *these* Wide and Narrow devices on the same bus is never a good idea.

Disks 0 and 2 are Wide 16-bit, whereas all the other devices are Narrow 8-bit.

Suggest you get the hardware straightened out first.

BTW: Having a tape drive on the same SCSI bus is as the system disk is generally never a good idea (if your system disk is also on Bus 0). But I know nothing.

Steven:

;-)

Always enjoy your posts!


hth

DCBrown
Frequent Advisor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

timeout on disconnected request

This means scsi command delivered to 0/0/0 ok, then host disconnects. When disk is ready then it will arbitrate for the bus to start the data transfer .... and this never happens. Host times out, falls down, goes boom. Rinse, repeat.

Also see the same thing on 0/2/0. A random guess is the host can arb for the bus, but the target device can't or fails for some reason. I'd start by disconnecting all devices except 0/0/0 (which is probably not enough to successfully boot, but...) and see how far it gets. Still a problem - check termination/cables. Since there are two drives complaining about the same thing it *could* be one of these drives that has broken and mucked up the bus... but less likely than one of the other devices. Any devices added/changed on the bus lately? Wrong scsi ids? too much termination? If just having 0/0/0 on the bus "works", then start adding back in devices until it breaks.
DCBrown
Frequent Advisor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

and yeah, mixing wide and narrow devices should force all communication on the bus to *ALL* devices to be narrow which really hurts wide disk performance.
DCBrown
Frequent Advisor

Re: Digital Unix 5.0 issues SCSI errors i am not sure what they are

re: tape on same bus.

Be aware that some tape io has upwards of a 90 minute timeout value and during looong tape transfers some tape drives won't give up the bus. It depends on tape drive, backup software, and transfer size as to whether it splashes over and hurts other devices trying to share the same bus.

I'm assuming there is no fair arbitration hub or anything like that.