From owner-freebsd-sysinstall@FreeBSD.ORG Tue Nov 25 20:11:02 2014 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79F9D4DD; Tue, 25 Nov 2014 20:11:02 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D9B8F5B; Tue, 25 Nov 2014 20:11:02 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id h11so2694272wiw.15 for ; Tue, 25 Nov 2014 12:11:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HyuvHF7t7/vPml/jQl+1C7w+ZjkrDPiHrG/tyDN8WCY=; b=zVNiaFbQFG8ttUI6V9OvCENVWU+FuLZPf4R5LKcnHW4jZH5eZuP9t1rMJ2HyUmVy/g LQeut+K4Oujpz1ZXJj4Rrb9of+C+9pblxDCSRQ4RP0NkPv+ulWvF9V+iPX8CyWeWdzLM Dqi+Ol5uy6q5oagsG+4Eglfaz2PrcyU/JBbmXVjN8J22FXz736NbN98RA3bV73L0jsDM i6+p7FWlzhwVgtl0QD3wwZ7alFLrvJV6qtlDNC+us6vzkSnVCfUNCr8VCPRKdYc7p5YQ DC6T6edheD1eqgJFqj52h3YUZws4yYvHZmoTsjzcoB/nEaXss8xVq7H+BgCnFoppDyg3 pldg== MIME-Version: 1.0 X-Received: by 10.180.81.70 with SMTP id y6mr35871758wix.6.1416946260583; Tue, 25 Nov 2014 12:11:00 -0800 (PST) Received: by 10.194.45.199 with HTTP; Tue, 25 Nov 2014 12:11:00 -0800 (PST) In-Reply-To: <5470CFC3.2000806@freebsd.org> References: <546F6D79.9060909@freebsd.org> <5470CFC3.2000806@freebsd.org> Date: Tue, 25 Nov 2014 22:11:00 +0200 Message-ID: Subject: Re: Dangerously dedicated mode with FreeBSD 10.1 From: Rostislav Krasny To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Cc: freebsd-sysinstall@freebsd.org X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 20:11:02 -0000 On Sat, Nov 22, 2014 at 8:02 PM, Nathan Whitehorn wrote: > > On 11/22/14 06:15, Rostislav Krasny wrote: >> >> Unfortunately disk partitioning of bsdinstall(8) isn't precise and >> isn't informative. Disk partitioning by sysinstall(8) was much better >> in this sense. With bsdinstall(8) I don't see how much disk space is >> left unpartitioned and where. Also I don't see where partitions start >> and what are their sizes in LBA units of measurement. By default >> bsdinstall(8) offers one huge partition for the root mount and a few >> hundreds of megabytes for swap partition after the root one. If don't >> like the offered partition sizes and want to create the same >> partitions manually (with slightly different sizes) I can't do it >> because of the precision flaw. Defining the root partitions in GB >> units with a size close to the whole disk size doesn't left any free >> space for the small swap partition. And if I create a swap partition >> before the root one I get an unbootable system. > > > It isn't meant to provide partitioning at the level of detail where you are > specifying the start position in blocks. Why do you need that? If you want > that, gpart at the command line is a much better tool. You can tell > bsdinstall to use previously created partitions, of course, and you can also > specify partition sizes to arbitrary precision. If you want sub-GB > partitioning, specify the size in MB, or KB, or blocks. You are free to do > any of these things. I know that I can specify MB or KB but it doesn't help at all. bsdinstall(8) doesn't show the exact size of the disk. In my case it shows 13 GB, that is a rounded size of 26564832 sectors (26564832 * 512 bytes =~ 12.667GB). It also doesn't show how much space is left free. I wanted to divide all this disk space into one big UFS partition, one 256MB swap partition and left no free space. Partedit of the bsdinstall(8) is useless in this task. >> Another problem with bsdinstall(8) partitioning is an inability of >> using already partitioned disk. This is what I've tried first. In this >> case I was need to define the mount points of the existing partitions. >> It's easy to do (since I have a backup of my previous /etc/fstab) but >> then bsdinstall(8) didn't ask me if I want to re-format those >> partitions. Then the whole installation failed at the beginning of >> base.txz extracting (the first txz package). I'm almost sure it failed >> because it tried to extract the base.txz over existing filesystem of >> my previous FreeBSD 7.4 system. >> > It can use an already partitioned disk, which seems to be your problem here > in fact. Like the partition editor in every other OS, it assumes that if you > just specify the mount point for a partition, you don't want to erase it. > Erasing existing partitions is an extremely unfriendly thing to do. You can > re-initialize it by changing any non-mountpoint property of the partition or > from the command line. Installer should ask the user: does he want to re-format the chosen partition. Without this option the whole installation may fail, like in my case. If those partitions are system and have previous version of FreeBSD or any other OS installed on them, there is a high probability that the user really wants to re-format them. This is the usual behavior of other OS installers.