From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 2 18:40:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7AE116A4FD for ; Thu, 2 Nov 2006 18:40:22 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 844FD43D86 for ; Thu, 2 Nov 2006 18:40:12 +0000 (GMT) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.62) with esmtp (envelope-from ) id <1GfhU1-0004zB-EK>; Thu, 02 Nov 2006 19:40:09 +0100 Received: from e178044141.adsl.alicedsl.de ([85.178.44.141] helo=[192.168.1.128]) by inpost2.zedat.fu-berlin.de (Exim 4.62) with esmtpsa (envelope-from ) id <1GfhU1-00041H-Be>; Thu, 02 Nov 2006 19:40:09 +0100 Message-ID: <454A3B82.6040502@mail.zedat.fu-berlin.de> Date: Thu, 02 Nov 2006 19:40:02 +0100 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20061029) MIME-Version: 1.0 To: "Lars. Tunkrans" References: <1B6DFE5B-A4D4-48B8-AD72-4256A2462804@alphabox.net> <454A3745.9020103@bredband.net> In-Reply-To: <454A3745.9020103@bredband.net> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.44.141 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 6.1 problems on AMD64 Athlon 3800 - crashes from day 1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2006 18:40:23 -0000 Lars. Tunkrans wrote: > Angie Ahl wrote: >> >> I'm waiting for some answers to exactly what chipsets on the >> motherboard etc. Is there anything I should really check for if/when >> I can get back into the box. >> >> Thanks very very much >> >> Angie > > Hi, > One thing that I have experienced myself in new hardware is > substandard SATA cables. > One of my friends also resolved a situation where MS-Windows would > not install on a SATA disk > by changeing the SATA cable. I have a shuttle chassie with an > Athlon64 3800 , 1 GB RAM and thee Segate SATA 320 GB drives. > this box failed mysteriously and had unexplained HUNG situations. > > After I changed to SATA-300 cables with clip-locks on the > contactors all problems went away. > > //Lars Hello. You're right, I had a similar problem on my AMD64 box. One of two 200GB SATA 300 drives showed up errors after every third, fourth, sometimes tenth boot and then suddenly while running. Changing the SATA cable resolved the problem. SATA cabling is a piece of several tenth, not to say hundredth of an Euro - but it seems to be capable to bring down a whole server. All right, but this is one aspect. If Angie has already let the admins having exchanged RAM and motherboard and even more the CPU, I would suspect the PSU - but this depends on what the local Admin can see on the console if there is any. If the box hangs during init of drives, maybe the cabling is faulty. If not, I would exchange the PSU first ... Regards, Oliver