On 12/28/20 5:26 PM, Mihai Osian wrote:
Tocmai am gasit asta, poate te ajuta:
https://wiki.archlinux.org/index.php/GRUB#Common_installation_errors
Zice acolo:
*Drop to rescue shell*
*If GRUB loads but drops into the rescue shell with no errors, it can be
due to one of these two reasons: *
- *It may be because of a missing or misplaced **grub.cfg**. This will
happen if GRUB UEFI was installed with **--boot-directory** and *
*grub.cfg** is missing,*
- *It also happens if the boot partition, which is hardcoded into the *
*grubx64.efi** file, has changed.*
So, pentru posteritate, referinta si de ajutor juniorilor voi afirma:
1. Sfatul de a bea cafeaua intra la categoria "instructiune tehnica" .. si e
chiar pur tehnica
2. Magia nu se regaseste nicaieri in alta parte mai mult decat in
scriptleturile rpm-urilor
Nu cunosc care a fost motivul dar rezolvarea (care sprijina cumva cele scrise
mai sus mai sus de Mihai)
a fost sa reinstalez toate pachetele grub2 care au rulat si ceva scriptlet-uri..
ulterior grub2-install a creat niste entry-uri in efivars bazate pe shim in loc
de grub.efi
si problema s-a rezolvat
Multumesc frumos tuturor!
Adrian
Iar aici:
https://unix.stackexchange.com/questions/565615/efi-boot-bootx64-efi-vs-efi-ubuntu-grubx64-efi-vs-boot-grub-x86-64-efi-grub-efi
*Note:** On Debian/Ubuntu, the generated GRUB core image will include a
baked-in UUID reference to whichever filesystem contains the **/boot**
directory, so you won't be able to just make a copy of either *
*/boot/grub/x86_64-efi/grub.efi** or **grubx64.efi** from the ESP and
transplant it to a removable media: it will just attempt to find the unique
UUID of your **/boot** filesystem and will drop to rescue mode if it won't
find it. If I recall correctly, the GRUB of RedHat/CentOS/Fedora should be
more suitable for transplantation to removable media.*
Mihai
_______________________________________________
RLUG mailing list
RLUG@lists.lug.ro
http://lists.lug.ro/mailman/listinfo/rlug_lists.lug.ro
