From owner-freebsd-geom@FreeBSD.ORG Thu Feb 26 01:44:10 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1053C106566B for ; Thu, 26 Feb 2009 01:44:10 +0000 (UTC) (envelope-from server@apz.fi) Received: from basestar1.apz.fi (basestar1.apz.fi [62.237.4.40]) by mx1.freebsd.org (Postfix) with ESMTP id BD2668FC12 for ; Thu, 26 Feb 2009 01:44:09 +0000 (UTC) (envelope-from server@apz.fi) Received: from localhost (localhost [127.0.0.1]) by basestar1.apz.fi (Postfix) with ESMTP id 138FA272C2A for ; Thu, 26 Feb 2009 03:28:48 +0200 (EET) X-Virus-Scanned: by amavisd-new at basestar1. Got none of those nasty buggers! Received: from basestar1.apz.fi ([127.0.0.1]) by localhost (basestar1.apz.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2oLhYkEuv+L for ; Thu, 26 Feb 2009 03:28:45 +0200 (EET) Received: from [214.1.1.1] (dsl-kvlbrasgw2-fe19df00-212.dhcp.inet.fi [80.223.25.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by basestar1.apz.fi (Postfix) with ESMTPSA id A1DF6272C27 for ; Thu, 26 Feb 2009 03:28:45 +0200 (EET) Message-ID: <49A5F04C.1060302@apz.fi> Date: Thu, 26 Feb 2009 03:28:44 +0200 From: =?ISO-8859-1?Q?Ari_Sovij=E4rvi?= User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: GEOM_ELI with device crypto makes root unmountable X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 01:44:10 -0000 Hi again! I managed to debug the problem a bit further and it'd seem it's not GEOM_ELI, but the 'device crypto'-line that causes the problem. Apparently the same problem exists in other platforms aswell; I found a post about identical problem in PowerPC. Anyway, false alarm, sorry :) -- Ari Sovijärvi