Date: Tue, 19 Aug 1997 20:16:53 -0700 From: pius@ienet.com To: freebsd-hardware@freebsd.org Cc: terryl@ienet.com, robert@ienet.com Subject: wdunwedge failed Message-ID: <199708200316.UAA16965@iago.ienet.com>
next in thread | raw e-mail | index | archive | help
We've got a machine with the following configuration: 100 MHz Pentium on an ASUS VX97 motherboard 32 MB RAM 1282 MB IDE drive (Seagate Medalist SL) 2 Intel EtherExpress PRO/100 ethernet adapters (fxp0 and fxp1) a cheap ISA video card FreeBSD 2.2-stable (from mid-June) 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 console flashes on and off and logging in at the console or via telnet doesn't work anymore. However it still responds to pings and it forwards packets from one ethernet interface to the other. However, after about an hour of spewing out these messages, the machine completely dies and it won't come up after a reboot (DRIVE BOOT FAILURE). The last time this happened, we left the machine turned off for a couple days, then turned it on, and it actually booted up fine, and now, after running most of the day, it's spewing out those error messages again. 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. Thanks very much for any help, Pius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708200316.UAA16965>