From owner-freebsd-current@freebsd.org  Wed Jun 13 19:27:36 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E9FB100A04B
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 13 Jun 2018 19:27:36 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org
 [54.200.247.200])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9290275C89
 for <freebsd-current@freebsd.org>; Wed, 13 Jun 2018 19:27:35 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-RoutePath: aGlwcGll
X-MHO-User: d1578089-6f3f-11e8-8837-614b7c574d04
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 67.177.211.60
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [67.177.211.60])
 by outbound1.ore.mailhop.org (Halon) with ESMTPSA
 id d1578089-6f3f-11e8-8837-614b7c574d04;
 Wed, 13 Jun 2018 19:27:32 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w5DJRVRw061245;
 Wed, 13 Jun 2018 13:27:31 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1528918051.12122.70.camel@freebsd.org>
Subject: Re: GELI attach issue from r326073 -> r334996
From: Ian Lepore <ian@freebsd.org>
To: Michael Jung <mikej@mikej.com>, freebsd-current@freebsd.org
Date: Wed, 13 Jun 2018 13:27:31 -0600
In-Reply-To: <1aa4ba2a8313f602bd0b0445987c18ec@mikej.com>
References: <1aa4ba2a8313f602bd0b0445987c18ec@mikej.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2018 19:27:36 -0000

On Wed, 2018-06-13 at 14:29 -0400, Michael Jung wrote:
> Hi!
> 
> I just tried updating current from r326073 -> r334996 and when
> I try 'geli attach' I get the following error:
> 
> # geli attach -p -k mykey.key /dev/gpt/da14
> geli: Missing keyno argument
> #
> 
> If I boot the old kernel GELI attaches just fine.
> 
> I ran into this once before but can not find the thread.  I recall
> it being a bug... with no resolution.
> 
> I mount zfs partitions over GELI - my painful solution was to
> nuke each GPT partition in the zpool, resilver, repeat and
> rinse until everything was non-encrypted and repeat the cycle
> to re-encrypt.  NOT FUN.
> 
> Looking for suggestions to supply additional information to debug
> and resolve.
> 
> dmesg attached from working kernel.
> 
> Thanks!

r333439 added a '-n keyno' parameter to geli attach, but it's supposed
to default to trying all keys if you don't use -n. Is it possible
you're running a newer kernel (or geom_eli module) than your userland
or vice versa?

-- Ian