linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Mitchell <george@chinilu.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Scan not being performed properly on boot
Date: Sun, 03 Aug 2014 21:22:48 -0700	[thread overview]
Message-ID: <53DF0A98.2010907@chinilu.com> (raw)
In-Reply-To: <30613326.hzdtJptJHK@xev>

On 08/03/2014 09:14 PM, Russell Coker wrote:
> On Sun, 3 Aug 2014 21:00:19 George Mitchell wrote:
>>> But just changing your boot configuration to use /dev/sdx is probably the
>>> best option.
>> Assuming you are booting with grub2, you will need to use /dev/sdx in
>> the grub2 configuration file.  This is known issue with grub2. Example
>> from my script:
> That's not a GRUB issue it's an initrd issue.  GRUB just passes text to the
> kernel.  "cat /proc/cmdline" will show you what GRUB sent to the kernel, the
> programs in the initrd read /proc/cmdline and then do what they think is
> appropriate.
>
>> ----------------------------------------------------------------------------
>> ---------- echo    'Loading Linux desktop ...'
>> linux   /vmlinuz-desktop root=/dev/sda7 ro splash quiet
>> echo    'Loading initial ramdisk ...'
>> initrd  /initrd-desktop.img
Russell, it fixed the problem for me, that's all I know.  That's why I 
am suggesting it.

  reply	other threads:[~2014-08-04  4:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  3:02 Scan not being performed properly on boot Peter Roberts
2014-08-04  3:31 ` Russell Coker
2014-08-04  4:00   ` George Mitchell
2014-08-04  4:14     ` Russell Coker
2014-08-04  4:22       ` George Mitchell [this message]
2014-08-04  4:34       ` George Mitchell
2014-08-04  5:01         ` Russell Coker
2014-08-04  5:23     ` Duncan
2014-08-04  9:36   ` Chris Samuel
2014-08-04 15:00   ` Peter Roberts

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=53DF0A98.2010907@chinilu.com \
    --to=george@chinilu.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).