From: Chuck Burns <break19@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: grub-1.99 and btrfs-only
Date: Sat, 05 Nov 2011 21:02:53 -0500 [thread overview]
Message-ID: <1485076.Kk29g2Lexo@funbeast> (raw)
I have a btrfs-only system, using grub2 (1.99), and have /boot on btrfs as
well...
When I first boot, grub first complains it cannot find files, then apparently
successfully finds them, loading the menu..
After I select the option I want, grub again complains of unable to find a file,
and seconds later begins to properly boot..
This is my boot.cfg
---
set timeout=5
insmod gpt
insmod btrfs
set root=(hd0,gpt3)
search --no-floppy --fs-uuid --set a549b032-017c-4a96-ae28-5dffe61cff1d
if loadfont /boot/grub/unifont.pf2; then
set gfxmode=1680x1050
insmod gfxterm
insmod vbe
terminal_output gfxterm
fi
set menu_color_normal=cyan/black
set menu_color_highlight=black/cyan
menuentry "Linux 3.1.0" {
insmod gpt
insmod btrfs
set root=(hd0,gpt3)
search --no-floppy --fs-uuid --set a549b032-017c-4a96-ae28-5dffe61cff1d
linux /boot/bzImage-3.1.0 root=/dev/sda3 rootfstype=btrfs
initrd /boot/initframfs-3.1.0
set gfxpayload=keep
}
set default=0
---
These are my current subvolumes:
# btrfs sub list /
ID 256 top level 5 path mainroot
ID 257 top level 5 path home
I have sub 256 set as default, and then home is mounted onto mainroot.
I'm assuming that since I have my boot inside that subvolume, that is why
grub, at first, has issues locating the files, but then manages to find it.
My question is this: Is anyone aware of any grub.cfg magic I can use to
specify a specific subvolume to look for /boot/grub ? my plan is to eventually
move boot into it's -own- subvolume, and create more subvolumes for different
distros.
next reply other threads:[~2011-11-06 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 2:02 Chuck Burns [this message]
2011-11-07 21:07 ` grub-1.99 and btrfs-only Phillip Susi
2011-11-07 22:42 ` Arand Nash
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=1485076.Kk29g2Lexo@funbeast \
--to=break19@gmail.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).