[Opensuse 1.5.5] New installation the efi opensuse directory is nearly empty and the system won't boot
Hi, I did a new installation using Leap 15.5, I have a dual-boot system with windows, I am using EFI without secure-boot. I had another linux distribution and I wanted to replace it with Leap. The installation process seemed to go well until I rebooted and I was greeted by the grub shell. mounting /boot/efi partition (which I did not format) I compared the opensuse directory with the old linux directory and there was a huge difference. In the opensuse directory there was on file GRUBX64.EFI and no grub.cfg, on the other hand the old linux efi directory was full of files. Why is this happening and how can I solve it? Regards.
On 2023-07-04 11:52, Wodel Youchi wrote:
Hi,
I did a new installation using Leap 15.5, I have a dual-boot system with windows, I am using EFI without secure-boot. I had another linux distribution and I wanted to replace it with Leap. The installation process seemed to go well until I rebooted and I was greeted by the grub shell. mounting /boot/efi partition (which I did not format) I compared the opensuse directory with the old linux directory and there was a huge difference. In the opensuse directory there was on file GRUBX64.EFI and no grub.cfg, on the other hand the old linux efi directory was full of files. Why is this happening and how can I solve it?
The normal contents are (with secure boot): cer@Telcontar:~> l /boot/efi/EFI/main-os/ total 3200 drwxr-xr-x 2 root root 8192 Aug 10 2020 ./ drwxr-xr-x 5 root root 8192 Aug 10 2020 ../ -rwxr-xr-x 1 root root 852408 Apr 13 12:43 MokManager.efi* -rwxr-xr-x 1 root root 56 Apr 13 12:43 boot.csv* -rwxr-xr-x 1 root root 120 Apr 13 12:43 grub.cfg* -rwxr-xr-x 1 root root 1275904 Apr 13 12:43 grub.efi* -rwxr-xr-x 1 root root 143360 Apr 13 12:43 grubx64.efi* -rwxr-xr-x 1 root root 953800 Apr 13 12:43 shim.efi* cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 04.07.2023 12:52, Wodel Youchi wrote:
Hi,
I did a new installation using Leap 15.5, I have a dual-boot system with windows, I am using EFI without secure-boot. I had another linux distribution and I wanted to replace it with Leap. The installation process seemed to go well until I rebooted and I was greeted by the grub shell. mounting /boot/efi partition (which I did not format) I compared the opensuse directory with the old linux directory and there was a huge difference. In the opensuse directory there was on file GRUBX64.EFI and no grub.cfg, on the other hand the old linux efi directory was full of files. Why is this happening
Because you do not use secure boot.
and how can I solve it?
Solve what? What exactly does not work?
On 2023-07-04 16:48, Andrei Borzenkov wrote:
On 04.07.2023 12:52, Wodel Youchi wrote:
Hi,
I did a new installation using Leap 15.5, I have a dual-boot system with windows, I am using EFI without secure-boot. I had another linux distribution and I wanted to replace it with Leap. The installation process seemed to go well until I rebooted and I was greeted by the grub shell. mounting /boot/efi partition (which I did not format) I compared the opensuse directory with the old linux directory and there was a huge difference. In the opensuse directory there was on file GRUBX64.EFI and no grub.cfg, on the other hand the old linux efi directory was full of files. Why is this happening
Because you do not use secure boot.
and how can I solve it?
Solve what? What exactly does not work?
«The installation process seemed to go well until I rebooted and I was greeted by the grub shell.» :-) -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.5)
On 04.07.2023 18:39, Carlos E. R. wrote:
On 2023-07-04 16:48, Andrei Borzenkov wrote:
On 04.07.2023 12:52, Wodel Youchi wrote:
Hi,
I did a new installation using Leap 15.5, I have a dual-boot system with windows, I am using EFI without secure-boot. I had another linux distribution and I wanted to replace it with Leap. The installation process seemed to go well until I rebooted and I was greeted by the grub shell. mounting /boot/efi partition (which I did not format) I compared the opensuse directory with the old linux directory and there was a huge difference. In the opensuse directory there was on file GRUBX64.EFI and no grub.cfg, on the other hand the old linux efi directory was full of files. Why is this happening
Because you do not use secure boot.
and how can I solve it?
Solve what? What exactly does not work?
«The installation process seemed to go well until I rebooted and I was greeted by the grub shell.»
:-)
Usual information grep -Ev '^$|^#' /etc/default/grub lsblk -f fdisk -l
On 04.07.2023 19:13, Larry Len Rainey wrote:
I use this to fix my non booting OpenSUSE
change the device to what you have - I have nvme so my device is /dev/nvme0n1
You are still using legacy GRUB?
On 7/4/23 10:39, Carlos E. R. wrote:
On 2023-07-04 16:48, Andrei Borzenkov wrote:
On 04.07.2023 12:52, Wodel Youchi wrote:
Hi,
I did a new installation using Leap 15.5, I have a dual-boot system with windows, I am using EFI without secure-boot. I had another linux distribution and I wanted to replace it with Leap. The installation process seemed to go well until I rebooted and I was greeted by the grub shell. mounting /boot/efi partition (which I did not format) I compared the opensuse directory with the old linux directory and there was a huge difference. In the opensuse directory there was on file GRUBX64.EFI and no grub.cfg, on the other hand the old linux efi directory was full of files. Why is this happening
Because you do not use secure boot.
and how can I solve it?
Solve what? What exactly does not work?
«The installation process seemed to go well until I rebooted and I was greeted by the grub shell.»
:-)
Hi, My system is configured to boot UEFI, and I did have a linux distribution which was booting fine. I am not using secure boot and I did disable secure boot while installing opensuse, I think it is not mandatory since it allowed my to disable it. What does not work : the system does not boot on opensuse. After verifying the /boot/efi/EFI/opensuse contains only this file : grubx64.efi that's it. My old linux efi directory contains multiple files : BOOTIA32.CSV, BOOTX64.CSV, gcdia32.efi, gcdx64.efi, grub.cfg, grubia32.efi, grub64.efi shim.efi, shim64.efi So the problem is clear, but I am able to correct it for now. I tried to boot with rescue mode then to chroot the / while mounting all the necessary directories like /dev, /sys, /proc and /run, I also mounted /boot and /boot/efi. Then I tried to reinstall grub2 using : grub2-install --efi-directory=/boot/efi --bootloader-id=opensuse --target=x86_64-efi /dev/nvme0n1 But I am getting this error : grub2-install error efibootmgr failed to register the boot entry : no such file or directory Any ideas? Regards.
On 2023-07-05 22:47, Wodel Youchi wrote:
Hi,
My system is configured to boot UEFI, and I did have a linux distribution which was booting fine. I am not using secure boot and I did disable secure boot while installing opensuse, I think it is not mandatory since it allowed my to disable it. What does not work : the system does not boot on opensuse. After verifying the /boot/efi/EFI/opensuse contains only this file : grubx64.efi that's it. My old linux efi directory contains multiple files : BOOTIA32.CSV, BOOTX64.CSV, gcdia32.efi, gcdx64.efi, grub.cfg, grubia32.efi, grub64.efi shim.efi, shim64.efi
So the problem is clear, but I am able to correct it for now.
I tried to boot with rescue mode then to chroot the / while mounting all the necessary directories like /dev, /sys, /proc and /run, I also mounted /boot and /boot/efi.
Then I tried to reinstall grub2 using :
grub2-install --efi-directory=/boot/efi --bootloader-id=opensuse --target=x86_64-efi /dev/nvme0n1
But I am getting this error : grub2-install error efibootmgr failed to register the boot entry : no such file or directory
Ok, the openSUSE trick for achieving that, is: you do the same things you do till your command above, but instead, you run "yast", typed exactly like that in a terminal. That will get you the text mode yast (running the graphical yast in a chroot is more difficult, I don't know the trick). In "system" you select "boot loader". Check that all the settings in all the tabs are correct (you can copy paste them here, it is text), and finally, in "bootloader options" tab, change "Timeout in Seconds" just one second up or down, then exit accepting all changes ([OK] button) Just changing the timeout forces YaST2 to write everything in the boot system to disk again. Why I don't know, but it is useful. Ah, the name in the boot menu and the name in "/boot/efi/EFI/" directory is selected in "/etc/default/grub" file, line: GRUB_DISTRIBUTOR="main-os" Remember to heed the comment on the first line of the file, then do the timeout trick for paranoia shake. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Hi, I did all that, then used Yast to reinstall the boot loader, but it didn't change anything, still having one file in /boot/efi/EFI/opensuse and still the system booting the grub's shell. By the way, to make efibootmgr command works, I had to mount also : /sys/firmware/efi/efivars on /mnt/sys/firmware/efi/efivars before chrooting. But unfortunately, this didn't help me to solve the problem. Regards.
On 2023-07-09 13:32, Wodel Youchi wrote:
Hi,
I did all that, then used Yast to reinstall the boot loader, but it didn't change anything, still having one file in /boot/efi/EFI/opensuse and still the system booting the grub's shell.
By the way, to make efibootmgr command works, I had to mount also : /sys/firmware/efi/efivars on /mnt/sys/firmware/efi/efivars before chrooting.
But unfortunately, this didn't help me to solve the problem.
I don't know, I don't have any machine with efi security disabled. Andrei Borzenkov asked a question you did not answer: Usual information grep -Ev '^$|^#' /etc/default/grub lsblk -f fdisk -l -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-09-23 07:58]:
On 2023-07-09 13:32, Wodel Youchi wrote:
Hi,
I did all that, then used Yast to reinstall the boot loader, but it didn't change anything, still having one file in /boot/efi/EFI/opensuse and still the system booting the grub's shell.
By the way, to make efibootmgr command works, I had to mount also : /sys/firmware/efi/efivars on /mnt/sys/firmware/efi/efivars before chrooting.
But unfortunately, this didn't help me to solve the problem.
I don't know, I don't have any machine with efi security disabled.
Andrei Borzenkov asked a question you did not answer:
Usual information
grep -Ev '^$|^#' /etc/default/grub lsblk -f fdisk -l
I have a system with efi security disabled and have no /boot/efi nor /sys/firmware/efi directories and have no problem booting. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-07-09 14:34, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-09-23 07:58]:
On 2023-07-09 13:32, Wodel Youchi wrote:
Hi,
I did all that, then used Yast to reinstall the boot loader, but it didn't change anything, still having one file in /boot/efi/EFI/opensuse and still the system booting the grub's shell.
By the way, to make efibootmgr command works, I had to mount also : /sys/firmware/efi/efivars on /mnt/sys/firmware/efi/efivars before chrooting.
But unfortunately, this didn't help me to solve the problem.
I don't know, I don't have any machine with efi security disabled.
Andrei Borzenkov asked a question you did not answer:
Usual information
grep -Ev '^$|^#' /etc/default/grub lsblk -f fdisk -l
I have a system with efi security disabled and have no /boot/efi nor /sys/firmware/efi directories and have no problem booting.
I think you are also using legacy mode, which is different thing. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-09-23 08:56]:
On 2023-07-09 14:34, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-09-23 07:58]:
On 2023-07-09 13:32, Wodel Youchi wrote:
Hi,
I did all that, then used Yast to reinstall the boot loader, but it didn't change anything, still having one file in /boot/efi/EFI/opensuse and still the system booting the grub's shell.
By the way, to make efibootmgr command works, I had to mount also : /sys/firmware/efi/efivars on /mnt/sys/firmware/efi/efivars before chrooting.
But unfortunately, this didn't help me to solve the problem.
I don't know, I don't have any machine with efi security disabled.
Andrei Borzenkov asked a question you did not answer:
Usual information
grep -Ev '^$|^#' /etc/default/grub lsblk -f fdisk -l
I have a system with efi security disabled and have no /boot/efi nor /sys/firmware/efi directories and have no problem booting.
I think you are also using legacy mode, which is different thing.
possible, but I would need to reboot to find out and not so inclined. :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Le 09/07/2023 à 15:00, Patrick Shanahan a écrit :
* Carlos E. R. <robin.listas@telefonica.net> [07-09-23 08:56]:
On 2023-07-09 14:34, Patrick Shanahan wrote:
I have a system with efi security disabled and have no /boot/efi nor /sys/firmware/efi directories and have no problem booting.
I think you are also using legacy mode, which is different thing.
possible, but I would need to reboot to find out and not so inclined. :)
if you don't have any efi mount and can boot, you certainly boot as legacy, no doubt jdd -- c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E. R. -
jdd＠dodin.org -
Larry Len Rainey -
Patrick Shanahan -
Wodel Youchi