From owner-freebsd-current@FreeBSD.ORG Sat Oct 19 15:43:30 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 AB50CC48 for ; Sat, 19 Oct 2013 15:43:30 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7550220BC for ; Sat, 19 Oct 2013 15:43:30 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r9JFhJhE012653 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 19 Oct 2013 10:43:19 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Sat, 19 Oct 2013 10:43:18 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOzOHuoyZqOu2cyEmJYHyn2Q5Miw== Date: Sat, 19 Oct 2013 15:43:18 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC7E9DE@LTCFISWMSGMB21.FNFIS.com> References: <52629DA7.7090103@bridgenet.se> <5262A3EE.4050600@allanjude.com> <5262A5D0.3050604@bridgenet.se> <5262A69D.5070601@allanjude.com> In-Reply-To: <5262A69D.5070601@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <394EC62C45E45248A266C82FB398A468@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-18_03:2013-10-18,2013-10-18,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" 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:43:30 -0000 On Oct 19, 2013, at 8:34 AM, Allan Jude wrote: > On 2013-10-19 11:31, Johan Broman wrote: >>=20 >>=20 >> On 19/10/13 17:23, Allan Jude wrote: >>> On 2013-10-19 10:56, Johan Broman wrote: >>>> Hi! >>>>=20 >>>> 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. >>>>=20 >>>> Removing the raid device using the graid command resolved the >>>> situation. >>>>=20 >>>> 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? >>>>=20 >>>> Thanks for all the great work on the new installer, really looking >>>> forward to FreeBSD 10! >>>>=20 >>>> 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. >>>=20 >>=20 >> 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. >>=20 >> /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. >=20 > 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. >=20 The only reason for a msgbox widget to scroll is if it is displayed at maximum height or width of the screen and it *still* has more data to display than can be presented at-once. If... however... the msgbox widget is *not* full-height or full-width yet... it is requiring you to scroll -- then we've found a bug. Can we get a screen shot? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.