Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jun 1996 16:01:19 -0400 (EDT)
From:      "matthew c. mead" <mmead@Glock.COM>
To:        se@zpr.uni-koeln.de (Stefan Esser)
Cc:        hackers@freebsd.org
Subject:   Re: ST43400N
Message-ID:  <199606112001.QAA07036@Glock.COM>
In-Reply-To: <199606111955.AA13636@Sisyphos> from "Stefan Esser" at Jun 11, 96 09:55:12 pm

next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Esser writes:

> On Jun 11,  9:42, "matthew c. mead" wrote:
> } Subject: Re: ST43400N
> } M.R.Murphy writes:

> } > >  The drive hangs before a "fdisk sd1" completes, so I haven't
> } > > even gotten as far as writing a disktab for it, since I can't
> } > > get the probed geometry values for it.

> } > When it probed 2777M, what else did it say?

> } sd1(ncr0:2:0): Direct-Access
> } sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
> } 2777MB (5688447 512 byte sectors)

> } > What kind of SCSI interface do you have? What low-level
> } > formatters do you have available?

> } 	It's an NCR810 controller.  I don't believe it has any
> } low-level formatting capability, and I don't think it came with
> } much software, but I can see if it will let me lowlevel format
> } it.  Do you think that the problem is the low-level formatting of
> } the device?  Here's some info the sheet on the ST43400N has:

> } ** Already low-level formatted at the factory with six spare sectors
> } per cylinder, one spare cylinders/unit, one system cylinder/unit, and
> } one diagnostic cylinder/unit.

> The NCR can be used to low level format any SCSI drive
> with the "scsiformat" command, though I doubt it will
> make much of a difference.

	Hmm.  That's the last hope I was clinging to.

> If you are running a -current kernel, then please try
> one built with "options FAILSAFE". This will disable
> use of tagged command queues, which are the most likely
> cause of the problem you report.

> If the drive works with tags disabled, then I'll send 
> further directions to find out whether it is possible 
> to work around that problem. (You may comment out the
> call to scsi_start_unit() in /sys/scsi/sd.c for a test.)

	Do the above two paragraphs apply to a 2.1.0-RELEASE
kernel as well?  This drive is on a 2.1.0-R system.



-matt

-- 
Matthew C. Mead

mmead@goof.com
http://www.goof.com/~mmead/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606112001.QAA07036>