From owner-freebsd-questions@FreeBSD.ORG Wed Mar 3 16:22:42 2010 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 B2F6A106564A for ; Wed, 3 Mar 2010 16:22:42 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.103.93]) by mx1.freebsd.org (Postfix) with ESMTP id 8A76E8FC22 for ; Wed, 3 Mar 2010 16:22:42 +0000 (UTC) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.14.2/8.13.8) with ESMTP id o23GMX5v047090 for ; Wed, 3 Mar 2010 10:22:33 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <201003031622.o23GMX5v047090@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org Date: Wed, 03 Mar 2010 10:22:33 -0600 From: Martin McCormick Subject: Re: Remote Building of FreeBSD 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: Wed, 03 Mar 2010 16:22:42 -0000 I am beginning to wonder if there is something different about the way mfsbsd boots since it actually extracts itself in to memory upon boot. I looked at bootloader.conf once again and created a new boot.config file. The system does definitely see the file because it echos the commands. The boot process breaks down immediately as if what is on /dev/ad0s1b is not seen as a boot sector. Here is a screen capture from the system so you can see both the boot.config file and the system's response. þÿ/boot.config: -P verbose_loading="YES" # Set to YES for verbose loader output autoboot_delay="-1" # Delay in seconds before autobooting, # set to -1 if you don't want user to be # allowed to interrupt autoboot process and comconsole_speed="9600" # Set the current serial console speed console="vidconsole,comconsole" # A comma separated list of console(s) currdev="disk1s1b" # Set the current device root_disk_unit="0" # Force the root disk unit number rootdev="disk1s1b" # Set the root filesystem System Response FreeBSD/i386 boot Default: 0:ad(0,a)to boot: 'And there we die. There is a valid boot sector at Default: 0:ad(0,a) but there is also now valid boot code at 0:ad(0,b) which is what I am trying to force with boot.config. If one does fdisk on a partition that has had mfsboot.img sprayed on it, fdisk shows the first 3 partitions as being unused while Partition 4 has a type of 165 or standard FreeBSD. I think I am calling the bootloader wrong since the very same mfsboot image works properly when applied to /dev/ad0. The only difference is that one now has the same partition configuration on /dev/ad0 instead of ad0s1b Martin McCormick