Sorry if this is the wrong place to ask... didn't know where to turn...
Having a problem with a scsi drive/cabling... (will summarize responses)
Here's the setup that worked...
CPU--->23gbUW--->23gbUW---(68pin to 50pin cable)-->9gb fast scsi2--->TERM
ID=2 ID=3 ID=1
We added another 23gbUW disk in line with the others... and quickly got a
lot of timeout errors from that new disk (ID=4).
CPU-->23gbUW-->23gbUW-->23gbUW--(68p-50p cbl)-->9gb fast scsi2--->TERM
ID=2 ID=3 ID=4 ID=1
The errors we got were:
Apr 2 17:37:35 hepsu03 vmunix: cam_logger: CAM_ERROR packet
Apr 2 17:41:06 hepsu03 vmunix: cam_logger: bus 0 target 0 lun 0
(actually, repeated for target 0,1,2,3,4)
Apr 2 17:41:06 hepsu03 vmunix: ss_perform_timeout
Apr 2 17:41:06 hepsu03 vmunix: timeout on disconnected request
And on other machines trying to access it with automouting:
NFS3 RFS3_WRITE failed for server hepsu03: RPC: Timed out
NFS3 write error 60 on host hepsu03
NFS3 RFS3_READ failed for server hepsu03: RPC: Timed out
Now... each one of these cables are about 1 meter. Ultra should handle
15m.... Is the cable length combined with the narrow scsi causing the
problem? Why would it affect the last Ultra drive (ID=4)... I'd think it
would affect the narrow scsi.
Any ideas why? What if you have 10m of cabling for ultra wide, then stick
a narrow scsi-2 on the end that only has a length of 3m?
If you have a narrow scsi-2 on a chain full of ultra-wide, do you have to
limit the length to 3m?!
FYI for others... you CAN mix wide with narrow, provided you get an
adapter/cable that terminates the upper 8 bits, but I have no idea about
this cable length limitations.
A good cabling site is
http://www.adaptec.com/support/configuration/connect.html
Thanks!
- Dan Kirkpatrick - dkirk_at_physics.syr.edu -
| Systems Administrator |
| Physics Department |
| Syracuse University, Syracuse, NY |
-------------------------------------------
Received on Sat Apr 04 1998 - 00:07:29 NZST