GRUB “misc.h:335:overflow is detected” error on boot

Earlier this year I built a new PC and initially installed Linux Mint, but I replaced it with Fedora in February. (I have no OS installed besides Fedora.) Since then, I rarely see the grub menu, and instead usually get “error: ../../include/grub/misc.h:335:overflow is detected.” When that happens, no grub menu shows up, but Fedora still boots perfectly. I would like to resolve this before attempting to update to Fedora 42 though.

Here is my system info:

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.14.5-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550I AORUS PRO AX

I researched mostly by Googling and searching this forum for “Grub” and other similar things. The only instance I found of this error was Grub "overflow is detected" error on boot, where he concluded his hard drive was bad, but as my hard drive is new I am hesitant to conclude that.

I attempted to follow instructions at The GRUB2 Bootloader – Installation and Configuration :: Fedora Docs to reinstall GRUB2, but the instructions were too difficult for me to follow. Specifically, today I tried to follow “Restoring the bootloader using the Live disk”, but I could not identify the /boot and /root partitions, and my terminal was giving me errors. I would describe in more detail, but I’m not sure if using the Live disk even makes sense in this case, as I am able to boot Fedora on my hard drive just fine.

I cannot identify any rhyme or reason to when GRUB works and when it results in this error. It results in this error more often than not. I have read through all the “Start Here” posts, but please let me know if there’s more information I can provide.

Edit: Almost forgot to mention: running

$ [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

tells me that I’m using BIOS. If I disable CSM in the bios options, then Fedora will not boot (unless I use a live USB image). It’s unclear to me why my Fedora installation won’t use UEFI or if that is related. To the extent that is unrelated, please ignore, as I figure best to troubleshoot one issue at a time :slight_smile:

Also in case it is relevant, the output of

lsblk -f -p

is

NAME          FSTYPE   FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
/dev/loop0    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/bare/5
/dev/loop1    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/chromium-ffmpeg/73
/dev/loop2    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/chromium-ffmpeg/76
/dev/loop3    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/core/17200
/dev/loop4    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/core/17210
/dev/loop5    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/core22/1908
/dev/loop6    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/discord/238
/dev/loop7    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/core22/1963
/dev/loop8    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/discord/239
/dev/loop9    squashfs 4.0                                                     0   100% /var/lib/snapd/snap/gnome-42-2204/202
/dev/loop10   squashfs 4.0                                                     0   100% /var/lib/snapd/snap/gtk2-common-themes/13
/dev/loop11   squashfs 4.0                                                     0   100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop12   squashfs 4.0                                                     0   100% /var/lib/snapd/snap/opera/371
/dev/loop13   squashfs 4.0                                                     0   100% /var/lib/snapd/snap/snapd/23771
/dev/loop14   squashfs 4.0                                                     0   100% /var/lib/snapd/snap/opera/373
/dev/loop15   squashfs 4.0                                                     0   100% /var/lib/snapd/snap/snapd/24505
/dev/zram0                                                                              [SWAP]
/dev/nvme0n1                                                                            
├─/dev/nvme0n1p1
│                                                                                       
├─/dev/nvme0n1p2
│             ext4     1.0          19efef52-69be-4066-9086-6448aa1b316a    452M    47% /boot
└─/dev/nvme0n1p3
              btrfs          fedora 43850e52-5bc0-41d9-905b-b0d0b4a86eed  661.6G    29% /home
                                                                                        /

There lots of LHDB Probes of Gigabyte B0I AORUS PRO AX. I looked at a few and all were from 2020. Did you use recycled or second-hand parts for the build? The board supports UEFI, so some explanation is needed for why you aren’t using UEFI.

Few Fedors users still boot with BIOS. Since troubleshooting is easier if there are others with a similar configuration, you should consider making sure the system UEFI/BIOS is updated and then do a fresh install using UEFI.

1 Like

Thanks George, I appreciate the response. I only used new (unused) parts for this build, I purchased the Gigabyte board new January 2025. I guess some of the parts were older–I was trying to make a gaming build while keeping it affordable. I agree the board supports UEFI, so I was surprised to see I don’t have any UEFI boot options on my hard drive.

Fresh install does seem like the best option, though setting everything up again will be a real pain. There isn’t some kind of silver bullet for restoring my applications and settings, is there?

Edit: I’ve done some research on restoring applications and settings and I feel at least kind of OK about it now. I’ll plan to attempt an operating system reinstall tomorrow evening and then post with the outcome.

I did a fresh install of Fedora 42 (I figured might as well get the latest version) on UEFI, and grub has worked just fine since. Thank you!

Transferring my applications and settings over has gone better than I expected but not quite as well as I’d hoped. Everything will be up and running as it was shortly :slight_smile: