Re: grub2 boot root-on-zfs errors

[Andrey Borzenkov <arvidjaar@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2791 bytes --]

В Tue, 24 Sep 2013 07:56:36 +0400
Andrey Borzenkov <arvidjaar@gmail.com> пишет:

> В Mon, 23 Sep 2013 21:28:41 +0200
> Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> 
> > On 23.09.2013 20:59, Beeblebrox wrote:
> > >>>  This doesn't demonstrate anything else than that you didn't use tools
> > > correctly. It's:  grub-probe -d /dev/ada0p2
> > > 
> > > Thank you very much - I ran the command you instructed and see that
> > > the FS is identified correctly.
> > > $ grub-probe -d /dev/ada0p2
> > > zfs
> > > 
> > > I cannot, however, boot from grub directly into zfs-root. After the
> > > grub menu comes up, and I fall to command-prompt, listing the drives
> > > shows no ZFS paths and the various menu variations I have tried do not
> > > work.
> > > 
> > > Unfortunately, there is not much accurate documentation for
> > > FreeBSD+ZFS+grub, and the linux solutions to the problem do not work
> > > for FreeBSD.
> > > 
> > > The main problem form the grub loader / command line, is that I cannot
> > > get any code loaded which is located on a ZPOOL:
> > > 
> > > menuentry 'FreeBSD-ZFS' {
> > >     insmod zfs
> > >     set root='hd0,gpt2'
> > >     kfreebsd /boot/loader      }
> > > 
> > > Fails because grub cannot find bootloader and gives "no such file" error.
> > > Please let me know what ıther info I can provide to debug the problem.
> > > 
> > Syntax is:
> > (DISK)/VOLUME@[SNAPSHOT]/FILE
> > I think it's described somewhere in manual
> 
> No, it is not. There are examples using zfs with this syntax (but
> without snapshot)s).
> 
> I'm not sure where should it go ... in "File name syntax" probably?

Like this?

From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: [PATCH] document ZFS filename syntax.

Signed-off-by: Andrey Borzenkov <arvidjaar@gmail.com>

---
 docs/grub.texi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/grub.texi b/docs/grub.texi
index 574f602..1cef528 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -2564,6 +2564,13 @@ GRUB's @dfn{root device} implicitly. So if you set the root device to,
 say, @samp{(hd1,1)} by the command @samp{set root=(hd1,1)} (@pxref{set}),
 then @code{/boot/kernel} is the same as @code{(hd1,1)/boot/kernel}.
 
+On ZFS filesystem the first path component must be
+@var{volume}@samp{@@}[@var{snapshot}].
+So @samp{/rootvol@snap-129/boot/grub/grub.cfg} refers to file
+@samp{/boot/grub/grub.cfg} in snapshot of volume @samp{rootvol} with name
+@samp{snap-129}.  Trailing @samp{@@} after volume name is mandatory even if
+snapshot name is omitted.
+
 
 @node Block list syntax
 @section How to specify block lists
-- 
tg: (321e011..) u/zfs_file_names (depends on: master)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]