Date: Wed, 16 May 2012 05:25:26 -0700 (PDT) From: Sebulon <karli.sjoberg@gmail.com> To: freebsd-geom@freebsd.org Subject: Re: kern/167562: [geli] geli cannot use gpt labels in loader.conf Message-ID: <1337171126458-5708868.post@n5.nabble.com> In-Reply-To: <201205040731.q447V8K3061134@freefall.freebsd.org> References: <201205032237.q43MbHpe040196@freefall.freebsd.org> <201205040731.q447V8K3061134@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I have a related problem. That if I create a .eli provider ontop of a gpt-label, like: # geli init -b -s 4096 -l 128 -e AES-CBC gpt/diskX and then create a zpool using gpt/diskX.eli. When rebooting, it will find (a)daXpX first and prompt me to unlock that one before gpt/diskX, which is the one I want to unlock, because if you unlock (a)daXpX, zpool will resilver onto (a)daXpX instead of the gpt-provider. This is an unwanted behaviour for me, since I wanted zpool to use the logical gpt-provider, in case anything should happen with it=C2=B4s physical representation. Not typ= ing in a password for (a)daXpX three times makes it jump on to the next in line, which is the gpt/diskX, but could be somewhat tiresome if there where, say 10 drives that you needed to unlock and had to type in a wrong (or empty) password 30 times, and the right password 10 times to complete the process. Is there a way to specify only which provider(s) I want to unlock during boot? Using FreeBSD-9.0-RELEASE. Have I missed something? /Sebulon -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-kern-= 167562-geli-geli-cannot-use-gpt-labels-in-loader-conf-tp5684451p5708868.htm= l Sent from the freebsd-geom mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1337171126458-5708868.post>