Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #228893

Re: Fixing a Grub Foul-up, Not There Yet.

From Kushal Kumaran <kushal@locationd.net>
Newsgroups linux.debian.user
Subject Re: Fixing a Grub Foul-up, Not There Yet.
Date 2020-11-22 02:10 +0100
Message-ID <BdM38-2J6-9@gated-at.bofh.it> (permalink)
References <BbRTj-6Mo-1@gated-at.bofh.it> <BbVDA-yZ-3@gated-at.bofh.it> <BdGh3-7nD-3@gated-at.bofh.it> <BdGTL-7PZ-1@gated-at.bofh.it> <BdKaZ-1zH-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Sat, Nov 21 2020 at 05:04:30 PM, "Martin McCormick" <martin.m@suddenlink.net> wrote:
> Felix Miata <mrmazda@earthlink.net> writes:
>> Save yourself many keystrokes by using the symlinks in the root directory 
>> instead
>> of the long-winded full version-named /boot/vmlinuz-4.19.0-5-686-pae....
>
> This is wonderful to know and in the root or / directory of this
> disk, there is 
> initrd.img, initrd.img.old, vmlinuz and vmlinuz.old
>
> 	Those all point to valid targets.  I presently have the
> no-boot disk mounted on a working linux system where it's root
> directory is /dev/sde1 and the current links plus the old links
> are as follows:
>
> lrwxrwxrwx   1 root root    32 Jun 26  2019 initrd.img -> boot/initrd.img-4.19.0-5-686-pae
> lrwxrwxrwx   1 root root    31 Jun 26  2019 initrd.img.old -> boot/initrd.img-4.9.0-9-686-pae
> lrwxrwxrwx   1 root root    29 Jun 26  2019 vmlinuz -> boot/vmlinuz-4.19.0-5-686-pae
> lrwxrwxrwx   1 root root    28 Jun 26  2019 vmlinuz.old -> boot/vmlinuz-4.9.0-9-686-pae
>
> 	I finally have found something that may be a clue to
> what's actually wrong. While trying to manually make that drive
> boot, I got this:
>
> grub rescue> set prefix=(hd0,1)//boot/grub
> grub rescue> insmodnormal
> Unknown command `insmodnormal'.
>
> That was a good old syntax error so I tried
>
> insmod normal with a space
> grub rescue> insmod normal
> error: symbol `grub_calloc' not found.
>
> 	I'm pretty sure that shouldn't happen at all and is
> what's behind the failure to boot.
>
> 	I haven't found any uuid's that are different although I
> first thought I had as I looked at some links which had uuid's
> but they were good when I looked at the actual partition.  It's
> easy to go down a rabbit hole if one doesn't watch out.
>
> 	I think there may be something about grub that got left
> out or changed during the upgrade.
>

There was a recent update to grub that was reported to cause the
grub_calloc symbol error.  As I remember it, the problem is because of a
mismatch between the grub binaries and the grub modules.  Reinstalling
grub using the grub-install command fixes it.

For details, bug report is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575

-- 
regards,
kushal

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-16 20:00 +0100
  Re: Fixing a Grub Foul-up Dan Ritter <dsr@randomstring.org> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-17 04:00 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 05:00 +0100
      Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-12-01 15:40 +0100
        Re: Fixing a Grub Foul-up Solved! "Martin McCormick" <martin.m@suddenlink.net> - 2020-12-01 21:10 +0100
  Re: Fixing a Grub Foul-up John Boxall <jboxall47@gmail.com> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up Kenneth Parker <sea7kenp@gmail.com> - 2020-11-17 03:00 +0100
  Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-11-17 00:00 +0100
    Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-21 20:00 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-21 20:40 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 00:10 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-22 01:20 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Kushal Kumaran <kushal@locationd.net> - 2020-11-22 02:10 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Dan Ritter <dsr@randomstring.org> - 2020-11-22 01:10 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 04:50 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 18:00 +0100

csiph-web