From owner-freebsd-current@FreeBSD.ORG Mon Apr 3 14:47:06 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG 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 7D32716A400; Mon, 3 Apr 2006 14:47:06 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E80B443D6D; Mon, 3 Apr 2006 14:47:03 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k33El2Mg000430; Mon, 3 Apr 2006 16:47:02 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <44313566.4060206@deepcore.dk> Date: Mon, 03 Apr 2006 16:47:02 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: KOT MATPOCKuH References: <3979a4b0604030704u4a8a43fcxb76bdaab0de5f0f2@mail.gmail.com> In-Reply-To: <3979a4b0604030704u4a8a43fcxb76bdaab0de5f0f2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: freebsd-current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Problems with SATA drives on PDC20771 and SiI3512 controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Apr 2006 14:47:06 -0000 KOT MATPOCKuH wrote: > Hello! > > I got problems with my SATA II drives. > > 1. If drive attached to Promise FastTrak TX2300 (PDC20771 chipset), all > "small" operations like fsck, newfs with this drive works propertly. > But on hard load (like "dump 0f - / | restore rf -" or something like > this) on this drive, I have a WRITE_DMA (or WRITE_DMA48) errors, disk > detach, and as result - system panic. > After reboot and fsck, I does not see anything on filesystem. > > boot -hsv log is attached, and named boot.promise.log. > Panic log is panic.promise.log. Since you are getting ICRC errors I'd suggest you try a new/different SATA cable. -Søren