On 26.10.2022 05:42, David T-G wrote:
Andrei, et al --
...and then David T-G home said... % % ...and then Andrei Borzenkov said... % ... % % it signature. So TLDR - it sounds like core.img was overwritten on % % /boot/gub2/i386-pc. May be it was deleted when new file was generated but % % information in MBR was not updated. % % Oho! How interesting.
BTW, there *is* a core.img file, but it's dated 10/17 after all of his trying and retrying. No idea how it looked right after failure :-( But that IS dated before I ran bootinfoscript and generated RESULTS1.txt yesterday ...
% % Sooooo ... How do I fix that? I wonder if boot to rescue -> mount root % under /tmp -> chroot -> grub2 -magic -fixarg is what I need. [snip]
Alas,
# make chroot stuff # chroot grub2-install /dev/sda
didn't work; I get a
grub2-install: error: cannot find EFI directory.
You are booted in EFI mode. Now you wrote a lot of all caps and expletives and swear words in this thread but you never mentioned whether you were using legacy BIOS or EFI boot in the first place. If you are actually using legacy BIOS you can either boot in legacy BIOS mode, or force installation using grub2-install --target=i386-pc /dev/sda assuming /dev/sda is really your BIOS boot device (which we have no way to determine). If you do not use legacy BIOS boot the bootinfoscript is mostly useless.
error and it dies. I dunno how to force it [new grub2 install] to be legacy and use that MBR that it [previous grub2] supposedly has.
ARRRRRGH! :-(
:-D