From owner-freebsd-questions@FreeBSD.ORG Wed Aug 31 23:25:21 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDB6E106564A for ; Wed, 31 Aug 2011 23:25:21 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8188FC08 for ; Wed, 31 Aug 2011 23:25:21 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p7VNPKxr070351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Aug 2011 16:25:21 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p7VNPKS8070350; Wed, 31 Aug 2011 16:25:20 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA26191; Wed, 31 Aug 11 16:20:54 PDT Date: Wed, 31 Aug 2011 23:20:48 -0700 From: perryh@pluto.rain.com To: basarevych@gmail.com Message-Id: <4e5f2440.hTx3mrA+qH6Xa5WH%perryh@pluto.rain.com> References: <4e5e32f0.9who12387o0moTmx%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, jdc@parodius.com Subject: Re: Is there way to get filename for specific LBA? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 23:25:21 -0000 Ross wrote: > >> Aug 31 05:13:24 da kernel: ad6: WARNING - READ_DMA UDMA ICRC > >> error (retrying request) LBA=107491647 > > ... > > What does > > > > ??egrep 'ad[0-9]|ata' /var/run/dmesg.boot > > > > report? > > atapci0: port > 0x20b8-0x20bf,0x20cc-0x20cf,0x20b0-0x20b7,0x20c8-0x20cb,0x20a0-0x20af > mem 0xe0284000-0xe02843ff irq 19 at device 31.2 on pci0 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > ad4: 238475MB at ata2-master UDMA100 SATA > ad6: 476940MB at ata3-master UDMA100 SATA > Trying to mount root from ufs:/dev/ad6s1a Different hardware than mine, so my w/a may not help. If it's only happened the one time, you may want to just write it off as a glitch. If it happens frequently, or you start getting unrecovered failures, you could _try_ atacontrol mode ad6 UDMA66 Slowing down the transfer rate may make it more tolerant of electrical noise, bad cabling, etc. This approach worked for me, but on a PATA (not SATA) port and using a different type of controller (a VIA 6421). > smartd also reports this: > > Aug 31 10:41:04 da smartd[886]: Device: /dev/ad6, Failed SMART > usage Attribute: 184 End-to-End_Error. > > I found this explanation: http://kb.acronis.com/content/9119 > > So disk is dying? Or is it cable. I have no physical access to > the server at the moment. I'll leave the SMART analysis to those who are familiar with it :)