Bug#966575: Security update can break grub - grub_calloc not found

[Steve McIntyre]

On Fri, Jul 31, 2020 at 03:07:58PM +0100, Geoff Gibbs wrote:
>On Fri, 31 Jul 2020 14:30:14 +0100
>Steve McIntyre <steve at einval.com> wrote:
>
>> I'm guessing - do you have multiple disks on your system? If so, try
>> "grub-install <disk>" on each of the bootable disks and that should
>> fix your problem.
>
>As I mentioned,
>
>mount /dev/sda5 /mnt
>grub-install --boot-directory=/mnt /dev/sda
>
>has fixed the problem for me.

Yup. Sorry - I saw that. Trying to respond to lots of people atm...

>fdisk -l reports :-
>
>Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
>Disk model: Corsair Force GS
>Units: sectors of 1 * 512 = 512 bytes
>Sector size (logical/physical): 512 bytes / 512 bytes
>I/O size (minimum/optimal): 512 bytes / 512 bytes
>Disklabel type: dos
>Disk identifier: 0xc1920bad
>
>Device     Boot  Start       End   Sectors   Size Id Type
>/dev/sda1  *      2048    206847    204800   100M  7 HPFS/NTFS/exFAT
>/dev/sda2       210942 468860927 468649986 223.5G  5 Extended
>/dev/sda5       210944    722943    512000   250M 83 Linux
>/dev/sda6       724992 468860927 468135936 223.2G 8e Linux LVM
>
>
>Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
>Disk model: WDC WD10EZRX-00A
>Units: sectors of 1 * 512 = 512 bytes
>Sector size (logical/physical): 512 bytes / 4096 bytes
>I/O size (minimum/optimal): 4096 bytes / 4096 bytes
>Disklabel type: dos
>Disk identifier: 0xc1920ba9
>
>Device     Boot     Start        End    Sectors   Size Id Type
>/dev/sdb1  *         2048  209717247  209715200   100G  7 HPFS/NTFS/exFAT
>/dev/sdb2       209721342 1953523711 1743802370 831.5G  5 Extended
>/dev/sdb5       209721344  230201343   20480000   9.8G 82 Linux swap / Solaris
>/dev/sdb6       230203392 1953523711 1723320320 821.8G 8e Linux LVM
>
>Partition 2 does not start on physical sector boundary.
>
>And then there is a list of partitions handled by LVM (many for Xen)
>but including :-
>
>Disk /dev/mapper/SSD0-root: 20 GiB, 21474836480 bytes, 41943040 sectors
>Units: sectors of 1 * 512 = 512 bytes
>Sector size (logical/physical): 512 bytes / 512 bytes
>I/O size (minimum/optimal): 512 bytes / 512 bytes
>
>Disk /dev/mapper/HDD0-var: 9.3 GiB, 9999220736 bytes, 19529728 sectors
>Units: sectors of 1 * 512 = 512 bytes
>Sector size (logical/physical): 512 bytes / 4096 bytes
>I/O size (minimum/optimal): 4096 bytes / 4096 bytes
>
>Disk /dev/mapper/SSD0-home: 38.6 GiB, 41473277952 bytes, 81002496 sectors
>Units: sectors of 1 * 512 = 512 bytes
>Sector size (logical/physical): 512 bytes / 512 bytes
>I/O size (minimum/optimal): 512 bytes / 512 bytes

ACK. I tend to do "fdisk -l /dev/sd?" to avoid that behaviour on my
md/lvm machine here. :-)

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...