From owner-freebsd-questions@FreeBSD.ORG Tue Feb 19 21:36:58 2008 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 4036F16A475 for ; Tue, 19 Feb 2008 21:36:58 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id DF34613C465 for ; Tue, 19 Feb 2008 21:36:57 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id m1JLWs0B047303; Tue, 19 Feb 2008 16:32:54 -0500 (EST) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id m1JLWs2n047302; Tue, 19 Feb 2008 16:32:54 -0500 (EST) (envelope-from jerrymc) Date: Tue, 19 Feb 2008 16:32:54 -0500 From: Jerry McAllister To: Jeff Gold Message-ID: <20080219213254.GB47232@gizmo.acns.msu.edu> References: <4bded9640802191245q20832a83j31723763ab21a940@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4bded9640802191245q20832a83j31723763ab21a940@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: diskLabelCommit fails within a sysinstall script? 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: Tue, 19 Feb 2008 21:36:58 -0000 On Tue, Feb 19, 2008 at 03:45:25PM -0500, Jeff Gold wrote: > I am attempting to partition a disk non-interactively using > sysinstall, but I don't seem to be getting this right. I use the > following script on an 80G drive: > > debug=true > ufs=/6.2-RELEASE > mediaSetUFS > disk=ad0 > partition=all > bootManager=boot > diskPartitionEditor > diskPartitionWrite > > ad0s1a=ufs 1048576 / > ad0s1b=swap 4194304 none > ad0s1d=ufs 2097152 /tmp > ad0s1e=ufs 16777216 /usr > ad0s1f=ufs 0 /var 1 > diskLabelEditor > diskLabelCommit > shutdown > > This runs without any evident error, but the relevant contents of /dev > change from just ad0 to ad0, ad0s1 and ad0s1c. The first two make > sense but ad0s1c is the only device I didn't request. None of the > ones I did seem to appear. A boot loader does seem to have been > installed but when I select "F1" for FreeBSD it says "Invalid > partition" and complains that there's "No /boot/loader" to be found. > So I guess the first stage got installed but not the next one? > > Can anyone explain why this doesn't work? I skipped the 'c' partition > because that's what sysinstall wants to do when I run it > interactively, but renaming the devices to include the 'c' makes no > difference. There is still an s1c and nothing else. Also, I tried > the syntax in the man page (ad0s1-1 instead of ad0s1a) but that -- > perversely -- gives me a bunch of errors about being unable to mount > partitions with the other style names. I don't know about all you ask, but the 'c' partition should always be there and be set to identify the whole slice eg start at 0 and the size be the size of the slice. The system uses it to identify some internal information about the slice. Sysinstall should handle that correctly just fine. I don't know why you do not get ad0s1a, swap, ad0s1d, etc. Maybe, if you deleted that special 'c' partition, it made the rest of the process screw up. ////jerry > > Jeff > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"