From owner-freebsd-stable Wed Oct 28 12:08:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11113 for freebsd-stable-outgoing; Wed, 28 Oct 1998 12:08:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11093 for ; Wed, 28 Oct 1998 12:08:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00390; Wed, 28 Oct 1998 12:06:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282006.MAA00390@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Harold Gutch cc: stable@FreeBSD.ORG Subject: Re: HD problems In-reply-to: Your message of "Wed, 28 Oct 1998 19:00:05 +0100." <19981028190005.A426@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 12:06:17 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your disk is taking longer to handle the error than we allow it to. Your best bet at this point is probably to mount the partition forced readonly (mount -f -o ro), copy everything meaningful off the the partition, then dd zeroes over it to give the drive a chance to remap the sector(s) in question. > > 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 > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message