From owner-freebsd-current@FreeBSD.ORG Mon Sep 22 06:54:10 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 4C8CC16A4B3 for ; Mon, 22 Sep 2003 06:54:10 -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 E784143FBD for ; Mon, 22 Sep 2003 06:54:06 -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)h8MDs38M020168; Mon, 22 Sep 2003 08:54:05 -0500 (CDT) Message-Id: <5.2.1.1.2.20030922085006.01274e28@www.computinginnovations.com> X-Sender: derek@www.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 22 Sep 2003 08:54:02 -0500 To: Soren Schmidt From: Derek Ragona In-Reply-To: <5.2.1.1.2.20030920145252.0132be50@www.computinginnovations .com> References: <5.2.1.1.2.20030920053435.012510b8@www.computinginnovations .com> <200309200807.h8K87j38049734@spider.deepcore.dk> <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: Mon, 22 Sep 2003 13:54:10 -0000 I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the= =20 9/20 snapshot. That also wouldn't complete a buildworld without breaking=20 with the hard drive error. I booted windows and stress tested the drive with all kinds of I/O. Not a= =20 hiccup. It isn't the hardware, it has to be the driver code under 5.1-current. -Derek At 02:53 PM 9/20/2003 -0500, Derek Ragona wrote: >The 9/19 snapshot has the same issues. > >I will try to cvsup it and build a new kernel, if I can. > > -Derek > > >At 05:36 AM 9/20/2003 -0500, Derek Ragona wrote: >>This was using the 9/18 snapshot, I tried to cvsup it to the most=20 >>current, but the drive errors prevent the update. >> >>I just reloaded with the 9/19 snapshot, and will report if the error=20 >>still 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=20 >>> nature (not >>> > on large files, or small files, etc.) >>> >>>And you are on an uptodate -current ? >>> >>>If so I'd suspect HW ... >>> >>>-S=F8ren >>_______________________________________________ >>freebsd-current@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-current >>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >