From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 14 12:16:35 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 087AD16A4CE for ; Sun, 14 Mar 2004 12:16:35 -0800 (PST) Received: from cydem.org (h68-149-254-167.ed.shawcable.net [68.149.254.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE86C43D1F for ; Sun, 14 Mar 2004 12:16:34 -0800 (PST) (envelope-from soralx@cydem.org) Received: by cydem.org (Postfix/FreeBSD, from userid 426) id 01C9F393FA; Sun, 14 Mar 2004 13:16:33 -0700 (MST) Received: from soralx.cydem.org (h68-149-254-171.ed.shawcable.net [68.149.254.171]) by cydem.org (Postfix/FreeBSD) with ESMTP id 79CD038313; Sun, 14 Mar 2004 13:16:33 -0700 (MST) From: To: kuku@kukulies.org> Date: Sun, 14 Mar 2004 13:16:31 -0700 User-Agent: KMail/1.5 References: <20040311153709.AD00216A4D6@hub.freebsd.org> <4054532A.6090308@DeepCore.dk> <20040314154442.GA60773@gilberto.physik.rwth-aachen.de> In-Reply-To: <20040314154442.GA60773@gilberto.physik.rwth-aachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403141316.31755.soralx@cydem.org> cc: freebsd-hackers@freebsd.org Subject: Re: off topic - disk crash X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Mar 2004 20:16:35 -0000 > With certain directories or files I get READ_DMA timeouts and also the > system hangs totally when a certain type of error occurs. > > ad2: TIMEOUT - READ_DMA retryinmg (2 retries left) LBA=24703729 > ad2: WARNING - READ_DMA Interrupt was seen but but timeout fired > LBA=24703729 ad2: WARNING - READ_DMA Interrupt was seen but but taskqueue > stalled LBA=24703729 ad0: FAILURE - WRITE_DMA status=51 > error=40 LBA=9825063 > > What I find strange is that the failing drive on the secondary IDE channel > causes the primary channel also to fail. > > I wonder if this has to happen or could be avoided. I can only reboot from > that point on. I used a straightforward approach: copy files with midc, note on which the system freezes, reboot, and skip those files. Eventually I got everything impotant recovered. BTW, one of the few files which could not be read was the Apache log - another reason to keep huge logs on sepatate drives (or slices, at least). :) Timestamp: 0x4054BCAD [SorAlx] http://cydem.org.ua/