From owner-freebsd-current@FreeBSD.ORG Sun Dec 7 11:09:35 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED0801065670 for ; Sun, 7 Dec 2008 11:09:35 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id 7210D8FC18 for ; Sun, 7 Dec 2008 11:09:35 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1086082fkk.11 for ; Sun, 07 Dec 2008 03:09:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=mO5gMikeLQLmWpNdI5Pz307UoIoRAOCrblBtgRG9Bpc=; b=AjQvar2tYKhyCGdFCQkAGx284Si/8deWAeJvTC1g2DzkN5UFw5kU7QBch0Y97M2GRx 4VksCWFFVAK7yO2BzXQBTnn3RQo3ShClqZ6v3umvblRUz9rd+oY7VEGmmWtIUMZ947pO VRdKhNC0S27yQZGME+NDXE2hZHOV+jnd8KyUw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qo3+rUghik9Q2jt9G2RosjHZPpgGqtfsz7tiR5bVqJy430STidRCyiVs68ty4l0dly lvkhv7vqo3nJRMfE6pWhwfx32VTDi37cb+KF8p3rolMDTysGF49I/uPSrjjZBdoUsHQO S1Bu9tnhUhVrV9eOxGG2v/7906FGlhLWPHGK0= Received: by 10.180.253.12 with SMTP id a12mr776136bki.147.1228646913361; Sun, 07 Dec 2008 02:48:33 -0800 (PST) Received: by 10.180.236.13 with HTTP; Sun, 7 Dec 2008 02:48:33 -0800 (PST) Message-ID: <70e8236f0812070248p3341c24aob024995be08b962a@mail.gmail.com> Date: Sun, 7 Dec 2008 10:48:33 +0000 From: "Joao Barros" To: "Doug Rabson" In-Reply-To: <66BF33BA-EC11-446F-9DE7-15395F293FE2@rabson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200812070319.18461.ken@mthelicon.com> <66BF33BA-EC11-446F-9DE7-15395F293FE2@rabson.org> Cc: hackers@freebsd.org, Pegasus Mc Cleaft , current@freebsd.org Subject: Re: Problems with zfsboot loader if raidz present on any drive 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: Sun, 07 Dec 2008 11:09:36 -0000 On Sun, Dec 7, 2008 at 9:22 AM, Doug Rabson wrote: > > On 7 Dec 2008, at 03:19, Pegasus Mc Cleaft wrote: > >> Hello Hackers, >> >> Recently and friend and I have been trying to get the new >> gptzfsboot working >> on our machines and ran into a interesting problem. >> >> Initially I was building the world without the environment variable >> LOADER_ZFS_SUPPORT=YES in the /etc/make.conf and this, of course, didnt >> work >> very well. Every time the machine booted, it would throw 2 lines after the >> pin-wheel and then reboot. I couldent read what the lines were it went so >> fast. >> >> My friend had a bit more luck and got his machine working OK with a >> single >> drive and later a mirror drive added. >> >> I added the environment variable and rebuilt everything and >> installed. This >> time, I could see the bios drives and a further 2 lines of ZFS something >> and a >> reboot... >> >> No matter what I tried, I couldent get the machine to boot up to a >> point >> where I could try and fix the problem, so I started pulling devices out >> and >> found the following: If there is a raidz pool on any drive (not >> necessarily >> the one that you are trying to boot from) the loader dies and reboots the >> machine. My friend, as an experiment created 3 gpt partitions (in addition >> to >> the single partition that he had been previously booted from) on his >> single >> drive and made a raidz pool for testing. His machine showed the same >> condition >> as mine, however he was able to capture the message before the machine >> rebooted: >> >> >> ZFS: can only boot from disk or mirror vdevs >> >> ZFS: inconsistent nvlist contents > > The zfsboot code in current doesn't support raidz or raidz2. I have been > working on adding that support but its not ready yet. The code works in my > test harness but crashes instantly when I put it in the boot code :(. I > should have time to finish debugging it soon. > After installing my system yesterday on a single disk with gptzfsboot, I connected my old raidz and I only got cyclic reboots. I knew instantly it had something to do with the raidz. Disconnecting 2 out of the 4 disks of the raidz would allow the system to boot as the raidz would not present itself as ONLINE. As a temporary workaround for this problem I disabled those 2 disks on the BIOS, the system boots fine and the kernel is able to find them later. Doug, when you feel comfortable to share any patches, I'm willing to test :-) -- Joao Barros