Yogi2
January 1st, 2020, 07:35 PM
MY CONFIGURATION
OS Name: Microsoft Windows 10 Pro
System Name: MSI
System Manufacturer: Micro-Star International Co., Ltd.
System Model : GL72 7QF
System Type: x64-based PC
Processor: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. E1795IMS.311, 2/22/2018
SMBIOS Version: 3.0
BIOS Mode UEFI
BaseBoard Manufacturer: Micro-Star International Co., Ltd.
BaseBoard Product: MS-1795
BaseBoard Version: REV:1.0
Secure Boot State: Off
Installed Physical Memory (RAM): 16.0 GB
Video Card: NVIDIA GM107M [GeForce GTX 960M] Optimus enabled
Additional OS: Mageia7; Ubuntu 19.10
My laptop multi-boots into three OS's: Windows 10, Mageia7, and Ubuntu 19.10. Recently I installed Linux Peppermint alongside the others, which turned out to be a huge mistake. Peppermint identifies itself as Ubuntu in the EFI boot directory disregarding the fact that a true Ubuntu OS was already installed. This conflict caused problems with the Windows Boot Device Manager so that it became necessary to uninstall Peppermint (deleted it's partition).
I used the Boot Repair Disk to restore Grub to a working state. There were errors during the repair. The final report was very long and the following were the only entries that might relate to the current problem, but I can't be certain of that. Given that secure boot is not enabled, these may be normal errors, or not.
Adding custom /mnt/boot-sav/sda6/boot/efi/EFI/refind/drivers_x64/ext4_x64.efi
Installing for x86_64-efi platform.
grub-install: warning: Cannot set EFI variable Boot0001.
grub-install: warning: vars_set_variable: write() failed: No space left on device.
grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No such file or directory.
grub-install: error: failed to register the EFI boot entry: No such file or directory.
grub-install --efi-directory=/boot/efi --target=x86_64-efi --no-uefi-secure-boot : exit code of grub-install :1
efibootmgr reports the following boot order:
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0000,0003,0002,0004
Boot0000* Windows Boot Manager HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS..... ....x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...t................
Boot0002* mageia7 HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\MAGEIA\GRUBX64.EFI)
Boot0003* rEFInd Boot Manager HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\REFIND\REFIND_X64.EFI)
Boot0004* ubuntu HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\UBUNTU\SHIMX64.EFI)..BO
The EFI boot directory is structured as such:
oot@GL72-7QF:/mnt/EFI# ls -l
total 24
drwxr-xr-x 4 root root 4096 Dec 31 17:09 Boot
drwxr-xr-x 2 root root 4096 Nov 29 11:28 mageia
drwxr-xr-x 4 root root 4096 Nov 1 10:58 Microsoft
drwxr-xr-x 4 root root 4096 Nov 1 10:58 MSI
drwxr-xr-x 4 root root 4096 Nov 1 10:58 refind
drwxr-xr-x 3 root root 4096 Apr 16 2019 ubuntu
root@GL72-7QF:/mnt/EFI# ls -l ubuntu
total 4264
-rwxr-xr-x 1 root root 108 Dec 31 16:51 BOOTX64.CSV
drwxr-xr-x 2 root root 4096 Apr 16 2019 fw
-rwxr-xr-x 1 root root 75992 Apr 16 2019 fwupx64.efi
-rwxr-xr-x 1 root root 126 Jan 1 10:47 grub.cfg
-rwxr-xr-x 1 root root 1668984 Jan 1 10:47 grubx64.efi
-rwxr-xr-x 1 root root 1269496 Dec 31 16:51 mmx64.efi
-rwxr-xr-x 1 root root 1334816 Dec 31 16:51 shimx64.efi
It appears that Ubuntu is booting from the shimx64.efi (grub) binary while Mageia is using it's grubx64.efi binary. It was my understanding that the shimx64.efi file is used for secure boot only so that it does not make sense why Ubuntu isn't using it's own grubx64.efi binary.
I can boot into Ubuntu via the Windows Boot Device Manager and most things are working well. I tried to install a package from the repository called Grub Customizer and received the following error message:
Unable to install "Grub Customizer:
Error while installing package: Installed grub-efi-amd64-signed package post-installation returned error exit status 1
This error seems to relate back to the error from the Boot Repair Disk operation. I thought I had the boot problem resolved but apparently something is still amiss. I am looking for advice on how to fix the efi booting so that I do not have errors when running Ubuntu 19.10. Can anyone provide some guidance?
OS Name: Microsoft Windows 10 Pro
System Name: MSI
System Manufacturer: Micro-Star International Co., Ltd.
System Model : GL72 7QF
System Type: x64-based PC
Processor: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. E1795IMS.311, 2/22/2018
SMBIOS Version: 3.0
BIOS Mode UEFI
BaseBoard Manufacturer: Micro-Star International Co., Ltd.
BaseBoard Product: MS-1795
BaseBoard Version: REV:1.0
Secure Boot State: Off
Installed Physical Memory (RAM): 16.0 GB
Video Card: NVIDIA GM107M [GeForce GTX 960M] Optimus enabled
Additional OS: Mageia7; Ubuntu 19.10
My laptop multi-boots into three OS's: Windows 10, Mageia7, and Ubuntu 19.10. Recently I installed Linux Peppermint alongside the others, which turned out to be a huge mistake. Peppermint identifies itself as Ubuntu in the EFI boot directory disregarding the fact that a true Ubuntu OS was already installed. This conflict caused problems with the Windows Boot Device Manager so that it became necessary to uninstall Peppermint (deleted it's partition).
I used the Boot Repair Disk to restore Grub to a working state. There were errors during the repair. The final report was very long and the following were the only entries that might relate to the current problem, but I can't be certain of that. Given that secure boot is not enabled, these may be normal errors, or not.
Adding custom /mnt/boot-sav/sda6/boot/efi/EFI/refind/drivers_x64/ext4_x64.efi
Installing for x86_64-efi platform.
grub-install: warning: Cannot set EFI variable Boot0001.
grub-install: warning: vars_set_variable: write() failed: No space left on device.
grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No such file or directory.
grub-install: error: failed to register the EFI boot entry: No such file or directory.
grub-install --efi-directory=/boot/efi --target=x86_64-efi --no-uefi-secure-boot : exit code of grub-install :1
efibootmgr reports the following boot order:
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0000,0003,0002,0004
Boot0000* Windows Boot Manager HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS..... ....x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...t................
Boot0002* mageia7 HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\MAGEIA\GRUBX64.EFI)
Boot0003* rEFInd Boot Manager HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\REFIND\REFIND_X64.EFI)
Boot0004* ubuntu HD(2,GPT,b524318a-9654-4983-9b59-d34dfbee61b0,0x40800,0x96000)/File(\EFI\UBUNTU\SHIMX64.EFI)..BO
The EFI boot directory is structured as such:
oot@GL72-7QF:/mnt/EFI# ls -l
total 24
drwxr-xr-x 4 root root 4096 Dec 31 17:09 Boot
drwxr-xr-x 2 root root 4096 Nov 29 11:28 mageia
drwxr-xr-x 4 root root 4096 Nov 1 10:58 Microsoft
drwxr-xr-x 4 root root 4096 Nov 1 10:58 MSI
drwxr-xr-x 4 root root 4096 Nov 1 10:58 refind
drwxr-xr-x 3 root root 4096 Apr 16 2019 ubuntu
root@GL72-7QF:/mnt/EFI# ls -l ubuntu
total 4264
-rwxr-xr-x 1 root root 108 Dec 31 16:51 BOOTX64.CSV
drwxr-xr-x 2 root root 4096 Apr 16 2019 fw
-rwxr-xr-x 1 root root 75992 Apr 16 2019 fwupx64.efi
-rwxr-xr-x 1 root root 126 Jan 1 10:47 grub.cfg
-rwxr-xr-x 1 root root 1668984 Jan 1 10:47 grubx64.efi
-rwxr-xr-x 1 root root 1269496 Dec 31 16:51 mmx64.efi
-rwxr-xr-x 1 root root 1334816 Dec 31 16:51 shimx64.efi
It appears that Ubuntu is booting from the shimx64.efi (grub) binary while Mageia is using it's grubx64.efi binary. It was my understanding that the shimx64.efi file is used for secure boot only so that it does not make sense why Ubuntu isn't using it's own grubx64.efi binary.
I can boot into Ubuntu via the Windows Boot Device Manager and most things are working well. I tried to install a package from the repository called Grub Customizer and received the following error message:
Unable to install "Grub Customizer:
Error while installing package: Installed grub-efi-amd64-signed package post-installation returned error exit status 1
This error seems to relate back to the error from the Boot Repair Disk operation. I thought I had the boot problem resolved but apparently something is still amiss. I am looking for advice on how to fix the efi booting so that I do not have errors when running Ubuntu 19.10. Can anyone provide some guidance?