From owner-freebsd-stable@FreeBSD.ORG Mon Apr 14 13:09:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78E00A45; Mon, 14 Apr 2014 13:09:02 +0000 (UTC) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::13]) by mx1.freebsd.org (Postfix) with ESMTP id 8949C15BC; Mon, 14 Apr 2014 13:08:59 +0000 (UTC) Received: from yggdrasil.alkumuna.eu (unknown [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87]) by smtp4-g21.free.fr (Postfix) with ESMTP id 37F224C8155; Mon, 14 Apr 2014 15:08:49 +0200 (CEST) Received: from yggdrasil.alkumuna.eu (localhost [IPv6:::1]) by yggdrasil.alkumuna.eu (8.14.7/8.14.7) with ESMTP id s3ED8lZf043172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 14 Apr 2014 15:08:47 +0200 (CEST) (envelope-from troyax@yggdrasil.alkumuna.eu) Received: (from troyax@localhost) by yggdrasil.alkumuna.eu (8.14.7/8.14.7/Submit) id s3ED8jRi043171; Mon, 14 Apr 2014 15:08:45 +0200 (CEST) (envelope-from troyax) Date: Mon, 14 Apr 2014 15:08:45 +0200 From: Troyax To: Haowu Ge Subject: Re: Freebsd 10 install kernel not booting. Message-ID: <20140414130845.GA43154@yggdrasil.alkumuna.eu> References: <20140328160019.GA93913@yggdrasil.alkumuna.eu> <20140404214900.6ff7681e@freedom.alkumuna.eu> <20140411135453.GA19755@yggdrasil.alkumuna.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org, Matthieu Volat X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 13:09:02 -0000 Thanks for the follow-up Haowu, it didn't work in itself but helped me find a work-around. I ran the following (slightly different) commands on my USB image: gpart bootcode -b /boot/boot0 da0 gpart bootcode -p /boot/boot1 -i 1 da0 gpart set -a active -i 1 da0 (with a warning message "gpart: attrib 'active': Device not configured") But it ended up with the same behaviour: the bootstrap stops (and reboot the machine) right before the "loading /boot/defaults/loader.conf" output message, which got me thinking that the problem may be in the stage 3. So I tried with a fresh fbsd10 USB image with only the /boot/loader from my fbsd9.2 (I mounted the USB stick and cp-ed the file) and voila, it works. I took a very quick look at the /sys/boot/i386/loader code, and the major (only?) difference I found there was the NANDFS support. But I don't know if it is used for the USB image and there are probably lots of other possible cause - it needs a more expert look I think. Troyax. On Sun, Apr 13, 2014 at 10:43:31AM +0800, Haowu Ge wrote: > Try this? > gpart bootcode -b /mnt2/boot/boot0 da0 > gpart bootcode -b /mnt2/boot/boot1 /dev/da0s1 > gpart set -a active -i 1 da0 > > > 2014-04-11 21:54 GMT+08:00 Troyax : > > > > Hello, since there's no answer yet, and it seems to be a bootloader > > related problem, would you try the following? > > > * Create a 10.0 memory stick > > > * From your 9.2 environment, copy the bootcode to the memory stick: > > > # gpart bootcode -b /boot/boot da0 > > > * Try and see if it boots > > > > I have just tried your suggestion, but the result is the same. To be more > > precise, BTX loader 1.02 seems to launch the loader correctly; but it stops > > (and reboots the machine) very early on loading the kernel.