'error: ../../grub-core/fs/fat.c:447:not a FAT filesystem'

Hi I have this error ‘error: …/…/grub-core/fs/fat.c:447:not a FAT filesystem’ fedora 30 displayed briefly during boot. Lenovo ideapad
UEFI, secure boot disabled.

2 Likes

I am also having the same error :
Error message in startup-boot screen of Fedora 30 on new installation

That’s exactly the same issue that I’m experiencing here with a Fedora 30 installed on a UEFI device!

/boot: ext4
/boot/efi: fat16

have to mention that this issue is not causing any problem while the system is booting (i.e. it is ignored while booting but just take a few seconds to show up and then pass…).

1 Like

Sounds like this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1699761

2 Likes

Tanks I did not find the solution

Fixed , the fix is on the fedora main repo, just update your system or:

sudo dnf update grub2\*

Regards

1 Like

Sorry same error the result is

[root@Fedora mahdi]# sudo dnf update grub2*
Fedora 30 - x86_64 8.5 kB/s | 6.3 kB 00:00
Fedora 30 - x86_64 888 kB/s | 64 MB 01:13
RPM Fusion for Fedora 30 - Free - Test Updates 27 kB/s | 15 kB 00:00
RPM Fusion for Fedora 30 - Free - Test Updates 11 kB/s | 37 kB 00:03
RPM Fusion for Fedora 30 - Free - Updates 37 kB/s | 15 kB 00:00
RPM Fusion for Fedora 30 - Free - Updates 33 kB/s | 114 kB 00:03
RPM Fusion for Fedora 30 - Free 7.2 kB/s | 2.6 kB 00:00
RPM Fusion for Fedora 30 - Nonfree - Test Updates 19 kB/s | 14 kB 00:00
RPM Fusion for Fedora 30 - Nonfree - Test Updates 8.8 kB/s | 21 kB 00:02
RPM Fusion for Fedora 30 - Nonfree - Updates 38 kB/s | 14 kB 00:00
RPM Fusion for Fedora 30 - Nonfree - Updates 3.9 kB/s | 7.6 kB 00:01
RPM Fusion for Fedora 30 - Nonfree 15 kB/s | 15 kB 00:00
virtio-win builds roughly matching what was shipped in latest 2.4 kB/s | 3.0 kB 00:01
Latest virtio-win builds 2.3 kB/s | 3.0 kB 00:01
Fedora - - VirtualBox 373 B/s | 181 B 00:00
WineHQ packages 3.9 kB/s | 3.2 kB 00:00
Dependencies resolved.
Nothing to do.
Complete!

1 Like

All the grub2 packages upgraded here on my Fedora 30 today, but the issue still exist!

do recommendation in comment #7 in bugzilla when it fixed uncomment again:

https://bugzilla.redhat.com/show_bug.cgi?id=1699761#c7

1 Like