Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Aug 1997 14:31:20 +0930
From:      Mike Smith <mike@smith.net.au>
To:        pius@ienet.com
Cc:        freebsd-hardware@freebsd.org, terryl@ienet.com, robert@ienet.com
Subject:   Re: wdunwedge failed 
Message-ID:  <199708200501.OAA01146@word.smith.net.au>
In-Reply-To: Your message of "Tue, 19 Aug 1997 20:16:53 MST." <199708200316.UAA16965@iago.ienet.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

> 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






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708200501.OAA01146>