Date: Mon, 19 Oct 1998 10:42:06 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Ben Smithurst <ben@scientia.demon.co.uk> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: wd0 wdunwedge errors Message-ID: <Pine.BSF.4.03.9810191041190.28969-100000@resnet.uoregon.edu> In-Reply-To: <19981017005318.A5558@scientia.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Oct 1998, Ben Smithurst wrote: > Doug White wrote: > > > wdunwedge is a function in the IDE controller driver that gets called when > > the interface timeouts too much and it needs to try to get the disk > > restarted. > > Ah, I see. Like the name says really :-) > > > If you get this a lot your disk is going south, something is > > sitting on IRQ 14 or your cables are going bad. > > Hmm.. I'm pretty sure no-one's sitting on IRQ 14, so I have to hope it's > the cables. The disk's only about 18 months old, it can't be dead > already :-( > > (Would BIOS disk power down settings cause this? I think they caused > timeouts before[1], but it was only a single line I used to see for > them. I haven't seen it for wd2, which takes ages to start up, so it > probably isn't this.) Possibly. If it does take a while to get going again, it could be confusing the code. I'd suggest disabling spindown. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" 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.4.03.9810191041190.28969-100000>