[Bug 1889509] Re: grub boot error : "symbol 'grub_calloc' not found
Jeff Turner
1889509 at bugs.launchpad.net
Thu Aug 6 05:57:52 UTC 2020
*** This bug is a duplicate of bug 1889556 ***
https://bugs.launchpad.net/bugs/1889556
> 1. How can I boot the system from within the Grub rescue prompt? I
don‘t have a live System and can‘t get hands on one for several days.
You can't. The part of grub that loaded from the MBR (and printed 'grub
rescue>') is incompatible with stage 2 of grub at /boot/grub/. You
either need to upgrade the MBR part ('grub-reinstall /dev/...') or
downgrade /boot/grub/ somehow (perhaps copy off another system?). Either
way you need the install media.
> 2. I did reboot my computer right now, and minutes before I did a full
upgrade. From the above conversation one can see that the bug is known
for almost a week. So why is there no emergency patch like a package
that goes back to the last functional version and does a grub reinstall?
The bug (#1889556) has been fixed. Did you 'apt-get update' and 'apt-get
upgrade' prior to rebooting? If so, 'apt-get upgrade' would terminated
early with an exit code, which is as much of a hint as dpkg can give you
that grub is hosed, and needs fixing ('dpkg-reconfigure grub-pc') prior
to reboot.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot error : "symbol 'grub_calloc' not found
Status in grub2 package in Ubuntu:
Confirmed
Status in grub2 package in Debian:
Unknown
Bug description:
After updating grub2 (to 2.02~beta2-36ubuntu3.26) and rebooting, my
server does not boot:
Booting from Hard Disk 0...
error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue> _
I rebooted 3 servers in this way (all running Ubuntu 16.04.6 LTS) and
all hung.
A lot of other people are reporting the same problem at:
https://askubuntu.com/questions/1263125/how-to-fix-a-grub-boot-error-
symbol-grub-calloc-not-found.
---
Above most likely means that dpkg debconf no longer knows about the
correct drives to install grub onto.
Please boot & mount all the target disks and execute
$ sudo dpkg-reconfigure grub-pc
You will be asked which drives to install grub onto, and then grub
will be installed onto them, and more importantly, it will remember
where to install grub to, on all future upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509/+subscriptions
More information about the foundations-bugs
mailing list