From owner-freebsd-questions@FreeBSD.ORG Sun May 4 18:16:25 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD4BE1065673 for ; Sun, 4 May 2008 18:16:25 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA708FC17 for ; Sun, 4 May 2008 18:16:24 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.2/8.14.2) with ESMTP id m44IGIP1021615; Sun, 4 May 2008 20:16:18 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.2/8.14.2/Submit) with ESMTP id m44IGIIo021612; Sun, 4 May 2008 20:16:18 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 4 May 2008 20:16:18 +0200 (CEST) From: Wojciech Puchar To: Christian Zachariasen In-Reply-To: <4a89d1190805040335r18ecc433ie6631a64866fd99a@mail.gmail.com> Message-ID: <20080504201503.H21598@wojtek.tensor.gdynia.pl> References: <4a89d1190805040335r18ecc433ie6631a64866fd99a@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Mailing Lists , Colin Brace Subject: Re: server (partly) fails: hardware? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2008 18:16:26 -0000 > Can you predict at what point the server will crash? Is it after performing > a specific action, or at a certain time of day? i think it's quite inpredictable, with probability proportional to disk load. > > If you can connect a monitor to the server and actually see what happens and > also if it still accepts keystrokes and stuff, that would probably help in > diagnosing the problem. yes it will. i had such problem many times. it's always disk/cables/controller problem. > > Another tip might be to download memtest86 and run it for a while on the memory is fine, disk or disk controler or cables are not.