Date: Tue, 8 Oct 1996 15:28:58 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: gordon@drogon.net (Gordon Henderson) Cc: freebsd-scsi@freebsd.org Subject: Re: Buslogic controller, Sync mode & a SCSI disk error Message-ID: <199610081928.PAA11730@hda.com> In-Reply-To: <Pine.LNX.3.91.961010172220.1551L-100000@unicorn> from "Gordon Henderson" at Oct 10, 96 06:08:30 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> So - 2 different versions of the Buslogic board, and the most recent one
> doesn't come up in Sync mode.... Any reason why? (According to Buslogic,
> that version of board firmware is good and I should use Linux instead of
> FreeBSD - I did boot Linux on it once while testing it and Linux correctly
> enabled all devices in 10MB/sec sync mode - Why doesn't FreeBSD?)
In bt.c the driver is reading back the board setup and interpreting
the setting as being for async only. Either the Linux driver
ignores the setting or the FreeBSD driver misinterprets the setting.
Do you have a Buslogic utility to set up the board? See if it has
a setting to permit synchronous negotiation.
>
> 2nd problem: One of the disks seems to have a fault. Heres the errors
> from the messages file:
>
> /kernel: sd1(bt0:1:0): MEDIUM ERROR info:272133 asc:11,0
> Unrecovered read error
> /kernel: , retries:4
> /kernel: sd1(bt0:1:0): MEDIUM ERROR info:272133 asc:11,0
> Unrecovered read error
> /kernel: , retries:3
> /kernel: sd1(bt0:1:0): MEDIUM ERROR info:272133 asc:11,0
> Unrecovered read error
> /kernel: , retries:2
> /kernel: bt0: Try to abort
> /kernel: bt0: not taking commands!
> /kernel: Debugger("bt742a") called.
> /kernel: bt0: Abort Operation has timed out
>
> at this stage the machine rebooted it's self, fsck'd ok and carried on.
> (It's a news server). That disk isn't used for swap so it was a file read
> that caused the failure. Why should reading a duff sector cause the system
> to crash?
A SCSI disk won't slip the sector on an unrecovered read error - it doesn't
know what to put there. You'll have to write something there, preferably
by restoring the partition, or by using "dd" to write something to that sector
once you've decided what to write there. If you do decide to restore
the partition blast it full of zeros using dd first to make sure any failing
sectors get mapped out on the write failure.
The problem with bt0 locking up and rebooting on this error is a bug.
--
Peter Dufault Real-Time Machine Control and Simulation
HD Associates, Inc. Voice: 508 433 6936
dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610081928.PAA11730>