From owner-freebsd-stable@FreeBSD.ORG Sat Jun 19 08:13:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04D3E1065670 for ; Sat, 19 Jun 2010 08:13:45 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 45D8F8FC16 for ; Sat, 19 Jun 2010 08:13:43 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA04887; Sat, 19 Jun 2010 11:13:36 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OPtBH-000EQH-SC; Sat, 19 Jun 2010 11:13:35 +0300 Message-ID: <4C1C7C2F.8090203@icyb.net.ua> Date: Sat, 19 Jun 2010 11:13:35 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Jeremy Chadwick References: <1276844904.7519.19.camel@almscliff.bubblegen.co.uk> <20100618082127.GA34578@icarus.home.lan> <1276876031.7519.39.camel@almscliff.bubblegen.co.uk> <20100618174208.GA47470@icarus.home.lan> In-Reply-To: <20100618174208.GA47470@icarus.home.lan> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Matthew Lear , FreeBSD Stable Subject: Re: 7.2-RELEASE-p4, IO errors & RAID1 failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jun 2010 08:13:45 -0000 on 18/06/2010 20:42 Jeremy Chadwick said the following: > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > I've always read IDNF to mean "OS requested access (read or write) to an > LBA which is out of bounds", where "out of bounds" means "not between 0 > and ". How exactly is that possible? Alexander, do you have > any familiarity with this error code per ATA spec? I think that there is another possibility. I think that sector IDs could be written somewhere on media, in some sector service information block. And if that information can not be read, then the sector can not be found. But I am not sure, just trying to come up with an explanation. -- Andriy Gapon