freebsd stable - May 2017 - EFI loader doesn't handle md_preload (md_image) correct?

Hello,

unfortunately I had some trouble with my preferred MFS-root setups.
It seems EFI loader doesn't handle type md_image correctly.

If I load any md_image with loader invoked by gptboot or gptzfsboot,
'lsmod'
shows "elf kernel", "elf obj module(s)" and
"md_image".

Using the same loader.conf, but EFI loader, the md_image-file is
prompted and sems to be loaded, but not registered.  There's no md_image
with 'lsmod', hence it's not astonsihing that kernel doesn't
attach md0
so booting fails since there's no rootfs.

Any help highly appreciated, hope Toomas doesn't mind beeing initially
CC'd.

Thanks,

-harry

> On 16. mai 2017, at 17:55, Harry Schmalzbauer <freebsd at omnilan.de>
wrote:
> 
> Hello,
> 
> unfortunately I had some trouble with my preferred MFS-root setups.
> It seems EFI loader doesn't handle type md_image correctly.
> 
> If I load any md_image with loader invoked by gptboot or gptzfsboot,
> 'lsmod'
> shows "elf kernel", "elf obj module(s)" and
"md_image".
> 
> Using the same loader.conf, but EFI loader, the md_image-file is
> prompted and sems to be loaded, but not registered.  There's no
md_image
> with 'lsmod', hence it's not astonsihing that kernel
doesn't attach md0
> so booting fails since there's no rootfs.
> 
> Any help highly appreciated, hope Toomas doesn't mind beeing initially
CC'd.
> 
> Thanks,
> 
> -harry

The first question is, how large is the md_image and what other modules are
loaded?

rgds,
toomas