| Summary: | drakboot crashed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jim Beard <jim.beard> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | lewyssmith |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools-18.21-1.mga7 | CVE: | |
| Status comment: | |||
|
Description
Jim Beard
2019-07-21 04:54:06 CEST
> See my bug report of a few minutes on failure of new kernel installation https://bugs.mageia.org/show_bug.cgi?id=25162 Your ESP (EFI System Partition) has lots of strange things, but what matters here is: /boot/EFI/EFI/mageia: -rwxr-xr-x 1 root root 125440 Jul 23 2018 grubx64.efi* So at some point, Grub2-efi was installed OK in the proper place. As Thomas says in the other bug, the visibility of the ESP is in question. If you can get into the system with the added kernel, # update-grub2 is usually good for re-making Grub2 menus with everything in them. CC:
(none) =>
lewyssmith Jim Can you re-visit this? There is the suspicion that somehow the system was installed with Grub2 for MBR, whereas the box is apparently EFI: > grub2-install failed: Installing for x86_64-efi platform. > grub2-install: error: cannot find EFI directory. These messages are consistent. The related bug 25162 had as an important factor the fact that the system was not configured for the ESP (EFI System Partition), though how that arose is a mystery. You have now manually configured in the ESP, and things are better. Can you please re-try 'drakboot' to see whether this bug still applies? Drakboot now works. See my comments to bug 25162 for the root of the problem, two entries for the DVD reader in the BIOS boot priority order and the wrong entry appeared earlier in the list. So we can close this, thank you. The other bug says it all. Status:
NEW =>
RESOLVED |