thanks that's just a re-type error. i can't cut-paste from the other network :(
On Wed, Nov 20, 2024 at 4:57 AM Ulrich Sibiller
<ulrich.sibil...@gmail.com> wrote:
>
> Hi,
>
> looks like your configuration lacks an 'e' in the chainloader line
> (.fi instead of .efi).
>
> Uli
>
> On Tue, Nov 19, 2024 at 10:14 PM Michael DiDomenico
> <mdidomeni...@gmail.com> wrote:
> >
> > i'm having a little trouble getting grub2 to chain load from pxe to an
> > nvme drive. i'm certainly doing something wrong or missing something
> >
> > currently, my server is set to boot by default via pxe. pxe boots a
> > uefi grub2 instance which pulls in this config file
> >
> > menuentry "local disk" {
> > insmod chain
> > search --set=root --file /EFI/redhat/grubx64.efi
> > chainloader /EFI/redhat/grubx64.fi
> > }
> >
> > for just about every other server this seems to work okay, but not
> > this one, and this is the first server i have using internal nvme
> > drives. the drivers are behind a raid controller HPE NS204i-t Gen10
> >
> > when grub2 tries to execute the 'local disk' menu entry. i get an
> > error that says /EFI/redhat/grubx64.efi could not be found. sure
> > enough if i drop to command prompt and do an 'ls' no drives are
> > returned
> >
> > is there something funny about this disk controller? or is there some
> > other step in grub2 that i need to do in order to see the drives when
> > the drivers are nvme?
> >
> > if i boot the system via the disk controller, selected from the
> > one-time boot menu, the server does boot
> >
