From owner-freebsd-questions@FreeBSD.ORG Fri May 8 05:38:55 2009 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 36248106566C for ; Fri, 8 May 2009 05:38:55 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 055F28FC0A for ; Fri, 8 May 2009 05:38:54 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id B9F0E7E837; Thu, 7 May 2009 21:38:53 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Fri, 8 May 2009 07:38:51 +0200 User-Agent: KMail/1.11.2 (FreeBSD/8.0-CURRENT; KDE/4.2.2; i386; ; ) References: <27ade5280905071446ucdb53f0q263efc713860d11b@mail.gmail.com> In-Reply-To: <27ade5280905071446ucdb53f0q263efc713860d11b@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905080738.52013.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: APseudoUtopia Subject: Re: Frozen on Boot - Kernel Hanging? 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: Fri, 08 May 2009 05:38:55 -0000 On Thursday 07 May 2009 23:46:54 APseudoUtopia wrote: > Hey, > > My server was fine when I went to work. When I got back, it was dead. > I had the datacenter reboot it, and it refused to boot. It just hangs > with no error message when booting. After the "Welcome to FreeBSD" > menu, it just freezes up. > > I have no idea where to start to fix this. Any ideas? Like Wojchiech said, most likely hardware. Try to boot a livecd and if that won't work either, it's time to yank out hardware. If you have a replacement or test machine, put the HDD in there and if the HDD isn't the problem you might be able to read it's log files to get hints about what hardware part is the problem. -- Mel