All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Hugo Mills <hugo@carfax.org.uk>,
	Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or newer?
Date: Wed, 23 Apr 2014 15:50:18 -0700	[thread overview]
Message-ID: <20140423225018.GL26949@merlins.org> (raw)
In-Reply-To: <20140423224303.GB2391@carfax.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

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/  

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 308 bytes --]

  reply	other threads:[~2014-04-23 22:50 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров
2014-04-23 18:33 ` Swâmi Petaramesh
2014-04-23 18:54 ` Marc MERLIN
2014-04-23 19:02   ` Hugo Mills
2014-04-23 19:06   ` Пламен Петров
2014-04-23 19:15     ` Marc MERLIN
2014-04-23 19:37       ` Пламен Петров
2014-04-23 20:58         ` Marc MERLIN
2014-04-23 21:54           ` Пламен Петров
2014-04-23 22:03             ` Marc MERLIN
2014-04-23 22:20               ` Пламен Петров
2014-04-23 22:40                 ` Chris Murphy
2014-04-23 22:43                   ` Hugo Mills
2014-04-23 22:50                     ` Marc MERLIN [this message]
2014-04-23 22:53                       ` Hugo Mills
2014-04-23 22:41               ` Hugo Mills
2014-04-24 12:34           ` Chris Mason
2014-04-24 12:36             ` Chris Mason
2014-04-24 17:08               ` Пламен Петров
2014-04-24 17:19       ` Пламен Петров
2014-04-24 17:33         ` Marc MERLIN
2014-04-24 17:44           ` Пламен Петров
2014-04-24 18:51           ` Пламен Петров
2014-04-24 19:31             ` Marc MERLIN
2014-04-24 20:26               ` Пламен Петров
2014-04-24 21:47                 ` Chris Murphy
2014-04-24 21:06             ` Chris Murphy
2014-04-24 21:23               ` Пламен Петров
     [not found]               ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info>
2014-04-24 23:07                 ` Marc MERLIN
2014-04-25  0:04                   ` Chris Murphy
2014-04-25  0:08                     ` Chris Mason
2014-04-25  5:04                       ` Пламен Петров
2014-04-25  7:02                       ` Duncan
2014-04-25  5:03                     ` Пламен Петров
2014-04-23 19:06 ` Kai Krakow
2014-04-23 20:25   ` Calvin Walton
2014-04-23 22:34   ` Chris Murphy
2014-04-24  3:23 ` Chris Murphy
2014-04-24  6:27   ` Fajar A. Nugraha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140423225018.GL26949@merlins.org \
    --to=marc@merlins.org \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.