From owner-freebsd-hardware  Tue Aug 19 22:05:19 1997
Return-Path: <owner-freebsd-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA29261
          for hardware-outgoing; Tue, 19 Aug 1997 22:05:19 -0700 (PDT)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29252
          for <freebsd-hardware@freebsd.org>; Tue, 19 Aug 1997 22:05:11 -0700 (PDT)
Received: from word.smith.net.au (lot.atrad.adelaide.edu.au [203.20.121.21]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id OAA22778 for <freebsd-hardware@freebsd.org>; Wed, 20 Aug 1997 14:35:07 +0930 (CST)
Received: from word.smith.net.au (localhost.atrad.adelaide.edu.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA01146;
	Wed, 20 Aug 1997 14:31:21 +0930 (CST)
Message-Id: <199708200501.OAA01146@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: pius@ienet.com
cc: freebsd-hardware@freebsd.org, terryl@ienet.com, robert@ienet.com
Subject: Re: wdunwedge failed 
In-reply-to: Your message of "Tue, 19 Aug 1997 20:16:53 MST."
             <199708200316.UAA16965@iago.ienet.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 20 Aug 1997 14:31:20 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> After running fine for a little over a month, it started spewing out
> the following message on the console:
> 
> wd0: wdunwedge failed:
> wd0: status 80<busy> error 80<badblk>
> wd0s1e: wdstart: timeout waiting to give command writing fsbn 80 of 80-95
> (wd0s1 bn 217168; cn 14 tn 157 sn 7)wd0: status 80<busy> error 80<badblk>

The disk appears to be dying

> The console flashes on and off and logging in at the console or via telnet
> doesn't work anymore. 

This is strange; what do you mean by "flashes on and off"?

> Has anyone else seen this? What's causing these errors and the flashing
> console? Is it a bad drive or a bad IDE controller? The cabling looks fine.

It sounds like the drive is either overheating or on its way out; 
fix/replace it ASAP, and MAKE A BACKUP if you haven't already.

mike