From owner-freebsd-current Thu Dec 16 0:19:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 3A29F14F23 for ; Thu, 16 Dec 1999 00:19:43 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 741A61DEA; Thu, 16 Dec 1999 09:19:50 +0100 (CET) Date: Thu, 16 Dec 1999 09:19:50 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Cc: sos@freebsd.dk Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <19991216091950.B8469@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <38588452.3383809C@wireless.net> <199912160729.IAA58142@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912160729.IAA58142@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote: > It seems Devin Butterfield wrote: > > I just recently compiled a kernel with the new ATA driver and have > > discovered a problem: if I run sysinstall, right when it says "probing > > devices, please wait (this can be a while)" error messages saying... > [snip] > > and after printing these messages a number of times, sysinstall will > > finally come up. If I quit sysinstall and then run it again, probing > > goes well and there are no timeouts. The interesting thing is that I can > > reproduce this problem by rebooting and running sysinstall. So, this > > only happens when running sysinstall for the first time after a boot. > > > Hmm, I'd put my disks on different channels, but thats just for > performance sake. I'm currently trying every wierd setup I can > imagine with the HW I have for testing, but I havn't been able > to get any of my test setups to exhibit this behavior... > > But I'm working on it... I am still having "disc contact lost messages" regularly too. I've been posting about them on several occasions some time ago. I haven't been able to pinn it down, however. IF they occur, they occur somewhere between 9:15 and 9:20 a.m. OR p.m. But they don't always. This used to be 10:15, but that changed _some weeks after_ the change of daylight saving time. I can't seem to relate it to anything. It is unlikely that it's a power glitch, because the system has been displaying the problem with two different UPS's. The machine is running current current's which are regularly updated. It's an ABIT BP6 and the disk causing problems is a WD 7200 RPM 18,2 Gb disk running UDMA33. It's the only IDE disk in the system; the other disks are all SCSI. The system is running 24/7. Other details were posted earlier. There are two important aspects of the problem: 1. The problem does not always occur: it's unpredictable 2. When it occurs, I can actually hear the disk spinning down and then up again. I haven't been able to find any relevant information at www.wdc.com. I am also not sure if it is a hardware problem, however since I never noticed the problem with the wd0 driver (which I used some months ago). Regards, Dave Boers. -- God, root, what's the difference? djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message