From owner-freebsd-current@FreeBSD.ORG Mon Sep 8 22:07:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4951F16A4BF for ; Mon, 8 Sep 2003 22:07:04 -0700 (PDT) Received: from s1.stradamotorsports.com (ip30.gte4.rb1.bel.nwlink.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BFA343FEC for ; Mon, 8 Sep 2003 22:07:02 -0700 (PDT) (envelope-from jcw@highperformance.net) Received: from s1.stradamotorsports.com (s1.stradamotorsports.com [192.168.1.201])h8956wOe080306 for ; Mon, 8 Sep 2003 22:06:58 -0700 (PDT) (envelope-from jcw@highperformance.net) Date: Mon, 8 Sep 2003 22:06:58 -0700 (PDT) From: "Jason C. Wells" X-X-Sender: jcw@s1.stradamotorsports.com To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.0 required=5.0 tests=USER_AGENT_PINE version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: partition C doesn't start at 0! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 05:07:04 -0000 I recently did an install of 5.1R. I sliced the disk into three slices. A 128 MB slice for ad0s1 on /, a 64MB slice for as0s2 on an alternate /, and the remainder for ad0s3 for /var and /usr. So I have ad0s1,s2, and s3. I can boot from ad0s1. I am still monkeying around with the ad0s2 slice. In the process of trying to get ad0s2 to boot with a PicoBSD-esque system, I looked at my disklabel and I saw all kinds of scary messages. # bsdlabel ad0s1 partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition C may cause problems for standard system utilities. bsdlabel ad0s2 reports the same errors The disklabel is as was created by sysinstall. Funny, the error about not starting at zero. The compatibility mode slicing forces the 63 sector offset. This is hardly an error. 1 - I am wondering, do these errors is prevent my second slice (ad0s2) from booting? 2 - The first slice (ad0s1) boots, so what's with the scary messages? I should mention that I have an old BIOS that has the 1023 cylinder limit. With both of my root slices under 200MB, I am well with this limit. Later, Jason C. Wells