Drops to grub> prompt in Secure Boot Mode

[setchi]

I've Ubuntu installed with Windows 10 in dual-boot. When I run the PC or when I restart it this happens:
1. I see the motherload screen.
2. A grub command line appears.
3. I type 'exit' to halt it.
4. The motherload screen appears again.
5. Finally the grub where I can select the OS shows up and all runs properly.
---
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No existe el archivo o el directorio: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EFITables:
 abr 05 15:07:13 toni-MS-7922 kernel: efi: EFI v2.31 by American Megatrends
 abr 05 15:07:13 toni-MS-7922 kernel: efi: ESRT=0xdef80998 ACPI 2.0=0xde7c8000 ACPI=0xde7c8000 SMBIOS=0xf04d0 MPS=0xfd520
 abr 05 15:07:13 toni-MS-7922 kernel: esrt: Reserving ESRT space from 0x00000000def80998 to 0x00000000def809d0.
 abr 05 15:07:13 toni-MS-7922 kernel: Secure boot could not be determined
InstallationDate: Installed on 2018-04-04 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
Package: shim-signed 1.33.1~16.04.1+13-0ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
SecureBoot: 6 0 0 0 0
Tags: xenial
Uname: Linux 4.13.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Steve Langasek (vorlon)]

I had a look at the set of modules being loaded by the grub.cfg. The only line that seems like it wouldn't be satisfied is:

        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi

There is no lzopio module being included in grubx64.efi.

However, I have this in my own grub.cfg as well, and it doesn't cause any failure to boot.

Otherwise, the config looks uneventful. your boot entries do show that you have the .signed kernel installed, so it should be bootable.

If you try to individually run the commands listed in /boot/efi/EFI/ubuntu/grub.cfg at the grub prompt, what happens?:

search.fs_uuid 908780ee-820c-44ee-9625-2bd693097849 root hd1,gpt4
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

[Steve Langasek (vorlon)]

Please also run 'apport-collect 1761336' from the booted system to provide more complete information about the firmware and setup.

[setchi (setchi)]

I've been checking meanwhile to try to fix it and... I did! I solved the issue disabling the MSI Fast Boot feature in the BIOS configuration. It can be found in the following menu: Settings > Advanced > Windows 8/8.1 Configuration. It seems it was causing the problem. My motherload is MSI Z97S.

Do you still want me to run 'apport-collect 1761336'?

Thank you for your time.

[Steve Langasek (vorlon)]

On Thu, Apr 05, 2018 at 01:09:19AM -0000, setchi wrote:
> Do you still want me to run 'apport-collect 1761336'?

Yes, please. It is unclear how or why this MSI Fast Boot feature is
changing the behavior of grub.

[setchi (setchi)]

apport information

[setchi (setchi)]

apport information

[setchi (setchi)]

apport information

[setchi (setchi)]

apport information

[setchi (setchi)]

apport information

[setchi (setchi)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

Could MSI Fast Boot skip scanning devices which the EFI subsystem in the ESP's copy of grub rely on?

There are also actually two "ubuntu" entries in firmware, one with extra firmware-specific extra options appended. One may work with fastboot while the other does not.

If you re-enable Fastboot and hit F12, does one of the two 'ubuntu' entries you should see there work normally?

[setchi (setchi)]

I've tested it. If I hit F12, both 'ubuntu' entries run okay.

[Launchpad Janitor (janitor)]

[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]