Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: yuma!jamison@ccncsu.colostate.edu (Jamie Gulden)
Newsgroups: comp.sys.sun
Subject: Re: SunOS 4.1.1 and Sync SCSI
Keywords: Hardware
Message-ID: <1368@brchh104.bnr.ca>
Date: 21 Jan 91 18:53:37 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 18
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v10n12
X-Sun-Spots-Digest: Volume 10, Issue 25, message 8
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <1232@brchh104.bnr.ca> rick@olivea.olivetti.com (Rick Meneely) writes:
>From article <976@brchh104.bnr.ca>, by mea@sparta.com (Mike Anderson):
>> We just got a copy of SunOS 4.1.1 here for our SparcStation 1+ and we are
>
>> [...] but I started getting all kinds of READ
>> errors from various blocks on the disk (that is when I tried the sync
>> jumper).
>
>> Has anyone seen this problem?

We have just spent a week with the disk error problem and (no thanks to
Sun) have found our problem to be in the SCSI interface.  Depending on the
length of the cables, the particular terminater used, and how many devices
are on the bus will affect the success or failure.  We originally got our
system running by removing one of the devices (leaving 2) from the bus.
National Peripherals suggested shorter cables even though we were below
the 6 meter limit and this worked and allowed us to put the third device
back on the machine.  Suns only suggestion was to remove the terminator.