From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 17:10:01 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 116E71065672 for ; Mon, 1 Jun 2009 17:10:01 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Received: from mail.yellowspace.net (mail.yellowspace.net [80.190.200.164]) by mx1.freebsd.org (Postfix) with ESMTP id 9234F8FC15 for ; Mon, 1 Jun 2009 17:10:00 +0000 (UTC) (envelope-from lopez.on.the.lists@yellowspace.net) Received: from [192.168.178.21] ([85.181.128.36]) (AUTH: CRAM-MD5 lopez.on.the.lists@yellowspace.net, TLS: TLSv1/SSLv3, 128bits, AES128-SHA) by mail.yellowspace.net with esmtp; Mon, 01 Jun 2009 19:09:56 +0200 id 00495B26.000000004A240B64.00010E5C Message-Id: From: Lorenzo Perone To: Adam McDougall In-Reply-To: <20090531071759.GA35763@egr.msu.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 1 Jun 2009 19:09:55 +0200 References: <29579856-69F7-4CDC-A52A-B414A40180ED@yellowspace.net> <4A1B0B4F.1020106@h3q.com> <18972.5870.795005.186542@already.dhcp.gene.com> <4A1C18CC.7080902@icyb.net.ua> <18972.7173.216763.407615@already.dhcp.gene.com> <63548432-B73D-4A08-BA99-FEF5BCC1028A@yellowspace.net> <20090531071759.GA35763@egr.msu.edu> X-Mailer: Apple Mail (2.930.3) Cc: Mickael MAILLOT , FreeBSD Stable Mailing List Subject: Re: ZFS booting without partitions (was: ZFS boot on zfs mirror) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 17:10:01 -0000 On 31.05.2009, at 09:18, Adam McDougall wrote: > I encountered the same symptoms today on both a 32bit and 64bit > brand new install using gptzfsboot. It works for me when I use > a copy of loader from an 8-current box with zfs support compiled in. > I haven't looked into it much yet but it might help you. If you > want, you can try the loader I am using from: > http://www.egr.msu.edu/~mcdouga9/loader Hi, thanx a lot for this hint. Meanwhile, I was almost giving up, and had a try with ZFS on Root with GPT partitioning, using gptzfsboot as the bootloader, a UFS root partition as boot partition (gmirrored to both disks), and the rest (inclusive of a zvol for swap!) on ZFS. This worked perfectly on the first try. (if anyone is interested, I can post my commented command series for that, but it's just a mix of the available tutorials on the web..). I'll be glad do give the zfs-only solution a new try. Had the same impression, that the loader was involved in the problem, but had no env at hand to build a -CURRENT right away... (I did, in fact, repeat the dd-steps a zfsboot bootloader from a recent 8- snapshot iso... with the results being the same as before...). Sidenote: I encountered a few panics when using rsync with the HAX flags enabled (rsync -avxHAX from UFS to ZFS). I'll try to figure out which one of the flags caused it... (Hard links, ACLs, or eXtended attributes..). Never had even the slightest problem with rsync -avx. Thanx for posting me your loader, I'll try with this tomorrow night! (any hint, btw, on why the one in -STABLE seems to be broken, or whether it has actually been fixed by now?) Regards, Lorenzo > (...) > >> 2009/5/28 Lorenzo Perone: >>> Hi, >>> >>> I tried hard... but without success ;( >>> >>> the result is, when choosing the disk with the zfs boot >>> sectors in it (in my case F5, which goes to ad6), the kernel >>> is not found. the console shows: >>> >>> forth not found >>> definitions not found >>> only not found >>> (the above repeated several times) >>> >>> can't load 'kernel' >>> >>> and I get thrown to the loader prompt. >>> lsdev does not show any ZFS devices. >>> >>> (...)