Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #964906

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

From Colin Watson <cjwatson@debian.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found
Date 2019-07-16 23:30 +0200
Message-ID <ykDbm-50t-33@gated-at.bofh.it> (permalink)
References (2 earlier) <yj02m-1u3-15@gated-at.bofh.it> <yiSet-4Yd-3@gated-at.bofh.it> <ykCRY-4TM-29@gated-at.bofh.it> <yiSet-4Yd-3@gated-at.bofh.it> <ykCRY-4TM-29@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Jul 16, 2019 at 11:08:25PM +0200, MiloMak wrote:
>    Updated from 2.02+dfsg1-20 to 2.04-1 like the op and get similar to the op
> 
>    [1]https://i.imgur.com/jKYXOHs.png
> 
>    when i downgrade back to 2.02 grub boots without issue. I have debian
>    installed as:
>    /dev/sdc1    /boot/efi
>    /dev/sdc2    /                (/boot is here)
> 
>    it has been working with:
>    # grep 'set root' /boot/grub/grub.cfg
>    set root='hd2,msdos2'

To save time, I'd just like to point out that whatever "set root" says
in /boot/grub/grub.cfg is basically irrelevant here.  That describes the
expected location of GRUB's modules, but it says nothing about where
grub-install is installing GRUB's core image nor about where the
firmware is loading GRUB from, and what matters here is that those last
two things need to match.

(It's also not interesting whether "set root" in your grub.cfg matches
the value of the "root" variable that you see at run-time.  The "set
root" command is just a fallback, and what usually takes effect instead
is the following "search" command which causes GRUB to try to find a
file system by UUID or similar.  On systems with multiple disks, it's
unsurprising for this to result in something different from the guessed
value.)

>    i see you say that the problem is most probably caused by a
>    misconfiguration.
> 
>    what should i be checking and how do i fix it?

I think the only thing I can say to you is to repeat the advice I gave
in the message that you were replying to just now (that is,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931896#10).  You
should at least start by going through each one of those questions and
answering them.  Since you appear to have multiple disks, it seems quite
likely that the firmware might be booting from an EFI System Partition
that isn't the same as the one you have mounted on /boot/efi, and if so
then that's something you need to correct.

-- 
Colin Watson                                       [cjwatson@debian.org]

Back to linux.debian.bugs.dist | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Sebastian Ramacher <sramacher@debian.org> - 2019-07-12 03:10 +0200
  Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Diederik de Haas <didi.debian@cknow.org> - 2019-07-12 23:50 +0200
  Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Colin Watson <cjwatson@debian.org> - 2019-07-16 23:30 +0200
  Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found dirdi <debian@dirdi.name> - 2019-07-22 06:10 +0200
  Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found "Max Hofer" <max-hofer@gmx.net> - 2019-07-29 22:20 +0200
  Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found Max Hofer <max-hofer@gmx.net> - 2019-07-30 22:00 +0200
  Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found "J. Pietschmann" <j.deb@pietschmann.ch> - 2019-08-07 12:00 +0200

csiph-web