[SOLVED] LM20.1 Boot issue after GRUB menu failed

[caramba]

Hello,
A similar problem on a DELL 3793 17' with an I3 processor. Running dual boot with MINT 20.1 Cinamon and Win10 with EFI in secure boot mode (I tried also without secure boot, with no difference).
But first, this laptop has a 128G M2 disk with EFI partition and Win10, and a second internal SSD disk with linux.
Randomly, maybe 1 over 5 boots, the selection of an OS gives 'error, you need to load the kernel first' and jumps to a grub prompt. Only way out, power off the machine and restart, and next boot run fine.
I tried to use boot repair, no effect.
I read that similar questions were raised in the ubuntu forum, but no clear solution.
Is this a consequence of boot options in grub.cfg ?
Content for mint is here :
menuentry 'Linux Mint 20.1 Cinnamon' --class linuxmint --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-77c8a244-a765-4bb0-a938-21c13675434e' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 77c8a244-a765-4bb0-a938-21c13675434e
else
search --no-floppy --fs-uuid --set=root 77c8a244-a765-4bb0-a938-21c13675434e
fi
linux /boot/vmlinuz-5.4.0-66-generic root=UUID=77c8a244-a765-4bb0-a938-21c13675434e ro quiet splash
initrd /boot/initrd.img-5.4.0-66-generic
}

Suggestion may help other people installing linux on DELL laptops, there are a number signalling a very similar problem.

[SMG]

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

[caramba]

here the result of inxi -Fxxxrz :

Code: Select all

System:
  Kernel: 5.4.0-66-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: <filter> 
  Chassis: type: 10 serial: <filter> 
  Mobo: Dell model: 0W0WYK v: A00 serial: <filter> UEFI: Dell v: 1.13.0 
  date: 11/13/2020 
Battery:
  ID-1: BAT0 charge: 38.1 Wh condition: 38.1/42.0 Wh (91%) volts: 13.0/11.4 
  model: SMP DELL VM73283 type: Li-poly serial: <filter> status: Full 
CPU:
  Topology: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
  arch: Ice Lake rev: 5 L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 9523 
  Speed: 1200 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 1200 2: 1200 
  3: 1200 4: 1200 
Graphics:
  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:8a56 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel Smart Sound Audio vendor: Dell driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:34c8 
  Sound Server: ALSA v: k5.4.0-66-generic 
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
  driver: r8169 v: kernel port: 3000 bus ID: 01:00.0 chip ID: 10ec:8136 
  IF: enp1s0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter 
  vendor: Dell driver: ath10k_pci v: kernel port: 3000 bus ID: 02:00.0 
  chip ID: 168c:0042 
  IF: wlp2s0 state: up mac: <filter> 
  Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:4 
  chip ID: 0cf3:e009 
Drives:
  Local Storage: total: 350.27 GiB used: 16.50 GiB (4.7%) 
  ID-1: /dev/nvme0n1 model: PC SN530 NVMe WDC 256GB size: 238.47 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 21106012 scheme: GPT 
  ID-2: /dev/sda vendor: Samsung model: SSD 840 EVO 120GB size: 111.79 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: BB6Q scheme: GPT 
