From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 03:37:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C924416A4B3 for ; Sat, 20 Sep 2003 03:37:04 -0700 (PDT) Received: from www.computinginnovations.com (dsl081-142-072.chi1.dsl.speakeasy.net [64.81.142.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75F6B43FB1 for ; Sat, 20 Sep 2003 03:37:03 -0700 (PDT) (envelope-from derek@computinginnovations.com) Received: from p17.computinginnovations.com (dhcp-192-168-1-121.computinginnovations.com [192.168.1.121]) (authenticated bits=0)h8KAb0Hf009325; Sat, 20 Sep 2003 05:37:02 -0500 (CDT) Message-Id: <5.2.1.1.2.20030920053435.012510b8@www.computinginnovations.com> X-Sender: derek@www.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Sat, 20 Sep 2003 05:36:56 -0500 To: Soren Schmidt From: Derek Ragona In-Reply-To: <200309200807.h8K87j38049734@spider.deepcore.dk> References: <5.2.1.1.2.20030919151835.01308600@www.computinginnovations.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-current@FreeBSD.ORG Subject: Re: SATA drive lock-up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 10:37:04 -0000 This was using the 9/18 snapshot, I tried to cvsup it to the most current,= =20 but the drive errors prevent the update. I just reloaded with the 9/19 snapshot, and will report if the error still= =20 exists. As for the hardware, it is all brand new hardware, and the system dual=20 boots, the other OS has no issues. -Derek At 10:07 AM 9/20/2003 +0200, Soren Schmidt wrote: >It seems Derek Ragona wrote: > > I have a single SATA drive on an Adaptec 1210SA card. > > > > The drive will give a write error warning a few times, then will=20 > repeatedly > > give: > > ad4: timeout sending command=3Dca > > > > The only recovery is the reset switch, reboot single-user fsck, and then > > come back up in multiuser. > > > > These errors occur with disk access, but not with a predictable nature= =20 > (not > > on large files, or small files, etc.) > >And you are on an uptodate -current ? > >If so I'd suspect HW ... > >-S=F8ren