From owner-freebsd-current@FreeBSD.ORG Sat Oct 19 15:31:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EFC2A265 for ; Sat, 19 Oct 2013 15:31:37 +0000 (UTC) (envelope-from johan@bridgenet.se) Received: from smtp-gw11.han.skanova.net (smtp-gw11.han.skanova.net [81.236.55.20]) by mx1.freebsd.org (Postfix) with ESMTP id 7CE242FFF for ; Sat, 19 Oct 2013 15:31:36 +0000 (UTC) Received-SPF: pass (smtp-gw11.han.skanova.net: domain bridgenet.se designates 212.181.212.146 as permitted sender) identity=mailfrom; receiver=smtp-gw11.han.skanova.net; client_ip=212.181.212.146; envelope-from=johan@bridgenet.se; helo=mail.bridgenet.se; Received: from mail.bridgenet.se (212.181.212.146) by smtp-gw11.han.skanova.net (8.5.133) id 525514D7004E7E09 for freebsd-current@freebsd.org; Sat, 19 Oct 2013 17:31:35 +0200 Received: from mail.bridgenet.se (unknown [10.0.0.5]) by mail.bridgenet.se (Postfix) with ESMTP id 9168E17E8E for ; Sat, 19 Oct 2013 17:31:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bridgenet.se; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:to:mime-version:user-agent:from:from :date:date:message-id; s=dkim; t=1382196693; x=1383060694; bh=Ea N++hv4wzERiP7IcWS+mVSx49oTxkEly7kNOOAmMP4=; b=Smc0kRz7wKwW255dhf ABvowFE14p4+ggQkOjuplVFWV+0Xa4RmhEHZanfaj3ebN4YJYvao6TTj+LLx2qGt j/YXV17DF01LQVaxkHX22rAcGrFGizJoXgu4FxSZCxofMQTpD3y6h1VQF6O9GZLx RoPw2FXcDgghESTEOtF6yXAfk= X-Virus-Scanned: amavisd-new at mail.bridgenet.se Received: from mail.bridgenet.se ([10.0.0.5]) by mail.bridgenet.se (mail.bridgenet.se [10.0.0.5]) (amavisd-new, port 10024) with ESMTP id dxfzUM1-ANI0 for ; Sat, 19 Oct 2013 17:31:33 +0200 (CEST) Received: from dhcp-208-143.arn.redhat.com (unknown [192.168.0.129]) by mail.bridgenet.se (Postfix) with ESMTPSA id 633D517E82 for ; Sat, 19 Oct 2013 17:31:32 +0200 (CEST) Message-ID: <5262A5D0.3050604@bridgenet.se> Date: Sat, 19 Oct 2013 17:31:28 +0200 From: Johan Broman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52629DA7.7090103@bridgenet.se> <5262A3EE.4050600@allanjude.com> In-Reply-To: <5262A3EE.4050600@allanjude.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 19 Oct 2013 15:31:38 -0000 On 19/10/13 17:23, Allan Jude wrote: > On 2013-10-19 10:56, Johan Broman wrote: >> Hi! >> >> Just tested the root-on-ZFS install option using FreeBSD 10 beta 1. I >> have 4 SATA drives in my server. I select all four of them in a RAIDZ1 >> setup. I hit enter to continue the installation and the zpool is >> created, but I'm then returned to the zpool selection screen again. It >> turned out that two of the drives had previously been used in a >> (Linux) software mirror setup and because of this they got activated >> in /dev/raid/r0. Because of this I ended up in an endless bsdinstall >> loop. >> >> Removing the raid device using the graid command resolved the situation. >> >> Now maybe this is working as designed, but there was no warning/alert >> to the fact that the devices couldn't be used. Perhaps a warning >> should be rasied in this situation? >> >> Thanks for all the great work on the new installer, really looking >> forward to FreeBSD 10! >> >> Cheers >> Johan >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > Errors like that normally generate a msgbox dialog with the error output > from whichever command failed. I'll have to dig into it and see where > that problem is. I've seen other people have problems creating ZFS > arrays after graid, but in that case it was an incomplete graid label > causing a device to be locked but not appear in the graid status output. > Ah ok. A msgbox did appear but the drives that had the problem (ada2 and ada3) wasn't visible in the output. (not sure if the box itself has a size limit or maybe I was just unable to scroll down and see the errors?). The only visible output was that it was able to create labels on ada0 and ada1. /Johan