Partition:
  ID-1: / size: 22.98 GiB used: 11.02 GiB (47.9%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 80.86 GiB used: 2.52 GiB (3.1%) fs: ext4 dev: /dev/sda3 
  ID-3: swap-1 size: 5.65 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 0 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://mirror6.layerjet.com/linuxmint/packages ulyssa main upstream import backport
  2: deb http://mirror.unix-solutions.be/ubuntu focal main restricted universe multiverse
  3: deb http://mirror.unix-solutions.be/ubuntu focal-updates main restricted universe multiverse
  4: deb http://mirror.unix-solutions.be/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/yannubuntu-boot-repair-focal.list 
  1: deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal main
Info:
  Processes: 247 Uptime: 48m Memory: 7.55 GiB used: 1.36 GiB (18.0%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

when boot error occurs, it affects both linux and windows boot but not the UEFI entry. Then, after 'saving' the configuration but without any change it goes back to the grub starting menu and it may be possible to start linux (maybe not always). Other solution is to stop the computer by holding the power button and then restart it, not very safe...
Thanks for any help and clues. I've seen similar messages on ubuntu forum but no clear answer, and it may be that several errors may cause this behaviour.
Puzzling point, it happens randomly and the computer may also start correctly

[SMG]

Your system is quite new. I recommend switching to the 5.8 kernel which is available in Update Manager. I expect you will get better performance although I do not know that it will affect the issue of this thread.

Open Update Manager. Select View > Linux Kernels and click Continue. Make sure 5.8 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear. Install the kernel and then reboot for it to become active.

For LM20 we recommend a root partition of 30-50GB in size when there is a separate /home. You have a smaller / so you'll want to make sure as you add kernels you are also deleting ones you are no longer using to keep the fullness percentage below 75%. I personally keep the current one I am using and one version back that I know works on my system.

when boot error occurs, it affects both linux and windows boot but not the UEFI entry. Then, after 'saving' the configuration but without any change it goes back to the grub starting menu and it may be possible to start linux (maybe not always). Other solution is to stop the computer by holding the power button and then restart it, not very safe...
Thanks for any help and clues. I've seen similar messages on ubuntu forum but no clear answer, and it may be that several errors may cause this behaviour.
Puzzling point, it happens randomly and the computer may also start correctly

It's always difficult to know if a change has any effect when the issue happens randomly.

When you indicate you are "saving" the configuration, do you mean the EFI configuration which is part of BIOS/UEFI and not any configurations related to grub?

The fact killing the power and restarting seems to work leads me to suspect there might be a "leftover" setting or change from Windows which could be affecting this situation. I've seen posts where others indicate something similar happens to them which switching between Windows and Mint.

[caramba]

Thanks for the help.
Answers : root partition is at 47%, old kernels are erased.
yes, I meant saving the EFI configuration although without changing it
This machine almost never boots under windows. I kept it because the computer is still under warranty and was sold with windows only. But I added a SSD disk and installed MINT.
there was a message during the install about a secure boot key that could be needed, I did not understand and continued, expecting a request, but there was none. I don't know if secure boot keys come automatically for linux.
I'll load kernel 5.8 and test it a few days at least before coming back on the forum.

[SMG]

Thanks for the help.
Answers : root partition is at 47%, old kernels are erased.

Yes, the percentage does show in your inxi. There's no concern at the present time; I just wanted you to be aware for future reference.

yes, I meant saving the EFI configuration although without changing it
This machine almost never boots under windows. I kept it because the computer is still under warranty and was sold with windows only. But I added a SSD disk and installed MINT.

That seems odd that saving the configuration helps. It almost seems like it is somehow "forgetting", but I do not know what settings might affect that.

there was a message during the install about a secure boot key that could be needed, I did not understand and continued, expecting a request, but there was none. I don't know if secure boot keys come automatically for linux.

It is my understanding the necessary info is supplied by Ubuntu/Mint for Secure Boot for the operating install. Some third-party drivers (such as Nvidia which you do not have) do require defining MOK.

[caramba]

Changing to the 5.8 kernel did not solve the issue. The boot error may still occur.
I read on a post that a similar problem occurred on a DELL computer with windows removed and running only ubuntu or Mint. The idea of a mix-up due to windows is not convincing.
True, there are a large number of options in the EFI 'bios', I already found about changing a few to activate the SSD disk and de-activate the 'raid' mode for windows (the system would not see the SSD when raid was activated, and windows would not boot under AHCI unless told to accept it).
There remain questions about NIC - network interface card - and PXE, maybe I should deactivate since there is no question about network boot.
And a few other strange options that I don't quite understand...
I remember also problems in the past on a machine that refused to boot correctly until I decided to unplug it from the main to be certain that no information remained active except for the bios eeproms. But you cannot 'unplug' a laptop battery...

[SMG]

Someone just posted a solution this morning that is working for them on their Dell Inspiron 3793 [SOLVED] LM20 inconsistent boot.

They used the info in this post Dell Laptop Inspiron 17" 3793 brandnew - after Ubuntu install always boot failure to grub. Apparently the issues is with the TPM module.

[caramba]

A really excellent proposal. I modified the grub files according to the post from 'ask ubuntu', and so far the problem seems to be solved.
I re-started the machine maybe 20 times with no error.
put here a copy of these commands to clear tpm problem on the dell laptop
sudo cp /etc/grub.d/40_custom /etc/grub.d/06_notpm
sudo bash -c 'echo "rmmod tpm" >> /etc/grub.d/06_notpm'
sudo update-grub

The topic should be tagged SOLVED
Thanks a lot for the help !

[SMG]

The topic should be tagged SOLVED
Thanks a lot for the help !

Only you can change the top to solved. Please edit the title of your first post of this thread and add [SOLVED] at the beginning.

[caramba]

Thanks to a nice fellow on the forum who found the right tricky solution - Other users of DELL laptop may be concerned