On Wed, Apr 23, 2014 at 03:50:18PM -0700, Marc MERLIN wrote: > 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. Ah, OK. Never mind, then. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Computer Science is not about computers, any more than --- astronomy is about telescopes.
Attachment:
signature.asc
Description: Digital signature
