HP DAT drive on PI has trouble with large block sizes

Thread View: comp.sys.sgi.hardware

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Steve Gaarder Mon, 21 Dec 1992 17:28

Author: Steve Gaarder
Date: Mon, 21 Dec 1992 17:28

17 lines
1042 bytes

We have an HP DAT drive connected to a Personal Iris 4D/20 running Irix
4.0.5.  I modified /usr/sysgen/master.d/tpsc to allow the machine to
identify the unit as a DAT, and that seems to have worked.  However,
when I try to use a tar blocking factor greater than 64 (= a block size
greater than 32768), I get the following error:

sc0,7,0: cmd=0x8 disconnected on non-word boundary (addr=C05CB402, 0x0 left).
  Resetting SCSI bus

I have the same problem when I put the drive on a 4D/35.  Any ideas
what's going on here?

Thanks,

Steven Gaarder                              Network and Systems Administrator
gaarder@actech.com                          A C Technology, Ithaca, N.Y., USA

Re: HP DAT drive on PI has trouble with large block sizes

Author: David (Duis) Story
Date: Tue, 22 Dec 1992 02:40

24 lines
1516 bytes

In article <BzMDuq.E7t@well.sf.ca.us> gaarder@well.sf.ca.us (Steve Gaarder) writes:
>
>We have an HP DAT drive connected to a Personal Iris 4D/20 running Irix
>4.0.5.  I modified /usr/sysgen/master.d/tpsc to allow the machine to
>identify the unit as a DAT, and that seems to have worked.  However,
>when I try to use a tar blocking factor greater than 64 (= a block size
>greater than 32768), I get the following error:
>
>sc0,7,0: cmd=0x8 disconnected on non-word boundary (addr=C05CB402, 0x0 left).
>  Resetting SCSI bus
>
>I have the same problem when I put the drive on a 4D/35.  Any ideas
>what's going on here?

This message indicates that the device did not disconnect on a 32-bit
word boundary.  The device itself may allow this to be configured; I
believe our SCSI drivers require this.

Cheers,

David Story                        	        Silicon Graphics, Inc.
story@bent.wpd.sgi.com				Mountain View, California

I've changed my name, so duis@sgi.com may bounce, please use story@sgi.com.

Re: HP DAT drive on PI has trouble with large block sizes

Author: Dave Olson
Date: Wed, 23 Dec 1992 04:30

32 lines
1965 bytes

In <BzMDuq.E7t@well.sf.ca.us> gaarder@well.sf.ca.us (Steve Gaarder) writes:


| We have an HP DAT drive connected to a Personal Iris 4D/20 running Irix
| 4.0.5.  I modified /usr/sysgen/master.d/tpsc to allow the machine to
| identify the unit as a DAT, and that seems to have worked.  However,
| when I try to use a tar blocking factor greater than 64 (= a block size
| greater than 32768), I get the following error:
| 
| sc0,7,0: cmd=0x8 disconnected on non-word boundary (addr=C05CB402, 0x0 left).
|   Resetting SCSI bus
| 
| I have the same problem when I put the drive on a 4D/35.  Any ideas
| what's going on here?

You need to bug Ardat or your distributor for newer firmware.
Almost certainly this is not a drive purchased from SGI.  I
asked Ardat to put the fix into their standard firmware, since
SGI isn't the only system with problems on non-word aligned
DMA (which is what happens when the drive disconnects on
a boundary not a multiple of 4 bytes from start of transfer).

They said they would do put it in their next general firmware
release, but either that hasn't happened, or you have
older firmware.

There is no workaround except to disable SCSI disconnects,
which has problems of its own (see master.d/scsi).
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads