From owner-freebsd-stable Mon Aug 3 08:38:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10766 for freebsd-stable-outgoing; Mon, 3 Aug 1998 08:38:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from outcast.media-net.net (outcast.media-net.net [206.52.136.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10705 for ; Mon, 3 Aug 1998 08:38:11 -0700 (PDT) (envelope-from chrisj@outcast.media-net.net) Received: from localhost (chrisj@localhost) by outcast.media-net.net (8.8.8/8.8.7) with SMTP id KAA00445 for ; Mon, 3 Aug 1998 10:40:13 -0500 (CDT) (envelope-from chrisj@outcast.media-net.net) Date: Mon, 3 Aug 1998 10:40:12 -0500 (CDT) From: Chris To: freebsd-stable@FreeBSD.ORG Subject: WD errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG within the last week i have been running into problems when the system will go idle. It will still take something like telnet/http/ftp connections but will never complete them and allow the login. it will connect up but then never display a prompt. Errors on the console are as follows. wd0s1f: wdstart: timeout waiting to give command reading fsbn 3148892 of 3148892-3148893 (wd0s1 bn 3689468; cn 229 tn 167 sn 62)wd0: status 80 error 80. after afew screens of that the message will turn to wd0: wdunwedge failed: > wd0: status 80 error 80 > wd0s1f: wdstart: timeout waiting to give command reading fsbn 3148892 of 3148892-3148893 (wd0s1 bn 3689468; cn 229 tn 167 sn 62)wd0: status 80 error 80. the system will remain on-line (ie pingable) but will no longer display a console login either. a hard boot will take care of the problem but once the system drops into idle again they will reserface. Thanks chris jeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message