From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:06:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 632FC1065675 for ; Thu, 1 Jul 2010 16:06:24 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 456748FC34 for ; Thu, 1 Jul 2010 16:06:23 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta02.emeryville.ca.mail.comcast.net with comcast id cduK1e0031HpZEsA2g6Pfz; Thu, 01 Jul 2010 16:06:23 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta14.emeryville.ca.mail.comcast.net with comcast id cg6N1e00T3S48mS8ag6Pyd; Thu, 01 Jul 2010 16:06:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D91B29B425; Thu, 1 Jul 2010 09:06:22 -0700 (PDT) Date: Thu, 1 Jul 2010 09:06:22 -0700 From: Jeremy Chadwick To: GNUbie Message-ID: <20100701160622.GA98823@icarus.home.lan> References: <4C280435.4060603@halplant.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: maurovale@gmail.com, freebsd-stable@freebsd.org Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:06:24 -0000 On Thu, Jul 01, 2010 at 11:59:43PM +0800, GNUbie wrote: > Hello MV, > > On Thu, Jul 1, 2010 at 11:47 PM, M. Vale wrote: > > > > Hum strange I've seen this occur on 2 types of situations: > > > > 1 - virtualbox or other module loaded at boot time > > 2 - Hardware problem > > > > To fix it you have a list of small options. > > > > The first one is by booting with the FreeBSD CD and choosing rescue/upgrade > > system > > > > Other option is by removing Memory DIMM's to ensure that the problem is not > > caused by a fault RAM module. > > I am currently running memtest86 here on my livecd. If there is no > error, then this could be something else. > > Still strange for me on the stdout before my system reboots that says: > "Cannot dump. Device not defined or unavailable." Does it mean that > when loading the kernel, it cannot dump it to the / or some other > designated place? Kernel crash dumps are not enabled by default. You need to define the following in /etc/rc.conf before that will happen: dumpdev="auto" Be aware that kernel crash dumps don't always work reliably -- or rather, the savecore(8) portion (once the system is back up, writing the crash details to files in /var/crash on the filesystem). Of course, I'm going off of history (circa 2007), but there wasn't ever any indication that the problem was fixed: http://www.freebsd.org/cgi/query-pr.cgi?pr=118255 If you can't get the OS installed (e.g. this is happening when booting the FreeBSD installation CD), you're kinda out of luck, unless others know of a way around it. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |