From: Peter Roberts <me@peter-r.co.uk>
To: russell@coker.com.au
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Scan not being performed properly on boot
Date: Mon, 04 Aug 2014 16:00:17 +0100 [thread overview]
Message-ID: <53DFA001.7020002@peter-r.co.uk> (raw)
In-Reply-To: <1704788.vV3kpDkpOK@xev>
On 04/08/2014 04:31, Russell Coker wrote:
> 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.
Here a screenshot http://imgur.com/8pQgG8g
Making changes to /etc/fstab didn't seem to work and nor did manually
adding device=/dev/sda1,device... in the GRUB config itself. What has
fixed the problem though seems pretty horrible it to specify
root=/dev/sda1 instead of UUID=....
> 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.
I'll file a bug report but I'm not sure whether this is a GRUB or an
initrd / initramfs problem. Getting a persistent fix required a bodge in
/etc/grub.d/10-linux
As for support, I don't think it is considered stable in 14.04 but I
haven't had to do anything special to use it and used to official
installer to get where I am (converting the single disk FS to a RAID1
after).
In any case, thanks for the help :)
prev parent reply other threads:[~2014-08-04 15:00 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
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 [this message]
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=53DFA001.7020002@peter-r.co.uk \
--to=me@peter-r.co.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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.