Install from USB stick
Everything looked OK
At the end the upgrade showed The starting screen of my Dell computer
I waited for some time but nothing else happened
How to repair the grub2?
It isn’t clear how you installed.
In particular, there is the question of whether you used UEFI booting or traditional BIOS booting to boot the installer.
How you booted the installer affects how booting is configured for the installed system.
You haven’t given enough useful information. “Install”? Or “Upgrade”? What does “end” entail? Did you power off after the installation was complete, or immediately reboot when installer finished? When was your Dell made? What model? Did you install in UEFI mode? Is Leap the only OS on your PC? Was 15.4 running perfectly fine on it prior to your upgrade/install? How do you know Grub is the problem? How long is “some time”?
Did you enter BIOS setup to see if it sees any bootable devices?
Can you boot the installation media, then select to boot the installed system successfully? This should be the easiest path to any necessary repair if the BIOS configuration seems to be in order.
My computer is a Dell made 03/04/2016 with Bios A17
L15.4 was running OK on it
I tried first “Upgrade”
The computer tells me Noot mode is set to UEFI secure boot is OFF
Under UEFI BOOT I see: UEFI : name of USB stick
Without asking The upgrade stops and I see only the DELL logo
My idea is that it has something to do with grub2
I tried “upgrade” again
In the end it tells me to reboot the computer
In a flash I see a warning: Failed to open /EFI/BOOT/? -Not found
Faile to load image??
I got it running again
I used “Boot system” and then it showed me several options
I choose sda1
Now it works
I love OpenSUSE
Great.
It isn’t quite clear whether booting now works normally, or you have to use the install USB and choose “Boot system” every time.
I restarted the computer and got the same problem
I restarted the computer and got the same problem
Can I change boot options in YAST Bootloader-default boot section?
I restarted the computer and got the same problem
Can I change boot options in YAST Bootloader-default boot section?
The setting is now:
GRUB2 for EFI /secure boot DISabled / Update NVRAM entry ENabled
Yes, you can.
Try switching from “GRUB2 for EFI” to just “GRUB2”. That’s the non-efi version of grub. I’m guessing that’s what you are actually using. If that doesn’t work, you can go back to booting via the install usb and then try again.
I will try later.
Now the OS is running and I have work to do on the computer
I changed with Yast The booting to GRUB2 That did not work.
It tells me the the setting should be GRUB2-EFI
So I started the computer again on the Installation USB and here I am back again
Can anyone give a hint how to solve this UEFI problem?
Thanks for your attention
It’s difficult to know without more information.
Usually, UEFI booting works well. And then you should not have been having these problems.
Some questions:
(1) What can you tell us about the computer (brand, model, etc). This is case we happen to recognize it as one with problems.
(2) Can you show us your disk partitioning. Provide the output from
fdisk -l
(you will need to run that as root).
(3) Provide the output from
efibootmgr -v
(you might need to run that as root, if it says that command is not found).
(4) provide the output of
df
mostly so we can tell which partition is mounted where.
------------------------------------------------------------ fdisk -l
Disk /dev/sda: 232.83 GiB, 250000000000 bytes, 488281250 sectors
Disk model: ST3250318AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6c0dd582
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 13275136 191184895 177909760 84.8G 83 Linux
/dev/sda2 12226560 13275135 1048576 512M ef EFI (FAT-12/16/32)
/dev/sda3 191184896 484085759 292900864 139.7G 83 Linux
/dev/sda4 484085760 488281249 4195490 2G 82 Linux swap / Solaris
Partition table entries are not in disk order.
Disk /dev/sdb: 28.82 GiB, 30943995904 bytes, 60437492 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2bb7c027
Device Boot Start End Sectors Size Id Type
/dev/sdb1 3392 10699 7308 3.6M ef EFI (FAT-12/16/32)
/dev/sdb2 * 10700 8620031 8609332 4.1G 17 Hidden HPFS/NTFS
---------------------------------------------------------------------efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0000,0001
Boot0000* opensuse HD(2,MBR,0x6c0dd582,0xba9000,0x100000)/File(\EFI\opensuse\grubx64.efi)
Boot0001* UEFI: KingstonDataTraveler 3.0 PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/HD(1,MBR,0x2bb7c027,0xd40,0x1c8c)AMBO
-----------------------------------------------------------------------df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4096 0 4096 0% /dev
tmpfs 4028936 4 4028932 1% /dev/shm
tmpfs 1611576 9952 1601624 1% /run
tmpfs 4096 0 4096 0% /sys/fs/cgroup
/dev/sda1 88954880 13463344 72017712 16% /
/dev/sda1 88954880 13463344 72017712 16% /.snapshots
/dev/sda1 88954880 13463344 72017712 16% /srv
/dev/sda1 88954880 13463344 72017712 16% /tmp
/dev/sda1 88954880 13463344 72017712 16% /usr/local
/dev/sda1 88954880 13463344 72017712 16% /boot/grub2/x86_64-efi
/dev/sda1 88954880 13463344 72017712 16% /var
/dev/sda1 88954880 13463344 72017712 16% /root
/dev/sda1 88954880 13463344 72017712 16% /opt
/dev/sda1 88954880 13463344 72017712 16% /boot/grub2/i386-pc
/dev/sda2 523248 5212 518036 1% /boot/efi
/dev/sda3 146450432 17534504 127064088 13% /home
tmpfs 805784 68 805716 1% /run/user/1000
nrickert , Thank you for your help on the subject. Highly appreciated!!
That all looks okay to me.
I’ll note that your hard drive “/dev/sda” is using DOS partitioning, which is unusual for UEFI booting. Typically, GPT partitioning is used. But this should not matter. In my experience, UEFI with Dell computers has been okay.
When you post computer output, as you did above, it is best to post as preformatted text. It the forum editor, click the “</>” before pasting in the computer text. It is easier to read that way.
Two more pieces of information would be useful now.
(1) The output from
ls -l /boot/efi/EFI/opensuse
and
(2) The output from
mokutil --sb-state
Thanks.
``teunis@localhost:~> ls -l /boot/efi/EFI/opensuse
total 3336
-rwxr-xr-x 1 root root 58 Aug 30 14:16 boot.csv
-rwxr-xr-x 1 root root 155 Aug 30 14:16 grub.cfg
-rwxr-xr-x 1 root root 1275904 Aug 30 14:16 grub.efi
-rwxr-xr-x 1 root root 319488 Aug 31 08:44 grubx64.efi
-rwxr-xr-x 1 root root 852408 Aug 30 14:16 MokManager.efi
-rwxr-xr-x 1 root root 953800 Aug 30 14:16 shim.efi
teunis@localhost:~> mokutil --sb-state
SecureBoot disabled
The computer is secondhand
I placed OpenSUSE on it deleting the DOS partition
The disklabel is "dos" (I thought OK what's in a name)
Thank you for helpingThe “dos” for disk label indicates that this is using traditional BIOS partitioning rather than the newer GPT partitioning.
Without getting my hands on the computer, I can only guess at what is wrong. But it seems likely that your computer is actually setup for traditional BIOS booting (Legacy booting) rather than UEFI booting. And Leap 15.4 worked, because you installed it for legacy booting. But that’s only guessing.
You can try going into BIOS settings, to see if you can switch it to UEFI booting (sometimes called CSM booting). Or you can at least take a look to see if you can tell whether that’s the problem.
An alternative would be to install booting for legacy booting, so that your system can then boot either way. To do that, run this command as root:
grub2-install --target=i386-pc /dev/sda
If there are no errors from that command, try rebooting to test.
**SOLVED**
Thanks for helping me
My computer is a DELL Optiplex with BIOS A 17
I did sudo the grub2-install command
and shut the computer down.
Start up and went straight to the BIOS settings
At advanced boot options I chose ENable legacy options ROM
At boot list options I choose LEGACY
Now shutting down and starting works as a charm 
1 Like
I’m glad to hear that.