Has anyone on an EFI system experienced this bug? I'm only seeing BIOS- based systems affected.
My servers were AWS EC2 instances where the 'grub rescue>' state is only a screenshot. To recover you need to reattach the broken volume to a rescue instance and 'grub-install' to the volume there. Write-up of the AWS process at: https://www.redradishtech.com/display/~jturner/2020/07/30/symbol+%27grub_calloc%27+not+found+--+how+to+fix+on+AWS Once recovered, I checked what my debconf settings were for grub. Debconf had grub installing to one partition: grub-pc grub-pc/install_devices_disks_changed multiselect /dev/disk/by-id/nvme- Amazon_Elastic_Block_Store_vol01678967bebb56f55-part1 However I know from trying manually that this would have failed with: grub-install: warning: File system `ext2` doesn't support embedding. grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. grub-install: error: will not proceed with blockists. I'm guessing I just didn't spot the error during the upgrade, and so was left with an unbootable server. Another observation: grub-pc is a rarely upgraded package. Prior to today's update for BootHole, my dpkg.log suggests the last update was July 2019. So perhaps we're all discovering problems that were latent in the Debian/Ubuntu grub update process, and the problem is not BootHole- specific? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889509 Title: grub boot error : "symbol 'grub_calloc' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
