From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 14 07:45:09 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 9ABF116A4CE for ; Sun, 14 Mar 2004 07:45:09 -0800 (PST) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 850B943D2D for ; Sun, 14 Mar 2004 07:45:08 -0800 (PST) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.12.10/8.12.10) with ESMTP id i2EFih7Z061063; Sun, 14 Mar 2004 16:44:43 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.12.10/8.12.10/Submit) id i2EFigjq061062; Sun, 14 Mar 2004 16:44:42 +0100 (CET) (envelope-from kuku) Date: Sun, 14 Mar 2004 16:44:42 +0100 From: "Christoph P. Kukulies" To: =?iso-8859-1?Q?S=F8ren?= Schmidt Message-ID: <20040314154442.GA60773@gilberto.physik.rwth-aachen.de> References: <20040311153709.AD00216A4D6@hub.freebsd.org> <20040311174030.GB8190@tikitechnologies.com> <20040314104717.GA16158@gilberto.physik.rwth-aachen.de> <4054410E.3000401@DeepCore.dk> <20040314120411.GA16600@gilberto.physik.rwth-aachen.de> <4054532A.6090308@DeepCore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4054532A.6090308@DeepCore.dk> User-Agent: Mutt/1.4.1i 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 15:45:09 -0000 On Sun, Mar 14, 2004 at 01:42:18PM +0100, Søren Schmidt wrote: > Christoph P. Kukulies wrote: > > >the whole image including partition table so that I will not have to > >scan the disk for the start of the filesystems. > > Dont get another DTLA/AVER IBM disk, you will just have the same problem > again sometime in the future, stay away from IBM/Hitachi disks that is > based on these models (I dont know much about the newer disks from > Hitachi and frankly I wont waste my money on them to find out). Yes, I abandoned that idea now since things turn out a bit better. I have built up a recovery system with a new big disk as a FreeBSD 5.2.1 and hooked the troubled disk as in as ad2. I can mount -rf /dev/ad2s1g /mnt and find the old FS with all its entries. I copied over already some very important files and as it seems I will not be as catastrophical as I initially thought. 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. For recovering data this additionally painful and it would be nice I could get this fixed somehow. Another question is whether the read error occurs on the actual data or only during the fstat or directory read. Is it possible to mount a FS with an alternate superblock as information base or do I have to fsck (write back to the disk risking that things get worse) -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de