Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!nntp.crl.com!reason.cdrom.com!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: WDINTR timeouts, why> Date: Tue, 11 Jun 1996 20:19:26 -0700 Organization: Walnut Creek CDROM Lines: 11 Message-ID: <31BE373E.237C228A@FreeBSD.org> References: <4phn9v$f75@mark.ucdavis.edu> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.2-CURRENT i386) To: Jason Gabler <ccjason@quadrophenia.ucdavis.edu> Jason Gabler wrote: > Jun 10 10:45:47 magicbus /kernel: wd1s1b: wdintr: timeout waiting for > status reading fsbn 12308 of 12304-12351 (wd1s1 bn 12308; cn 18 tn 9 sn > 32)wd1: status ff<busy,rdy,wrtflt,seekdone,drq,ecc_cor,index,err> error > 1<no_dam> The most likely explanation is that this drive is slowly failing and will eventually die completely. -- - Jordan Hubbard President, FreeBSD Project