From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: zaphod@berentweb.com
Subject: Re: grub2 boot root-on-zfs errors
Date: Tue, 24 Sep 2013 20:01:33 +0400 [thread overview]
Message-ID: <20130924200133.0f2a208d@opensuse.site> (raw)
In-Reply-To: <CAPSTskujZ10jENh-mDbKLoEQQXHSk7=z498u1_uiOE87aWWuUA@mail.gmail.com>
В Tue, 24 Sep 2013 18:49:33 +0300
Beeblebrox <zaphod@berentweb.com> пишет:
> Massimo:
> >> should be written as (hd0,gpt2)/mydataset/@/myfolder/myfile.
> Yes, of course - I made the mistake because I was in a hurry writing
> the mail. My current & corrected menu choices are:
>
> menuentry "Test1-BSD-ZFS Direct-Boot" {
> insmod zfs
> search -s -l bsds
> set root='hd0,gpt2'
> kfreebsd (hd0,gpt2)/bsds/@/boot/kernel/kernel
Should not it be (hd0,gpt2)/bsds@/boot/kernel/kernel (notice lack of
slash between "bsds" and "@")?
> kfreebsd_module_elf (hd0,gpt2)/bsds/@/boot/kernel/opensolaris.ko
> kfreebsd_module_elf (hd0,gpt2)/bsds/@/boot/kernel/zfs.ko
> kfreebsd_module (hd0,gpt2)/bsds/@/boot/zfs/zpool.cache
> type=/boot/zfs/zpool.cache
> kfreebsd_loadenv (hd0,gpt2)/bsds/@/boot/device.hints
> set kFreeBSD.vfs.root.mountfrom=zfs:bsds
> }
> menuentry 'Test2-BSD-ZFS ChainloadBTX' {
> insmod zfs
> set root='hd0,gpt2'
> kfreebsd (hd0,gpt2)/bsds/@/boot/loader
> }
>
> Neither of the above entries work. My root zpool is named "bsds" and
> the zfs is the same as the root pool. In other words, zfs list =>
> bsds /
> bsds/usr /usr
> bsds/var /var
> etc...
> I have also tried (unsuccessfully) the above with
> set root='hd0,gpt2'
> kfreebsd /@/boot/loader OR
> kfreebsd (hd0,gpt2)/@/boot/loader OR
> kfreebsd (hd0,gpt2)//@/boot/loader
> All give "unknown filesystem" message. When I drop to grub
> command-propmt, and try:
> zfsinfo (hd0,gpt2) => error: couldn't find a valid label
> I did not try the other 2 zfs-related commands because I do not know
> how to use them.
>
> Finally, The grub version on the HDD is from Ubuntu-Raring (2.0). I
> should and want to re-code grub from the FreeBSD side, but I am
> hesitant since I don't want to fail and work to re-install the
> bootloader. FreeBSD's grub is also 2.0. The grub-mkconfig command
> however, generates a completely different grub.cfg. The currently
> installed (ubuntu) grub does not recognize the "t" command and neither
> the root ID c2955d0d7dd8618b (no such device)
> menuentry 'FreeBSD' --class freebsd --class bsd --class os
> $menuentry_id_option 'kfreebsd-simple-c2955d0d7dd8618b' {
> tinsmod part_gpt
> tinsmod zfs
> tif [ x$feature_platform_search_hint = xy ]; then
> t search --no-floppy --fs-uuid --set=root c2955d0d7dd8618b
> telse
> t search --no-floppy --fs-uuid --set=root c2955d0d7dd8618b
> tfi
> echo 'Loading kernel of FreeBSD kernel ...'
> kfreebsd //@/boot/kernel/kernel
> kfreebsd_loadenv //@/boot/device.hints
> tinsmod part_gpt
> tinsmod zfs
> tif [ x$feature_platform_search_hint = xy ]; then
> t search --no-floppy --fs-uuid --set=root c2955d0d7dd8618b
> telse
> t search --no-floppy --fs-uuid --set=root c2955d0d7dd8618b
> tfi
> kfreebsd_module_elf //@/boot/kernel/opensolaris.ko
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2013-09-24 16:01 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 18:59 grub2 boot root-on-zfs errors Beeblebrox
2013-09-23 19:24 ` Massimo Maggi
2013-09-23 19:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-24 3:56 ` Andrey Borzenkov
2013-09-24 11:01 ` Andrey Borzenkov
2013-09-24 11:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-24 15:49 ` Beeblebrox
2013-09-24 16:01 ` Andrey Borzenkov [this message]
2013-09-24 16:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2013-11-24 9:14 Beeblebrox
2013-11-24 15:08 ` Andrey Borzenkov
2013-11-25 11:08 ` Beeblebrox
2013-11-25 11:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-25 17:29 ` Andrey Borzenkov
2013-11-25 22:12 ` Vladimir 'phcoder' Serbinenko
2013-11-22 7:09 Beeblebrox
2013-11-22 7:25 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-22 7:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-22 13:16 ` Colin Watson
2013-11-22 13:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-25 16:54 ` Colin Watson
2013-11-10 17:50 Beeblebrox
2013-11-10 19:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] ` <CAPSTskuZ2nHt6iKHfgFfWeBxpRyuqPmyXHd3AYCr1muaua+H7w@mail.gmail.com>
2013-11-22 15:22 ` Beeblebrox
2013-11-22 17:01 ` Beeblebrox
2013-11-23 1:09 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-23 12:54 ` Beeblebrox
2013-11-23 13:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-23 13:50 ` Beeblebrox
2013-11-23 17:58 ` Beeblebrox
2013-11-04 6:13 Beeblebrox
2013-11-05 7:35 ` Beeblebrox
2013-11-05 8:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-05 9:43 ` Beeblebrox
2013-11-09 15:31 ` Beeblebrox
2013-11-09 15:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 10:28 ` Beeblebrox
2013-11-10 10:41 ` Andrey Borzenkov
2013-11-10 14:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 12:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-08 14:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-31 10:37 Beeblebrox
2013-10-31 11:40 ` Beeblebrox
2013-10-31 16:24 ` Andrey Borzenkov
2013-10-31 16:36 ` Beeblebrox
2013-10-31 17:32 ` Andrey Borzenkov
2013-10-31 18:04 ` Beeblebrox
2013-11-02 7:58 ` Beeblebrox
2013-11-02 14:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-31 19:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-28 11:56 Beeblebrox
2013-09-28 14:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-28 8:48 Beeblebrox
2013-09-28 11:06 ` Andrey Borzenkov
2013-09-25 6:58 Beeblebrox
2013-09-25 8:06 ` Andrey Borzenkov
2013-09-25 10:33 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-30 7:23 Raif S. Berent
2013-09-05 7:31 ` Beeblebrox
2013-09-23 9:09 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20130924200133.0f2a208d@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zaphod@berentweb.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 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).