From owner-freebsd-hardware Mon Oct 6 08:05:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03362 for hardware-outgoing; Mon, 6 Oct 1997 08:05:36 -0700 (PDT) (envelope-from owner-freebsd-hardware) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03355 for ; Mon, 6 Oct 1997 08:05:32 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id JAA13888; Mon, 6 Oct 1997 09:05:23 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA00189; Mon, 6 Oct 1997 09:05:21 -0600 (MDT) Date: Mon, 6 Oct 1997 09:05:21 -0600 (MDT) Message-Id: <199710061505.JAA00189@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , hardware@freebsd.org Subject: Re: Strange error message In-Reply-To: <199710060854.SAA01131@word.smith.net.au> References: <199710060647.AAA28851@rocky.mt.sri.com> <199710060854.SAA01131@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I haven't booted up my second disk in a long time in my laptop, and now > > I get this error: > > > > wd0: interrupt timeout: > > wd0: status 50 error 0 > > wd0: interrupt timeout: > > wd0: status 50 error 1 > > The interrupt timeout suggests that either the drive electronics have > died, or that you have a connector problem; have you tried removing and > replugging it? I'll try that now. Sigh, the same thing happens. :( > > Unfortunately, it's on my root partition, so 'dd' doesn't even work. > > Unfortunately, the disk is 'unclean', so I can't even mount it > > read-write to go find the offended disk block. I suspectk it's trying > > to read some block on my disk that went bad, but the error recovery is > > such that once it starts to read it, it can't get past it. Is there > > something I can do to recover, or is it time to get a new disk (I don't > > even know if I can buy one for a machine this old)? I haven't noticed > > anything wrong on the DOS side of the disk, but it just might not have > > any bad-spots on that part of the disk. > > The error above doesn't really indicate a bad sector. It's odd though > that the disk works under DOS, unless DOS doesn't use the interrupt for > the disk but instead polls for status. Even more interesting is that I can fsck the /usr partition w/out any problems. > It's possible that the error is such that the firmware on the drive > crashes trying to deal with it, and this is the cause of the disk > "cycling" as you describe it. That's what I'm thinking. > > Thanks for any help you can provide! > > I'm mildly puzzled that the disk works at all in any other situation. > What sort of disk is it? You say "second" above; do you have another > identical unit? No, I have a smaller 'spare' drive that I keep -current installed on. My primary disk has two partitions, one for Win95, the other FreeBSD. I can read all of the DOS partition, and all but the root partition on the FreeBSD side. Nate