Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Oct 1996 21:41:51 -0500
From:      "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To:        proot@horton.iaces.com, questions@freebsd.org
Subject:   Re: Problems with Quantum 4gig drive
Message-ID:  <9610040241.AA28429@iworks.InterWorks.org>

Next in thread | Raw E-Mail | Index | Archive | Help

>         I've got a Compaq DeskPro 2000 (133MHz) machine, with 32 meg,
> an Adaptec 2940UW, a Seagate ST32550W 2 gig drive on sd0 and
> a Quantum XP34300W 4gig drive on sd1. 
>
> My problem is the Quantum won't work. I did install it and things went fine
> for a couple of hours then. I get parity errors and the SCSI bus hangs up.
>
> I did disable the IDE on the motherboard of the Compaq, and without the
> Quantum drive it works fine. The Quantum is in the middle connector on 
> the internal cable, the Seagate is on the end, there is nothing connected
> to the external connector.
>
> Could it be I need to set a jumper on the quantum? Termination? I didn't
> receive a book with the Quantum (I do have one for the Seagate). The 
> drive came installed with an IDE drive, I pulled the IDE, and installed
> the Seagate as sd0 and jumpered the Quantum as sd1. That's the only
> changes to the drives.

We've got a couple of Quantum 2GB (XP32150?) drives at work hanging off
a 2940UW and they work with no problems - they aren't being utilized
too much yet, though.  We're also running FreeBSD 2.1.5-RELEASE.   

The Adaptec 2940s seem to be touchy about cabling and termination.  You
want to double check these.  I've also had a bad internal connector on
my ribbon cable - you might try a different one if you have more than
a two device ribbon cable.

The last Quantum we pruchased came without a manual also.  You can get
all the information you need off Quantums web site (www.quantum.com).
Our drive didn't work at first - it wasn't set to spin up at power on
and we had to set the appropriate jumper.  Make sure that the Seagate
is terminated properly since it's the last device in the chain.  I never
use power from the SCSI bus to terminate and use the drives power to
terminate.

You can also try swapping drive positions on the cable to see if the
Seagate will then have the same problem on the same connector.

If all the hardware checks out, then you can go into SCSI Select Utilities
and try to disable SCSI parity checking.  The driver will read this 
value from the SEEPROM and use it to [dis|en]able parity error detection.
This isn't the optimal solution 'cause it could be masking out a real
problem with the drive.

Oh, check you've got a good power supply to the drive and that it's
not running too hot.  If it takes a couple of hours for the drive to
start generating errors, it could be heat related...

Dan Eischen
deischen@iworks.InterWorks.org



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?9610040241.AA28429>