[Bug 1889509] Re: grub boot error : "symbol 'grub_calloc' not found

[Edelmar Ziegler]

*** This bug is a duplicate of bug 1889556 ***
    https://bugs.launchpad.net/bugs/1889556

Just had the same issue on an aws instance running ubuntu 18.04.4
(GNU/Linux 5.3.0-1028-aws x86_64)

It bricked that instance when I rebooted it. I did run apt a few days
ago and today noticed the system was asking for a reboot, which I did
after business hours.

Now I can only see the screenshot, it says:
error: symbol `grub_calloc´ not found.
Entering rescue mode...
grub rescue> _

Seems to be a prompt, I cannot interact with.
The instance monitoring graph on CPU use is up to 49% since this happened. Is it actually trying to fix itself?

>From what I've read the only way back for that one would be to launch
another instance an manually recreate the messed config on the bricked
one's volume. Is it the case?

Luckily enough I had an almost exact copy of that instance running
already, so I just redirected traffic. But this second instance seems to
be in the same stage, it is asking for a reboot and I have no idea if I
can do that. Can anyone point me to the direction of what I should do to
fix it?

-- 
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