From owner-freebsd-questions@freebsd.org Sat Nov 12 18:29:35 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C52C6C3E686 for ; Sat, 12 Nov 2016 18:29:35 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96E9111DA for ; Sat, 12 Nov 2016 18:29:35 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-it0-f50.google.com with SMTP id q124so36771277itd.1 for ; Sat, 12 Nov 2016 10:29:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=m3vkHFQo5zrPZH/mC0ILZOsSVOdNFAFsHxC5mGjacoU=; b=bUIGL3PXcOJKVYSnd+fusPyef49wpvrNeyUsOEhGPg6x56RPiTp31NAg0DLAuorS5S SFQ62VHDQZzDQ6eAzwaUm6xXD8zRdpyDv/ccul5hGiSa9DxcZWQRafskdwoSDzewSq47 9IsJ1HiqPwjhEmspdNppmoCcE3ir8VSDsJYUz7uxmy1ZB3X/A4ay0IlgGDHkavTq8vjv aHxu2yYeHrizv8cSBYZt8TJBd2hwB/Ri1mIZ0YPNiMBhJjoT0B2bX+iFh56OxxFS6E+p mE32qSXcDSD/B7xuMNvelm1pefcWX9DHCqFn4mhC4chpAyynFHMbPZClSAWiUGooAkRh WS2Q== X-Gm-Message-State: ABUngvf3TwBDPuk8qDnfxOtTmdRdXU2pSUwR5kbaQTApkfoWuAAK6cSq2v5QoPG5U6h/HQ== X-Received: by 10.107.182.193 with SMTP id g184mr1752759iof.215.1478975369314; Sat, 12 Nov 2016 10:29:29 -0800 (PST) Received: from WorkBox.homestead.org (63-231-162-22.mpls.qwest.net. [63.231.162.22]) by smtp.gmail.com with ESMTPSA id f188sm6088461itb.5.2016.11.12.10.29.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 12 Nov 2016 10:29:28 -0800 (PST) Received: from localhost (WorkBox.homestead.org [local]) by WorkBox.homestead.org (OpenSMTPD) with ESMTPA id 39e4e269; Sat, 12 Nov 2016 12:29:29 -0600 (CST) References: User-agent: mu4e 0.9.16; emacs 25.1.1 From: Brandon J. Wandersee To: Baho Utot Cc: FreeBSD Mailing List Subject: Re: Installing to RaidZ-1 In-reply-to: Date: Sat, 12 Nov 2016 12:29:29 -0600 Message-ID: <861syg5z7a.fsf@WorkBox.homestead.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 18:29:35 -0000 Baho Utot writes: > I want to reinstall my desktop system using a raidz-1 filesystem using > the current installation image for usb drive. Reading the handbook I > find that bsdinstall will not do the installation I want. I am using 4 > 1TB drives and I want to partition to 800GB and install the raidz > there. Can I create a raidz storage pool manually and then use > bsdinstall or will I have to manually install freebsd not using bsdinstall? > > How do I do this? When the installer reaches the disk partitioning stage, it will present you with a list of options, one of which is "Shell." This will drop you to a shell instance where you can manually create your partitions and your zpool. A brief message will appear when you first enter the shell with basic instructions: 1. Mount your custom partitions with /mnt as the root of the system. In this case, use the `-R /mnt` flag when creating the pool so your new root ZFS filesystem is mounted there. 2. Create a custom fstab file and place it in /bsdinstall_etc. I'm not sure how necessary this is if you aren't using fstab to mount any ZFS filesystems; that is, I don't know if the installer will try to stick its own fstab into the installed system if a custom one isn't present. Once you exit the shell the installer will proceed as normal: installing everything to the mounted disks/filesystems, adding users, etc. After the installation, you'll want to choose the option to drop to a shell again in order to edit /boot/loader.conf and /etc/rc.conf, make sure no invalid fstab file has been installed (if necessary) and set the "bootfs=" property on your new pool. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------