From owner-freebsd-current@FreeBSD.ORG Sat Oct 19 15:34:50 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 15898731 for ; Sat, 19 Oct 2013 15:34:50 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id E6241205D for ; Sat, 19 Oct 2013 15:34:49 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id AB62D40558 for ; Sat, 19 Oct 2013 15:34:48 +0000 (UTC) Message-ID: <5262A69D.5070601@allanjude.com> Date: Sat, 19 Oct 2013 11:34:53 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 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> <5262A5D0.3050604@bridgenet.se> In-Reply-To: <5262A5D0.3050604@bridgenet.se> Content-Type: text/plain; charset=ISO-8859-1 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:34:50 -0000 On 2013-10-19 11:31, Johan Broman wrote: > > > 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 > _______________________________________________ > 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" Ahh yes, you have to press 'page-down' to scroll the msgbox. I tried to add a scrollbar but turns out that is not possible. The only indication that there is more message to read, is a small 'xx%' in the bottom right. We might have to look at breaking that output up or something. -- Allan Jude