From: Russell Coker <russell@coker.com.au>
To: Peter Roberts <me@peter-r.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Scan not being performed properly on boot
Date: Mon, 04 Aug 2014 13:31:42 +1000 [thread overview]
Message-ID: <1704788.vV3kpDkpOK@xev> (raw)
In-Reply-To: <53DEF7DD.5070002@peter-r.co.uk>
On Mon, 4 Aug 2014 04:02:53 Peter Roberts wrote:
> I've just recently started testing btrfs on my server but after just 24
> hours problems have started. I get booted to a busybox prompt user
> ubuntu 14.04. I have a multi device FS setup and I can't say for sure if
> it managed to boot initially or not but it worked fine in regular usage.
What is GRUB (or your boot loader) giving as parameters to the kernel?
What error messages appear on screen? Sometimes it's helpful to photograph
the screen and put the picture on a web server to help people diagnose the
problem.
> I cannot mount my root with anything other than an explicit /dev/sdx
> reference until I manually run a scan. Then UUID etc all work. I've
That sounds like a problem with the Ubuntu initrd, probably filing an Ubuntu
bug report would be the best thing to do. Is BTRFS supported in that version
of Ubuntu?
But just changing your boot configuration to use /dev/sdx is probably the best
option.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-08-04 3:31 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 [this message]
2014-08-04 4:00 ` George Mitchell
2014-08-04 4:14 ` Russell Coker
2014-08-04 4:22 ` George Mitchell
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=1704788.vV3kpDkpOK@xev \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=me@peter-r.co.uk \
/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).