Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Aug 1998 10:40:12 -0500 (CDT)
From:      Chris <chrisj@outcast.media-net.net>
To:        freebsd-stable@FreeBSD.ORG
Subject:   WD errors
Message-ID:  <Pine.BSF.3.96.980803103400.419A-100000@outcast.media-net.net>

next in thread | raw e-mail | index | archive | help
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<busy> error 80<badblk>. after afew screens of that the message
will turn to  wd0: wdunwedge failed:
> wd0: status 80<busy> error 80<badblk>
> 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<busy> error 80<badblk>. 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980803103400.419A-100000>