Re: Problem with U320 drive, high byte termination required?



Dave Scaramanga wrote:
Michael Baeuerle wrote:
Dave Scaramanga wrote:

[...]
This sounds very much like a "high-byte termination" problem.

Firstly, thank you for taking the time to help, I really appreciate this.
The devices that I need this drive to work with are Akai S5000 / S3000
series digital audio samplers with 50-pin SCSI host controllers, I assume
they are SCSI-1. I only use my PC's SCSI cards to perform maintenance upon
the drives I fit to samplers.

Even if they are not SCSI1, it is likely that they use a slow/uncritical
transfer mode because it is sufficient for audio. The narrow Adaptec
seems to behave very similar than the Akais (don't see the drive at
all). This really look like a problem with the wide interface of the
disk (high-byte termination).

[...]
I have a few other 68-way cables (with similar terminators) and I am getting
the same results with them as before, the drive is recognised, read speed is
17MB/sec.

Hmm ... and you are sure that you havn't limited the transfer mode to
Wide-Fast10 or Narrow-Fast20 in the setup of the 2940UW by accident?

Other LVD drives work fine using those centronics terminators. Is there
any
reason that this U320 drive would not work at all? I thought high-byte
termination was only required when connecting narrow devices to wide SCSI
cable / bus?

The other way round. If you connect a narrow device to a wide bus there
are no open lines and no problem (assumed that the wide bus is correctly
terminated).

If you connect a wide device to a narrow bus, the high byte of the
device-interface is floating. Some devices don't work at all in this
configuration. A termination for the high byte must be provided by the
wide/narrow-adapter or the device itself. Because 80pin SCA drives have
no terminators onboard, the adapter must do it for them.

Right, that makes sense. So it's the high byte of the *drive* that is
floating about, unterminated - and not the high byte of the *host
controller* that causes the problems as I originally thought?

Exactly. The 2940U has no high byte at all and the 2940UW can terminate
it with its onboard terminator if you connect a narrow bus.

Let me try to explain why floating lines are a problem:
Parallel SCSI use no dedicated address lines, instead the device address
(SCSI ID) is transferred over the data lines. But the address is not
binary encoded, every data line simply represent one address. This is
the reason why the number of devices on a narrow bus is limited to 8 but
a wide bus can work with 16 devices.
1) Arbitration
If a device want to access the bus it must do a so called arbitration
(required to avoid collisions). To arbitrate a device drive the BSY
signal and its own ID (the corresponding data line) active and wait a
defined time. Then it looks at the other data lines: If there is a data
line active that corresponds to a SCSI-ID with higher priority the
device has lost the arbitration and the SCSI protocol define that it
must release the bus now (the bus termination pulls undriven lines to
inactive state). At this time floating data lines can look active, like
devices that lost arbitration but don't release the bus and such a
protocol error may force the winning device to abort its transfer.
2) Selection
After a device has won arbitration it must select the communication
partner. Therefore it drives the BSY and SEL signals active and place
its own ID and the target ID together with valid parity on the data bus.
The SCSI protocol define that a target must not respond to a selection
if there are more than 2 data lines active or the parity is invalid. But
this is the case if floating data lines look active at this time.

In your case Problem 2) may occur at the device scan. The narrow host do
a correct selection but the wide device don't respond because it sees a
protocol error. After the selection timeout the host will give up and
continue with the scan.

Perhaps I need an active or LVD/SE terminator even though the terminator
will be attached to a 50pin centronics connector anyway?

Yes, at least for the Fast20 transfer mode.

So I may just have been lucky up until now - I have three 80-pin LVD drives
attached to those old 50-pin Akais, with standard passive terminators - they
have performed without error for years. They even run in series with various
other SCSI devices, notably Jaz drive and DVD-RAM, and they have been rock
solid until now.

This is no problem as long as a slower transfer mode is used. If the
Akai use Fast5 or asynchronous transfers, you can use 6m cable with
passive terminators.

Hopefully, the drive is simply faulty and I can indeed use U320 drives of
any brand, especially Fujitsu, on 50-pin buses.

Try the correct termination before declaring the disk as faulty. SCSI
don't allow floating signal lines, a wide interface requires wide
termination. Some devices may tolerate the floating high byte, but don't
expect that this will work. An exception are devices with a
"Narrow"-Jumper that can be forced in narrow mode.

Hmm, I don't think I've come across one of those. Occasionally there is a
'force SE' jumper. No good for me?

This has nothing to do with the bus width. The "Force SE" jumper simply
grounds the DIFFSENS line and prevent the disk from switching to LVD
mode. If you connect the Adaptec or the Akai, they will ground the
DIFFSENS line, the result is the same. The jumper is only needed if the
DIFFSENS signal is faulty wired.

To avoid the special "high-byte terminated adapter" think about this
solution:
Use a wide cable and connect the U320 disk with a mechanical-only
80/68-adapter (LVD-capable). Now use a mechanical-only 68/50-adapter to
connect the wide cable to the narrow SE-host (a SE-only adapter is
sufficient at this place). The wide terminator at the end of the cable
pulls all unused lines to defined levels (common for all disks if you
connect more than one!). The high-byte is unterminated at the other
side, this is not perfectly legal but it should work because there will
never be a data transfer on that lines (the narrow host can't do it).

Right, I see, that's not going to be easy since the drives must sit in
external enclosures which are all 50-pin. Unless I could obtain a 50-68 or
50-80 adapter with high byte termination built in.

Yes.

Or, use 68pin instead of 80 pin drives and set the drive's own terminator
on - would that work (assuming I do that only at the end of the SCSI chain)?

This will work. As you state, because on disks you can normally only
enable all terminators (high+low) together the disk must be at the end
of the bus and no additional terminator must be present on the external
cases second connector.


Micha
--
http://micha.freeshell.org/
.



Relevant Pages

  • Re: SCSI Tape Drive Not Recognized - "Termination" Problem?
    ... I am a TOTAL NEWBIE when it comes to SCSI! ... SCSI bus is a bus, and a bus needs to be ... Cannon) connector on one end, and the suitable device connectors for the ... the termination for the last device, as the bus would still extend a few ...
    (comp.os.linux.hardware)
  • Re: 37gb Ultrastar drive (SCA) scsi on a powermac 8500!
    ... He also gave me an SCA adaptor. ... They can be used with ordinary SCSI busses ... jumpers on the adapter - SCA drives typically do not have their own ID ... Note that there is no termination jumper (at least the spec sheet I ...
    (comp.sys.mac.hardware.storage)
  • Re: Ultra 60 SCSI External Interface
    ... 60's external SCSI interface. ... external termination as soon as I can. ... Who made the boxes which your external drives are in? ... Engineer's Handbook) appears to show a larger connector to connect to the ...
    (comp.sys.sun.hardware)
  • Re: PCI device driver vs SCSI device driver
    ... PCI is the thingy where you plug SCSI host adapters (the whitish slots ... the entire slot from the PCI bus. ... While the drives themselves stay on the SCSI bus ...
    (comp.os.linux.development.system)
  • Re: Ultra 60 SCSI External Interface
    ... 60's external SCSI interface. ... external termination as soon as I can. ... Who made the boxes which your external drives are in? ... Engineer's Handbook) appears to show a larger connector to connect to the ...
    (comp.sys.sun.hardware)