Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #225713
| From | Tom Dial <tddial@comcast.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: grub update and reinstallation |
| Date | 2020-08-01 22:40 +0200 |
| Message-ID | <Az6sq-4Pp-3@gated-at.bofh.it> (permalink) |
| References | <AyXS9-7em-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 8/1/20 05:23, Graham Seaman wrote: > On 01/08/2020 07:50, Tom Dial wrote: >> I have a laptop that became unbootable because >> the initial loader failed to find a symbol (grub_calloc) and balked. >> Like the one mentioned here, it uses legacy boot. One explanation has it >> that this happened because the MBR and the remainder of grub were not >> both updated or were updated with slightly incompatible data. >> >> One fix appears to be to reinstall grub using a rescue CD or another >> system. That worked for me. > > My home server sits in my loft managing comms with the outside world; > yesterday it overheated (not a surprise) and went down. On reboot after > cooling it came back up with the grub_calloc problem, so like Tom I > reinstalled after which it appears to be OK. > > BUT because I have no idea why the original problem occurred, or why a > reinstall fixed the problem, I have no idea if this is a permanent fix, > or if I have a system which is liable to fail to reboot again in the > future. Does anyone know? It's a very simple single drive system with > legacy boot. I run it with security updates on auto, and check for other > updates manually once a week or so. Should I change this pattern for a > while while possible grub problems are sorted upstream? My slightly educated and informed, and partly imagined, guess is that the original problem - inability to find the grub_calloc symbol - resulted from a packaging or installation glitch that left the boot block that referenced grub_calloc out of sync with the main part of grub with the piece that had the symbol. If that is so, and if reinstalling grub fixes the problem at all, the fix should be final. The grub-install done in conjunction with upgrade to 10.5 just worked OK, as did the previous installation of grub 2.02+dfsg1-20+deb10u2. I do not know if the fact it was on a VM might have changed the outcome. Tom Dial > > Graham
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
grub update and reinstallation Ross Boylan <rossboylan@stanfordalumni.org> - 2020-07-31 20:30 +0200
Re: grub update and reinstallation Brian <ad44@cityscape.co.uk> - 2020-07-31 20:40 +0200
Re: grub update and reinstallation Andrew Cater <amacater@gmail.com> - 2020-07-31 21:30 +0200
Re: grub update and reinstallation Tom Dial <tddial@comcast.net> - 2020-08-01 09:10 +0200
Re: grub update and reinstallation Graham Seaman <graham@theseamans.net> - 2020-08-01 13:30 +0200
Re: grub update and reinstallation Sven Joachim <svenjoac@gmx.de> - 2020-08-01 15:10 +0200
Re: grub update and reinstallation Graham Seaman <graham@theseamans.net> - 2020-08-01 19:30 +0200
Re: grub update and reinstallation Andrew Cater <amacater@gmail.com> - 2020-08-01 22:00 +0200
Re: grub update and reinstallation Tom Dial <tddial@comcast.net> - 2020-08-02 05:50 +0200
Re: grub update and reinstallation Graham Seaman <graham@theseamans.net> - 2020-08-03 00:00 +0200
Re: grub update and reinstallation Andrew Cater <amacater@gmail.com> - 2020-08-03 18:40 +0200
Re: grub update and reinstallation Leslie Rhorer <lesrhorer@att.net> - 2020-08-03 23:50 +0200
Re: grub update and reinstallation Tom Dial <tddial@comcast.net> - 2020-08-01 22:40 +0200
Re: grub update and reinstallation Ross Boylan <rossboylan@stanfordalumni.org> - 2020-08-01 00:40 +0200
csiph-web