EFI zfs loader and beadm?

[Andrey Fesenko]

On Thu, Mar 10, 2016 at 6:11 PM, krad <kraduk at gmail.com> wrote:
> As Eric said you cant have /boot on a separate dataset as the whole loader
> bootstrap isnt designed too look for it on the dataset defined by bootfs.
> Remember no other datasets are mounted at that stage of the bootstrap.
>
> You could maybe bodge something by manually playing around with the bootfs
> property, symlinks and rootfs variables in the loader.conf.  But why would
> you want to do this? It's more work and non standard, and will break a lot?
>
>
>
> On 10 March 2016 at 12:11, Andrey Fesenko <f0andrey at gmail.com> wrote:
>>
>> On Thu, Mar 10, 2016 at 2:55 PM, krad <kraduk at gmail.com> wrote:
>> > presumably it boots now?
>> >
>> > On 10 March 2016 at 11:01, Andrey Fesenko <f0andrey at gmail.com> wrote:
>> >>
>> >> On Thu, Mar 10, 2016 at 1:49 PM, krad <kraduk at gmail.com> wrote:
>> >> > Make sure you are running the latest snapshot of current or 10.3 as
>> >> > well, as
>> >> > the MFC commits were in early February for 10-stable
>> >> >
>> >> >>
>> >> >> If remove efiwpool/ROOT/init/boot and copy his content on
>> >> >> efiwpool/ROOT/init my scheme work fine too.
>> >> >> /usr /var /home and other included in BE for consistent boot system
>> >> >> (CURRENT world may not boot with kernel other rev),  and old home
>> >> >> snapshot sometimes useful for backup/restore
>> >> >> _______________________________________________
>> >>
>> >> % uname -a
>> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548:
>> >> Wed Mar  9 01:16:17 MSK 2016
>> >> root at des.local:/usr/obj/usr/src/sys/X220  amd64
>> >
>> >
>>
>> My current working config
>> % mount
>> ....
>>
>> This work fine, booted, beadm create new env, activate them, see boot
>> menu and select BE.
>>
>> % beadm list
>> BE    Active Mountpoint  Space Created
>> init  -      -          420.7M 2016-03-09 02:57
>> init0 NR     /           35.9G 2016-03-10 05:00
>>
>> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot)
>> system not booted, efi loader (first stage) see only my pool, not
>> found /boot/loader.efi
>
>

It probably does not matter, as bootfs have snapshots (BE), just
wanted to make it more clear (having taken significant mountpoint
/boot, /usr, /var... in zfs dataset) and was surprised why the system
does not boot

It is clear that as long as the functionality is experimental and
under development, but would like to see where the full instructions
on its implementation / restrictions, at least as early as has been
described https://wiki.freebsd.org/RootOnZFS