From owner-freebsd-fs@FreeBSD.ORG Sun Mar 10 06:30:50 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DBC313FE for ; Sun, 10 Mar 2013 06:30:50 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id B2DF4EAC for ; Sun, 10 Mar 2013 06:30:50 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id bn7so3643220ieb.11 for ; Sat, 09 Mar 2013 22:30:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PPfhhwj4qBZdpZY65kPMNJPcfF5HJlBWcYg3l9WdqZ4=; b=O7xsxN2Anse9VIrq66HDC3SKK345gu65+CxW7RkMKkmIPWSAaP28B5r0MHlh1Yitjr AU9OhQa4CRLl6LkggD8E7MMNIobcZK7FyOATtn5fgVZ6bNOggUgCS0eBjRBAmbkeeuhk g0aDmpchYgOmhZHsn4xO4p1ircledgxx8kxH1CzDRom1rOJZ7JUYEtBfkK0QX66T7Vb2 NIGVNJguBZpB8v1i88Za6lJe3Oxo/hTTWDXifCQtBmvILpikUGEkd4QsmcjAFkbfcDuC CD9d+Eny0Kob9kz/CbasY7wXZr3lOzt10gaNCw3eOQXDZ8xm5cozEu2MNISpVzr2fCUg yARg== MIME-Version: 1.0 X-Received: by 10.42.150.131 with SMTP id a3mr5691655icw.8.1362897050476; Sat, 09 Mar 2013 22:30:50 -0800 (PST) Sender: jdavidlists@gmail.com Received: by 10.42.153.133 with HTTP; Sat, 9 Mar 2013 22:30:50 -0800 (PST) In-Reply-To: References: <513C1629.50501@caltel.com> Date: Sun, 10 Mar 2013 01:30:50 -0500 X-Google-Sender-Auth: 7GB0uRqxB3vUfBQTUhypSAnV5hU Message-ID: Subject: Re: Aligning MBR for ZFS boot help From: J David To: Cody Ritts Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 06:30:50 -0000 Just to check myself, I ran this real quick on a virstor: # truncate -s 1G deleteme # mdconfig -a -t vnode -f deleteme md0 # gvirstor label -s 62522712k fakessd md0 Resizing virtual size to be a multiple of chunk size. New virtual size: 61056 MB Resizing virtual size to fit virstor structures. New virtual size: 61184 MB (32 new chunks) # gpart create -s gpt /dev/virstor/fakessd virstor/fakessd created # gpart add -t freebsd-boot -b 34 -s 128 /dev/virstor/fakessd virstor/fakessdp1 added # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 /dev/virstor/fakessd bootcode written to virstor/fakessd # gpart add -b 2048 -s 51G -l zroot -t freebsd-zfs /dev/virstor/fakessd virstor/fakessdp2 added # gpart add -t freebsd-swap /dev/virstor/fakessd # no -s = use all space left virstor/fakessdp3 added # gpart show /dev/virstor/fakessd => 34 125304765 virstor/fakessd GPT (59G) 34 128 1 freebsd-boot (64k) 162 1886 - free - (943k) 2048 106954752 2 freebsd-zfs (51G) 106956800 18347999 3 freebsd-swap (8.8G) # zpool create zroot /dev/gpt/zroot # zpool status pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 gpt/zroot ONLINE 0 0 0 errors: No known data errors I won't have much luck booting a virstor to test this :) but it sure looks pretty, so hopefully it will work for you.