From owner-freebsd-stable Wed Oct 28 10:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24388 for freebsd-stable-outgoing; Wed, 28 Oct 1998 10:01:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24377 for ; Wed, 28 Oct 1998 10:01:00 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA00477 for stable@FreeBSD.ORG; Wed, 28 Oct 1998 19:00:05 +0100 (CET) Message-ID: <19981028190005.A426@foobar.franken.de> Date: Wed, 28 Oct 1998 19:00:05 +0100 From: Harold Gutch To: stable@FreeBSD.ORG Subject: HD problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, last night all of a sudden my box halted, without panicing or rebooting. After pressing the reset-key, it came back up, and didn't manage to finish fscking a partition on an IDE-disk of mine. Phases 1-4 of fsck passed as normal, but then I got the following errormessages: ** Phase 5 - Check Cyl Groups wd1: interrupt timeout: wd1: status 58 error 0 wd1: interrupt timeout: wd1: status 50 error 1 the last 4 lines being repeated every 30s or so. At this point fsck seemed to repeatedly try to access the same part of the disk over and over again without ever timeouting or stopping. I watched this for about 10 minutes, then rebooted again, booted in singleuser-mode, removed the appropriate entry from my /etc/fstab (luckily this happened on no 'vital' disk) and booted again. bad144 -s -v wd1 behaved very similar to fsck, from the sounds the disk made, I would say that it tried to access one part of the disk over and over again. I haven't freed up enough space to try dd'ing the disk into a file, then mounting it via a vnode, to at least partially save some data, but I hope to achieve this later on tonight. Is there anything else I'm able to do to fix the disk (at least to get to know which parts of it are broken, mark the bad sectors and then do a fsck over the rest or something alike) or can I just hope that the dd will save some of the data ? -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message