From owner-freebsd-stable Wed Oct 24 5:31:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 728D537B407 for ; Wed, 24 Oct 2001 05:31:07 -0700 (PDT) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id f9OCV4C36977; Wed, 24 Oct 2001 14:31:04 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Wed, 24 Oct 2001 14:31:04 +0200 (CEST) Message-Id: <200110241231.f9OCV4C36977@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, Chris BeHanna Reply-To: freebsd-stable@FreeBSD.ORG, Chris BeHanna Subject: Re: Input/output Error In-Reply-To: <20011023235757.J24271-100000@topperwein.dyndns.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.4-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris BeHanna wrote: > On Wed, 24 Oct 2001, Oliver Fromme wrote: > > This sounds very much like a dying HD drive. Do you see any error > > messages from the kernel (on the console, or in the output from the > > dmesg command), mentioning something like "medium error"? If so, > > then it's the disk. > > The fact that he mentions "top" and "ps" specifically makes me > think "userland is out of sync with the kernel". That was my first thought, too, but then he mentioned that the problem only occurs after a few hours of uptime, so it can't be a kernel/bin out-of-sync problem (which would be there right after booting). It definitely sounds like a hardware problem. Could be the disk (this is the first thing I would check), but it could also be a problem with the controller, maybe a temperature problem (maybe it gets too hot after a few hours). Checking the fans is certainly not a bad idea. As for the non-existing error messages indicating hard disk errors -- is syslogd running at all? Maybe it died just like ps and top. Try logging some stuff yourself, like "/usr/bin/logger foo bar" -- does it end up in the messages file? If not, can you "echo foo bar >> /var/log/messages"? If that causes I/O errors, too, then there's your reason. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message