Xref: utzoo comp.sys.amiga.tech:8317 comp.sys.amiga:44108
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!att!cbnewsc!sft
From: sft@cbnewsc.ATT.COM (scott.thompson)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: Problems with Maxtor drives (merged threads)
Message-ID: <4922@cbnewsc.ATT.COM>
Date: 20 Nov 89 16:40:19 GMT
References: <22441@gryphon.COM>
Reply-To: sft@cbnewsc.ATT.COM (scott.thompson,ihp,)
Organization: AT&T Bell Laboratories
Lines: 53

In article <22441@gryphon.COM> rickf@pnet02.gryphon.com (Rick Flower) writes:
|greg@noel.CTS.COM (J. Gregory Noel) writes:
|
|>Scott Thompson (sft@cbnewsc.ATT.COM) writes:
|>>I have my large [1224-cylinder] Maxtor drive connected to a Commodore
|>>2090 controller.  ... [While preping] my amiga GURU'd and rebooted...
|>>Now the machine hangs at the BindDrivers call ... therefore I cannot Mount
|>>any partition to re-prep the drive.
|>
...
|
|Well, I was the original person that posted about my "Maxtor" problem, and I
|must say that MY problem was due to a stupid thing I did.. Mainly using the
|incorrect sectors/track value.. I used 32 instead of 24 sectors/track.  Once I
|got the correct value of 24, things have been working great!  I'm using a
|Maxtor XT3280 drive (220 Meg Formatted) if anyone is interested.. I've got it
|working great and it has been working for over a week now!  It DOES however
|come up with "NOT-A-DOS-DISK" the very first time it boots however.. I spin up
|the drive (it's in an external case) and then turn on the A2000.  I end up
|having to re-boot the system after it gets going a bit for it to work
|correctly...
|
...
|
|I'll assume that if you were to disconnect your Maxtor drive from the system,
|that the BindDrivers would run correctly enabling a complete boot?? You could
|possibly "and I do mean possibly" connect the drive to the SCSI bus after it
|has powered up, but I WOULDN'T -- AND I EMPHASIZE THAT -- WOULDN'T try that
|unless EVERYTHING else failed..  It is a strange problem though.  
|
|P.S. I'm also using an old 2090 controller..

The problem you described is not the same as my problem, I have had the
drive working for quite awhile.  My problem started when I decided to
re-partition the drive.  I created four partitions and the first three
went fine, it was only after the guru during the prep of the final
partition that this problem began.  This makes me believe my mountlist
is correct and that there is some other problem.

I cannot disconnect the Maxtor from the system if I want to use the drive
as it must be connected during the binddrivers call for the system to know
about the drive (and this is were it hangs).  Calling binddrivers again
later does not work; I believe this is because there is another drive
connected to the 2090 and the first binddrivers call starts the driver.
On subsequent calls, binddrivers thinks the device driver is already
running and nothing else is needed.

Again, thanks for the idea, but my problem does not appear to be the same
as yours.
-- 
  Scott Thompson, 45261, (IH 6W-207), AT&T Bell Labs, Naperville, Il. 60566

   VOICE: (312)-979-2237  UUCP: ...!att!ihlpa!sft  ARPA: sft@ihlpa.att.com