Date: Tue, 16 May 2017 17:57:53 +0300 From: Toomas Soome <tsoome@me.com> To: Harry Schmalzbauer <freebsd@omnilan.de> Cc: freebsd-stable@freebsd.org, tsoome@freebsd.org Subject: Re: EFI loader doesn't handle md_preload (md_image) correct? Message-ID: <DD0FE9CA-48C9-4A77-81FD-8CA139D95543@me.com> In-Reply-To: <591B12C6.4040301@omnilan.de> References: <591B12C6.4040301@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 16. mai 2017, at 17:55, Harry Schmalzbauer <freebsd@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DD0FE9CA-48C9-4A77-81FD-8CA139D95543>