I have a dell inspiron 15 3000.
After searching everywhere i tried yast2- Boot Loader changed to grub2 for efi and I got : /usr/sbin/grub2-install: error:cannot find EFI directory
fdisk -l
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 1067007 16384 8M BIOS boot
/dev/nvme0n1p3 1067008 84953087 83886080 40G Linux filesystem
/dev/nvme0n1p4 84953088 486940671 401987584 191.7G Linux filesystem
/dev/nvme0n1p5 486940672 500118158 13177487 6.3G Linux swap
gdisk
GPT fdisk (gdisk) version 1.0.1
efibootmgr -v
EFI variables are not supported on this system
Secure boot is disable
I m loss and I couldn’t find any solution , please help, thanks in advance
Le 22/05/2019 à 19:46, limonnana a écrit :
>
> I have a dell inspiron 15 3000.
> After searching everywhere i tried yast2- Boot Loader changed to grub2
> for efi and I got : /usr/sbin/grub2-install: error:cannot find EFI
> directory
>
> fdisk -l
>
> /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
> /dev/nvme0n1p2 1050624 1067007 16384 8M BIOS boot
> /dev/nvme0n1p3 1067008 84953087 83886080 40G Linux filesystem
> /dev/nvme0n1p4 84953088 486940671 401987584 191.7G Linux filesystem
> /dev/nvme0n1p5 486940672 500118158 13177487 6.3G Linux swap
>
>
>
> I m loss and I couldn’t find any solution , please help, thanks in
> advance
>
>
is the efi partition mounted?
To sort this out we may ultimately need you to post output from these:
cat /etc/fstab
blkid
Please wrap commands and their ouput in code tags. Select output to wrap, then click the # ] button above the input window.
To get output of current state from gdisk requires -l switch and device name, e.g. ‘gdisk -l /dev/sda’.
The df command would satisfy jdd’s request.
How and when was 15.0 installed? IOW, is it recent or brand new? Was installation from the stick you are booting from now? What does the screen look like when you boot the stick and choose installation instead of installed system? Is there a row of 5-6 function keys and what they do at the bottom of the screen? If so, it is booting in legacy mode, not UEFI.
sudo gdisk -l /dev/nvme0n1
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/nvme0n1: 500118192 sectors, 238.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0C12B7A7-E66D-47E6-92EA-3A9611CE1F19
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 500118158
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 1050623 512.0 MiB EF00 EFI System Partition
2 1050624 1067007 8.0 MiB EF02
3 1067008 84953087 40.0 GiB 8300
4 84953088 486940671 191.7 GiB 8300
5 486940672 500118158 6.3 GiB 8200
How and when was 15.0 installed? from usb stick 2 days ago
IOW, is it recent or brand new? what is iow ? the computer is new came with ubuntu preinstalled
Was installation from the stick you are booting from now? 2 days ago
What does the screen look like when you boot the stick and choose installation instead of installed system? Is there a row of 5-6 function keys
It looks as if you installed your system for traditional BIOS booting. But your system only boots with EFI. And that’s why it won’t boot without the install USB.
You can change your system to use UEFI booting, but that is tricky and depends on the BIOS as to how well it will work.
If you want to use UEFI booting, then you need to mount the EFI partition at “/boot/efi”. So start by doing that.
Maybe try adding the following line to “/etc/fstab”:
UUID=276C-D28C /boot/efi vfat iocharset=utf8 0 0
I copied that from my Leap 15.0 system, except that I changed the UUID to match what you show in output above. The exact position of the line should not matter. On my system, it is just before the line for “swap”.
When you have made that change, reboot. And then provide the output of
This is a puzzle that I’m not sure how to suggest you deal with.
[ol]
[li] Your NVME is GPT partitioned for both UEFI and Legacy booting (nvme0n1p1 is ESP; nvme0n1p2 is BIOS boot for standard Grub to use)[/li][li] Leap is installed in Legacy mode (ESP partition is missing from fstab and df output)[/li][li] The stick booted to installation selection is in UEFI mode (no Function keys “menu” at bottom of first screen)[/li][/ol]
I’m guessing:[ol]
[li] Leap was installed by booting the stick in legacy mode, leaving Ubuntu’s existing ESP partition untouched, while creating 4 partitions for Leap to use[/li][li] Given it came with Ubuntu and an ESP partition, Leap should be able to be reconfigured as a UEFI installation:[/li][list=a]
[li] change fstab via YaST partitioner to include the ESP partition[/li][li] use YaST bootloader to switch Grub booting to UEFI mode[/li][/ol]
[li] Reboot without using USB stick[/li][/list]
#2#2 seems to me to be partially consistent with NRickert’s recommendation in post #5, but through a different path, and with more steps.
You cannot switch to “booting in UEFI mode” while booted in legacy mode. It is impossible to write NVRAM boot entry. It is possible to run “grub2-install --no-nvram” to avoid error, manually select grubx64.efi on ESP and complete switch after openSUSE is booted by reinstalling bootloader again.
He booted the stick to UEFI mode installation. Can’t the stick be booted in UEFI to chroot to or boot installed system in UEFI mode? It’s what I thought was implied both possible and necessary by writing what I wrote.
[quote]What does the screen look like when you boot the stick and choose installation instead of installed system? Is there a row of 5-6 function keys
No[/quote]
Notice the function key notations. If you see the legacy boot screen, you are doing it wrong. So go back and try again to get the UEFI boot screen.
My experience with a Dell computer, is that you can hit F12 during boot, and get a boot menu. There you can select booting your USB. And it might give you two boot options (UEFI and CSM booting). Be sure to choose the UEFI booting).
By the way, those images are from a blog post that I recently made (about installing Leap 15.1).
What did you search for, and why?
Look, my son once fiddled with YaST2-Boot Loader on his UEFI laptop and made it unbootable from the internal hard disk.
So, why did you try to change the boot loader to grub2-efi?
What did happen before that?
From the second photo of your BIOS setup it seems to me that the USB stick can boot in UEFI mode:
My guess is that the “SanDisk” entries there correspond to USB sticks, right?
But perhaps you should uncheck/disable “USB storage device” in the first photo/page, in order to make sure that the stick is not booted in ***legacy ***mode.
Further, what does not appear to be logical to me is that in the second of these photos, “ubuntu” is checked/enabled (in non-UEFI mode?), while your 256GB Toshiba drive in UEFI mode is unchecked/disabled.
Can you try and disable “ubuntu” and enable your 256GB Toshiba drive in UEFI mode on that setup page?
What happens then at boot?
Did you remove ubuntu, and if yes, how?
Finally, it would be helpful if you could post the complete output of
sudo parted -l
so that one could see the flags of the partitions.
Except for the extra partition with the ‘bios_grub’ flag, this listing of parted looks like the setup and flags on the UEFI booting laptop here, which has openSUSE 15.0 installed and running. The ‘legacy_boot’ flag on the root partition doesn’t seem to say much about the boot method, strange enough.
Did you try to enable your Toshiba 256GB disk for UEFI booting (while probably disabling that “ubuntu” entry) ?
See the photos of your BIOS setup that you posted links of.
Ok I finally reinstall : leap 15.1 Thanks to your help guys I understood that the problem was that my installation was not in uefi. When I loaded up the stick for the new installation I recognize because the 2 last pictures that it was loaded in not uefi so went back and selected a different option and this time because of your 2 picture shared I saw it was loaded in uefi and everything is ok now thank you very very much
The situation with UEFI is still somewhat confusing. And different computer manufacturers manage to make it even more complicated. That’s why I provided those images.