Date: Sat, 4 Jan 1997 15:00:01 -0800 (PST) From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-bugs Subject: Re: kern/2371: SCSI disk corruption Message-ID: <199701042300.PAA21441@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/2371; it has been noted by GNATS.
From: j@uriah.heep.sax.de (J Wunsch)
To: markd@grizzly.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/2371: SCSI disk corruption
Date: Sat, 4 Jan 1997 23:43:21 +0100
As markd@grizzly.com wrote:
> AHC options:
> controller ahc0
> options AHC_TAGENABLE
> options AHC_SCBPAGING_ENABLE
^^^^^^^^^^^^^^^^^^^^ Turn this off, and see if your problem
persists. I think SCB paging is not
yet ready for prime-time.
> options AHC_ALLOW_MEMIO
I think problems with AHC_ALLOW_MEMIO are rather `binary' in nature:
it either works well, or starts to go afoul very early in the game.
Problems with tagged commands usually end up in ``Overlapped commands
attempted'' or something like this.
Eeek, no:
> ahc0: target 0 Tagged Queuing Device
> (ahc0:0:0): "HP C3725S 6039" type 0 fixed SCSI 2
> sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors)
This one is known to choke on tagged commands!
> The last major activity before the crash was formatting of sd2, an IOMega
> Zip drive. SCSI format, partition and newfs had generated the following
> message:
>
> Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): UNIT ATTENTION asc:28,0
> Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): Not ready to ready transition, medium may have changed
> Jan 3 22:47:13 osprey /kernel: Debugger("sdopen: no slices") called.
> Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB
> Jan 3 22:47:13 osprey /kernel: sd2 could not mode sense (4). Using ficticious geometry
> Jan 3 22:47:13 osprey /kernel: sd2: invalid primary partition table: no magic
That's something different, and basically a known problem. You might
get around this by creating a `quirk' record for this device in
/sys/scsi/scsiconf.c, and assign it to the `od' driver. This one has
a better understanding of removable media devices.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701042300.PAA21441>