From mboxrd@z Thu Jan  1 00:00:00 1970
From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
Message-ID: <20040303201135.GA5853@sigint.cs.purdue.edu>
References: <86d7c718c6dadec0e726d6af0614d49c@proxima.alt.za> <200403031134.i23BYcZq099220@adat.davidashen.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200403031134.i23BYcZq099220@adat.davidashen.net>
Date: Wed,  3 Mar 2004 15:11:35 -0500
Topicbox-Message-UUID: 10f707ca-eacd-11e9-9e20-41e7f4b1d025

On Wed, Mar 03, 2004 at 03:34:38PM +0400, David Tolpin wrote:
> 
> cpu% cat /dev/sdC0/ctl
> inquiry IBM-DTLA-307015                         
> config 045A capabilities 2F00 dma 00550020 dmactl 00550020 rwm 16 rwmctl 16
> geometry 29336832 512 16383 16 63

Oh my, the dread Deathstar 75GXP.

Before you go any further, I'd recommend downloading Hitachi's (formerly
IBM's) Drive Fitness Test floppy image and run its "advanced" drive test
a few times.  Your disk may be about to go toes-up.

http://www.hgst.com/hdd/support/download.htm

(I understand that it's not giving you trouble under FreeBSD, but it could
be that FreeBSD is masking or oblivious to a drive problem.)