From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 17:04:47 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68D1416A4CE for ; Fri, 22 Apr 2005 17:04:47 +0000 (GMT) Received: from jbhosting.de (mail.jbhosting.de [80.190.201.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2823543D41 for ; Fri, 22 Apr 2005 17:04:46 +0000 (GMT) (envelope-from jonas@schiebtsich.net) Received: (qmail 60234 invoked by uid 545); 22 Apr 2005 17:04:42 -0000 Received: from unknown (HELO sc-ws3.setcom.de) (jonsonn@jbhosting.de@213.155.74.230) by mx010.jbhosting.de with (RC4-MD5 encrypted) SMTP; 22 Apr 2005 17:04:42 -0000 From: jonas Organization: schiebtsich.net To: freebsd-questions@freebsd.org Date: Fri, 22 Apr 2005 19:04:06 +0200 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504221904.06602.jonas@schiebtsich.net> Subject: how to mark a slice bootable using command line X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 17:04:47 -0000 Hi again questions list, I'm running into trouble installing a FreeBSD system from script using a custom FreeSBIE (sysutils/freesbie). I'm using `fdisk -f configfile /dev/da0` to partition my da0 disk into four even-sized slices, `boot0cfg -B /dev/da0` to install the bootmanager to da0, `disklabel -R /dev/da0s$c protofile` to create partitions (which is called four times with $c being 1-4), `newfs -O2 -U /dev/da0s$c$p` to create filesystems (where $p is a, d and e - /tmp will be a memory disk, there is no -U for a) and finally untar the OS onto the new filesystems. Everything goes fine, except, I cannot boot from any slice other then the first (F1 entry in bootman). Any other choice will simply have the speaker beep. Obviously the slices are not marked bootable. Now if I launch sysinstall and choose Configure, Fdisk, da0, I can set the bootable flag to those four slices. Obviously, in sysinstall this is somehow linked to being the active slice, since it shows an 'A' next to the slice and only one A can be set at a time. So I tried to use `fdisk -a -2` to setting slice 2 bootable, without success. Also tried to set the slice bootable by using the -B switch to disklabel, also, without success. Furthermore I cannot figure out any difference to the output of fdisk and disklabel after using sysinstall, other than my slice of choice if now bootable. So... how can I set this bootable flag by using command line tools like fdisk and disklabel without the need of user input. Sadly the handbook refers only to sysinstall... Thanks in advance for any pointers, -- br. j.