grub boot error : "symbol 'grub_calloc' not found

1. offizieller Beitrag

    Hi there,

    after applying these Debian 10 security updates

    Code
    Get:1 http://deb.debian.org/debian-security buster/updates/main amd64 grub2-common amd64 2.02+dfsg1-20+deb10u2 [538 kB]
Get:2 http://deb.debian.org/debian-security buster/updates/main amd64 grub-pc amd64 2.02+dfsg1-20+deb10u2 [131 kB]
Get:3 http://deb.debian.org/debian-security buster/updates/main amd64 grub-pc-bin amd64 2.02+dfsg1-20+deb10u2 [903 kB]
Get:4 http://deb.debian.org/debian-security buster/updates/main amd64 grub-common amd64 2.02+dfsg1-20+deb10u2 [2477 kB]

    concerning the GRUB boot loader on my OMV 5 system I made a reboot and the I got stuck within the boot loader with this message:

    error: symbol `grub_calloc' not found.

    Entering rescue mode...

    grub rescue>

    I suppose it has something to do with this Debian/Ubuntu Bug: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509

    However, has anyone a hint to solve this issue?

    OpenMediaVault 6.x (most recent stable version) -- 64 bit -- OMV-Extras 6.x (most recent stable version) -- Default Kernel

    All of a sudden I am having the exact same error after the latest updates. Anyone?


    This is all I am seeing after the bios post:


    error: symbol `grub_calloc' not found.

    Entering rescue mode...

    grub rescue>

    Hi there,

    Heise Developer Online, a IT news site in Germany made some sort of summary and status of the boot loader mess which happens on different Linux distributions. So I wonder which is the recommended way to fix the issue on an OMV system? Is it the Boot-Repair-Disk or the rather complicated way as described by the Ubuntu Security Team ? Any advice by the OMV experts would be highly appreciated.

    OpenMediaVault 6.x (most recent stable version) -- 64 bit -- OMV-Extras 6.x (most recent stable version) -- Default Kernel

    • Offizieller Beitrag
    Zitat von topi

    Hi there,

    Heise Developer Online, a IT news site in Germany made some sort of summary and status of the boot loader mess which happens on different Linux distributions. So I wonder which is the recommended way to fix the issue on an OMV system? Is it the Boot-Repair-Disk or the rather complicated way as described by the Ubuntu Security Team ? Any advice by the OMV experts would be highly appreciated.

    The issue here is not the boothole fix that Heise is referring to and is causing problems on RHEL/CentOS. It might be the issue from the Ubuntu team though. Either way, if you have a grub issue, you can always boot a Debian 10 ISO and it has an option to repair grub.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    I have the same issue today,

    I restored a backup image once, then when I applied all the pending updates, the system crashed again.


    I will restore again I will check what update is the guilty...


    BUT, if someone has the solution... it will be helpful...

    Hi there,

    indeed, it is a mess with this bootloader update.

    However,

    Zitat von ludicerZA

    I also experienced this issue earlier today and used Boot-Repair-Disk to restore GRUB (which resolved this issue).

    seems an easy approach to fix the wrecked system after you applied the the grub updated in question.

    OpenMediaVault 6.x (most recent stable version) -- 64 bit -- OMV-Extras 6.x (most recent stable version) -- Default Kernel

    I tried to fix this error using Boot-Repair-Disk, but when it's throwing the below error:


    "GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again."


    I'm unclear on why my installation is throwing the error, but others aren't having any issues using this tool to fix.

    I encountered this issue this week as well. Luckily Boot-Repair-Disk got me back up and running. One thing of note is that I had to run the repair twice before it was able to fully fix all of the issues.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden