On Wed, Apr 23, 2014 at 11:43:03PM +0100, Hugo Mills wrote:
> On Wed, Apr 23, 2014 at 04:40:33PM -0600, Chris Murphy wrote:
> > The screen shot provided makes it clear that one of the following kernel parameters is incorrect:
> > 
> > > root=/dev/mapper/cryptroot
> > 
> > > rootflags=subvol=root
> > 
> > So either the dmcrypt volume hasn't been opened, thus isn't available; or rootfs isn't on a subvolume named root found at the top level of the file system. So I'd say this isn't a btrfs problem, rather it's due to some earlier misconfiguration that's preventing rootfs from being mounted.
> 
>    You'll need an initrd to run cryptsetup (or whatever) to collect a
> passphrase and decrypt the volume before you try to mount it. This
> sounds like a case for an initrd again.

I think you are confused, that's my config I pasted as an example.
He does not use dmcrypt in his example.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/