Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Jan 2016 02:58:26 +0000
From:      Steven Hartland <killing@multiplay.co.uk>
To:        freebsd-current@freebsd.org
Subject:   Re: ZFSROOT UEFI boot
Message-ID:  <56AAD552.9090202@multiplay.co.uk>
In-Reply-To: <CACA0VUiwF=40n0TNSfTAnbHY-1xLMytOzeXjnufF%2BoPKRbvBew@mail.gmail.com>
References:  <CALfReyeY3=L9O81AX7xMKj3Ai2DTvBpXtbqepTZc2%2BGEsrT3vA@mail.gmail.com> <8991747525093115430@unknownmsgid> <20160124215300.4cd7f1207f5a4c7b28ef7ffc@dec.sakura.ne.jp> <56A51A4C.1040808@multiplay.co.uk> <20160129000344.feaf5f828e5d43d5fbbb652a@dec.sakura.ne.jp> <CACA0VUiwF=40n0TNSfTAnbHY-1xLMytOzeXjnufF%2BoPKRbvBew@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 28/01/2016 16:22, Doug Rabson wrote:
> On 28 January 2016 at 15:03, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote:
>
>> It's exactly the NO GOOD point. The disk where boot1 is read from
>> should be where loader.efi and loader.conf are first read.
>>
> I just wanted to note that gptzfsboot and zfsboot behaves this way. Boot1
> looks for loader in the pool which contains the disk that the BIOS booted.
> It passes through the ID of that pool to loader which uses that pool as the
> default for loading kernel and modules. I believe this is the correct
> behaviour. For gptzfsboot and zfsboot, it is possible to override by
> pressing space at the point where it is about to load loader.

I believe I understand at least some of your issue now, could you please 
test the code on the following review to see if it fixes your issue please:
https://reviews.freebsd.org/D5108

     Regards
     Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56AAD552.9090202>