From owner-freebsd-fs@FreeBSD.ORG  Thu Jan  5 04:37:50 2006
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: freebsd-fs@freebsd.org
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4453A16A41F
	for <freebsd-fs@freebsd.org>; Thu,  5 Jan 2006 04:37:50 +0000 (GMT)
	(envelope-from v.velox@vvelox.net)
Received: from S1.cableone.net (s1.cableone.net [24.116.0.227])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 770CB43D5F
	for <freebsd-fs@freebsd.org>; Thu,  5 Jan 2006 04:37:49 +0000 (GMT)
	(envelope-from v.velox@vvelox.net)
Received: from vixen42.vulpes (unverified [24.119.122.41]) 
	by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 42092093 
	for <freebsd-fs@freebsd.org>; Wed, 04 Jan 2006 21:38:18 -0700
Date: Wed, 4 Jan 2006 22:45:02 -0600
From: Vulpes Velox <v.velox@vvelox.net>
To: freebsd-fs@freebsd.org
Message-ID: <20060104224502.1e20fd36@vixen42.vulpes>
X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-NotAscii: charset=us-ascii
X-IP-stats: Incoming Last 0, First 231, in=395, out=0, spam=0
X-External-IP: 24.119.122.41
X-Abuse-Info: Send abuse complaints to abuse@cableone.net
Subject: Does this pose a danger to the FS on a disk?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jan 2006 04:37:50 -0000

ad10: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=355277839
ad10: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=358666287

Smartctl so it as being good when a long self test is done. Because
of that I believe the drive is good. The chipset is a Silicon Image
3112, which from my reading across the lists lead me to believe that
it could very well be the problem.

I am not getting any errors about it not completing it in those other
two retries, so I am assuming it will be fine till I have a chance to
get a proper sata card next week.

Any one have any opinions on if it is save to leave it in rw mode, if
it should be kicking into ro mode, or the like?