From owner-freebsd-current@FreeBSD.ORG Wed Feb 17 18:40:48 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85CD8106566B for ; Wed, 17 Feb 2010 18:40:48 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFF88FC20 for ; Wed, 17 Feb 2010 18:40:48 +0000 (UTC) Received: from feathers.peganest.com (feathers.peganest.com [78.33.110.3]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id o1HIefSr065447; Wed, 17 Feb 2010 18:40:42 GMT (envelope-from ken@mthelicon.com) From: Pegasus Mc Cleaft Organization: Feathers To: freebsd-current@freebsd.org Date: Wed, 17 Feb 2010 18:40:41 +0000 User-Agent: KMail/1.12.4 (FreeBSD/9.0-CURRENT; KDE/4.3.5; amd64; ; ) References: <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <790a9fff1002161842g17de8ecfvf2cfa8c77f03c32@mail.gmail.com> <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com> In-Reply-To: <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002171840.41088.ken@mthelicon.com> X-Spam-Status: No, score=1.9 required=5.0 tests=AWL, BAYES_00, FH_DATE_PAST_20XX autolearn=no version=3.2.5 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hercules.mthelicon.com Cc: Chris , Scot Hetzel Subject: Re: Seeing the dreaded "ZFS: i/o error - all block copies unavailable" on 9.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 17 Feb 2010 18:40:48 -0000 Hello Chris, Scott & Current I use gptzfsboot on my AMD64 (current) machine all the time and also on my laptop. I am not sure if this will cause the problem you are seeing but I know I ran into a lot of trouble depending on what type of pool I was creating. I believe this is correct, and if I am not than I apologise in advance, but.... If you are trying to boot off a linear type pool (A single disk or a mirror) your bootable filing system has to be a zfs filing system beneath the root pool (IE: zroot/boot). If you are trying to boot off a zraid pool, your bootable filing system must be the root filing system of the pool (IE: zroot) You must also include the appropriate declaration in the /boot/loader.conf file: (for a zraid pool) zfs_load="YES" vfs.root.mountfrom="zfs:zpool" (for a linear type) zfs_load="YES" vfs.root.mountfrom="zfs:zpool/root" If I try any other method, zboot explodes in a myriad of different ways. I hope this helps Peg On Wednesday 17 February 2010 02:49:56 Chris wrote: > Scot, > > I did, as part of step 7 in section 1: > > 7. Create ZFS Pool zroot > > Fixit# mkdir /boot/zfs > Fixit# zpool create zroot /dev/gpt/disk0 > Fixit# zpool set bootfs=zroot zroot