From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 01:07:57 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 464F816A4B3 for ; Sat, 20 Sep 2003 01:07:57 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F145B43FAF for ; Sat, 20 Sep 2003 01:07:55 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.9/8.12.9) with ESMTP id h8K87jj5049735; Sat, 20 Sep 2003 10:07:45 +0200 (CEST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9/Submit) id h8K87j38049734; Sat, 20 Sep 2003 10:07:45 +0200 (CEST) From: Soren Schmidt Message-Id: <200309200807.h8K87j38049734@spider.deepcore.dk> In-Reply-To: <5.2.1.1.2.20030919151835.01308600@www.computinginnovations.com> To: Derek Ragona Date: Sat, 20 Sep 2003 10:07:45 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 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 08:07:57 -0000 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 repeatedly > give: > ad4: timeout sending command=ca > > 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 (not > on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren