Kubuntu installation will not boot - Grub reboots system

[ad4869]

New user here troubleshooting kubuntu installation boot/grub problem.

Problem: I installed Kubuntu onto my laptop which had 2 drives at the time(1 SSD and 1 M.2 at 500GB each). There was a previous Windows 10 installation on one of the drives(I can't remember which) and it was possible to boot into windows by selecting "Windows Boot manager". When selecting Ubuntu(or the drive that Kubuntu is installed on) after a couple seconds the message "Reset System" flashes at the top left of the screen and the system reboots.

I have tried to remove the Windows installation by formatting both drives and then installing only Kubuntu. I still get the Reset system message.

I have run Ubuntu's Boot Repair tool and then the recommended repair(Output below).

============================= Boot Repair Summary ============================== Recommended repair: __________________________________________________ __________ The default repair of the Boot-Repair utility will reinstall the grub-efi of nvme0n1p2, using the following options: nvme0n1p1/boot/efi Additional repair will be performed: unhide-bootmenu-10s use-standard-efi-file restore-efi-backups rm /mnt/boot-sav/nvme0n1p1/efi/Boot/bootx64.efi mv /mnt/boot-sav/nvme0n1p1/efi/Boot/bkpbootx64.efi /mnt/boot-sav/nvme0n1p1/efi/Boot/bootx64.efi Mount nvme0n1p1 on /mnt/boot-sav/nvme0n1p2/boot/efi Unhide GRUB boot menu in nvme0n1p2/etc/default/grub ===================== Reinstall the grub-efi of nvme0n1p2 ====================== chroot /mnt/boot-sav/nvme0n1p2 grub-install --version grub-install (GRUB) 2.06-2ubuntu7 modprobe: FATAL: Module efivars not found in directory /lib/modules/5.3.0-28-generic chroot /mnt/boot-sav/nvme0n1p2 modprobe efivars chroot /mnt/boot-sav/nvme0n1p2 efibootmgr -v before grub install BootCurrent: 001D Timeout: 0 seconds BootOrder: 0001,001A,0010,0011,0012,0013,0014,0015,0016,0017, 001D,001B,001E,0018,0019,001C,0000,001F,0020,0021, 0022 Boot0000* Windows Boot Manager HD(1,GPT,f2a613f6-f156-4475-a892-1719dda12115,0x800,0x100000)/File(EFIMicrosoftBootbootmgfw.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.}...O................ Boot0001* ubuntu HD(1,GPT,a5224259-dd38-4da8-a9b5-1971a22f3bf5,0x800,0x100000)/File(EFIubuntushimx64.efi) Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560) Boot0014 Regulatory Information FvFile(478c92a0-2622-42b7-a65d-5894169e4d24) Boot0015 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479) Boot0016 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5) Boot0017 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28) Boot0018* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55) Boot0019* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49) Boot001A* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400) Boot001B* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600) Boot001C* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601) Boot001D* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803) Boot001E* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803) Boot001F* IDER BOOT CDROM PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1) Boot0020* IDER BOOT Floppy PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0) Boot0021* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6) Boot0022* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354) chroot /mnt/boot-sav/nvme0n1p2 uname -r 5.3.0-28-generic chroot /mnt/boot-sav/nvme0n1p2 grub-install --efi-directory=/boot/efi --target=x86_64-efi Installing for x86_64-efi platform. grub-install: warning: EFI variables cannot be set on this system. grub-install: warning: You will have to complete the GRUB setup manually. Installation finished. No error reported. df /dev/nvme0n1p1 mv /mnt/boot-sav/nvme0n1p2/boot/efi/EFI/Boot/bootx64.efi /mnt/boot-sav/nvme0n1p2/boot/efi/EFI/Boot/bkpbootx64.efi cp /mnt/boot-sav/nvme0n1p2/boot/efi/efi/ubuntu/grubx64.efi /mnt/boot-sav/nvme0n1p2/boot/efi/EFI/Boot/bootx64.efi chroot /mnt/boot-sav/nvme0n1p2 grub-install --efi-directory=/boot/efi --target=x86_64-efi Installing for x86_64-efi platform. grub-install: warning: EFI variables cannot be set on this system. grub-install: warning: You will have to complete the GRUB setup manually. Installation finished. No error reported. chroot /mnt/boot-sav/nvme0n1p2 efibootmgr -v after grub install BootCurrent: 001D Timeout: 0 seconds BootOrder: 0001,001A,0010,0011,0012,0013,0014,0015,0016,0017, 001D,001B,001E,0018,0019,001C,0000,001F,0020,0021, 0022 Boot0000* Windows Boot Manager HD(1,GPT,f2a613f6-f156-4475-a892-1719dda12115,0x800,0x100000)/File(EFIMicrosoftBootbootmgfw.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.}...O................ Boot0001* ubuntu HD(1,GPT,a5224259-dd38-4da8-a9b5-1971a22f3bf5,0x800,0x100000)/File(EFIubuntushimx64.efi) Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560) Boot0014 Regulatory Information FvFile(478c92a0-2622-42b7-a65d-5894169e4d24) Boot0015 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479) Boot0016 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)

I removed the SSD and attempted to install using the manual disk installation on the M.2 following a Kubuntu installation video(creating a swap, /, /home partition) I feel like it's missing a boot partition but am unsure. After this didn't work I ran another boot info, here is the partial output.

============================== Boot Info Summary =============================== => No boot loader is installed in the MBR of /dev/nvme0n1. => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sda. nvme0n1p1: __________________________________________________ ___________________ File system: vfat Boot sector type: FAT32 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/BOOT/fbx64.efi /efi/BOOT/mmx64.efi /efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi /efi/ubuntu/grub.cfg nvme0n1p2: __________________________________________________ ___________________ File system: swap Boot sector type: - Boot sector info: nvme0n1p3: __________________________________________________ ___________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Ubuntu 22.04 LTS Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub nvme0n1p4: __________________________________________________ ___________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files: sda1: __________________________________________________ ________________________ File system: vfat Boot sector type: SYSLINUX 6.03 Boot sector info: Syslinux looks at sector 32792 of /dev/sda1 for its second stage. The integrity check of Syslinux failed. No errors found in the Boot Parameter Block. Operating System: Boot files: /boot/grub/grub.cfg /syslinux.cfg /efi/BOOT/grubx64.efi /ldlinux.sys ================================ 1 OS detected ================================= OS#1: Ubuntu 22.04 LTS on nvme0n1p3 ================================ Host/Hardware ================================= CPU architecture: 64-bit Video: Intel Corporation from Intel Corporation Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic, x86_64) ===================================== UEFI ===================================== BIOS/UEFI firmware: R0YET42W (1.25 ) from LENOVO The firmware seems EFI-compatible, but this live-session is in Legacy/BIOS/CSM mode (not in EFI mode). c152ec201c37b6e97bbc2207e49d1271 nvme0n1p1/BOOT/fbx64.efi fdafb5eece6caeccb788c946a28e6872 nvme0n1p1/BOOT/mmx64.efi f62c28d9b477b6a1a7b1c991b2b6637d nvme0n1p1/ubuntu/grubx64.efi fdafb5eece6caeccb788c946a28e6872 nvme0n1p1/ubuntu/mmx64.efi 728124f6ec8e22fbdbe7034812c81b95 nvme0n1p1/ubuntu/shimx64.efi 728124f6ec8e22fbdbe7034812c81b95 nvme0n1p1/BOOT/BOOTX64.efi ============================= Drive/Partition Info ============================= Disks info: __________________________________________________ __________________ nvme0n1 : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, no-wind, 2048 sectors * 512 bytes Partitions info (1/3): __________________________________________________ _______ nvme0n1p1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far nvme0n1p3 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, not-far nvme0n1p4 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios Partitions info (2/3): __________________________________________________ _______ nvme0n1p1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot nvme0n1p3 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot nvme0n1p4 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot Partitions info (3/3): __________________________________________________ _______ nvme0n1p1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1 nvme0n1p3 : not--sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, nvme0n1 nvme0n1p4 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1 fdisk -l (filtered): __________________________________________________ _________ Disk nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors Disk identifier: 0F9839BE-7C09-4942-B6E1-207E72C6E2D7 Start End Sectors Size Type nvme0n1p1 2048 999423 997376 487M EFI System nvme0n1p2 999424 64999423 64000000 30.5G Linux swap nvme0n1p3 64999424 164999167 99999744 47.7G Linux filesystem nvme0n1p4 164999168 1000206335 835207168 398.3G Linux filesystem Disk sda: 7.5 GiB, 8023703552 bytes, 15671296 sectors Disk identifier: 0x00459d98 Boot Start End Sectors Size Id Type sda1 * 2048 15671295 15669248 7.5G c W95 FAT32 (LBA) Disk zram0: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram1: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram2: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram3: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram4: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram5: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram6: 972.8 MiB, 1020071936 bytes, 249041 sectors Disk zram7: 972.8 MiB, 1020071936 bytes, 249041 sectors parted -lm (filtered): __________________________________________________ _______ sda:8024MB:scsi:512:512:msdos:Lexar USB Flash Drive:; 1:1049kB:8024MB:8023MB:fat32::boot, lba; nvme0n1:512GB:nvme:512:512:gpt:HFM512GDHTNG-8710B:; 1:1049kB:512MB:511MB:fat32::boot, esp; 2:512MB:33.3GB:32.8GB:linux-swap(v1)::; 3:33.3GB:84.5GB:51.2GB:ext4::; 4:84.5GB:512GB:428GB:ext4::; blkid (filtered): __________________________________________________ ____________ NAME FSTYPE UUID PARTUUID LABEL PARTLABEL sda └─sda1 vfat CEF1-79C4 00459d98-01 BOOT-REPAIR nvme0n1 ├─nvme0n1p1 vfat 1017-D283 2ebed6cc-2bea-48f5-9e08-46dec0952067 ├─nvme0n1p2 swap d2c9d1c8-9b85-41eb-a399-39339ec6a05a ff7f2c45-8397-4a76-b000-a4a36665614d ├─nvme0n1p3 ext4 1d86d826-e1df-4289-9c89-17ef9c381ae2 4543c35f-e90e-44b8-a0ca-8ee70f5bdbbe └─nvme0n1p4 ext4 456818fd-1781-4015-9cf2-6279e3677083 883656bc-c0ce-4529-9d6b-9ff688f12926 Mount points (filtered): __________________________________________________ _____ Avail Use% Mounted on /dev/nvme0n1p1 480.8M 1% /mnt/boot-sav/nvme0n1p1 /dev/nvme0n1p3 35.6G 19% /mnt/boot-sav/nvme0n1p3 /dev/nvme0n1p4 371G 0% /mnt/boot-sav/nvme0n1p4 /dev/sda1 6.6G 12% /cdrom Mount options (filtered): __________________________________________________ ____ /dev/nvme0n1p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,ioc harset=iso8859-1,shortname=mixed,errors=remount-ro /dev/nvme0n1p3 ext4 rw,relatime /dev/nvme0n1p4 ext4 rw,relatime /dev/sda1 vfat ro,noatime,fmask=0022,dmask=0022,codepage=437,ioch arset=iso8859-1,shortname=mixed,errors=remount-ro =================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) =================== search.fs_uuid 1d86d826-e1df-4289-9c89-17ef9c381ae2 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg =================== nvme0n1p3/boot/grub/grub.cfg (filtered) ==================== Ubuntu 1d86d826-e1df-4289-9c89-17ef9c381ae2 Ubuntu, with Linux 5.15.0-40-generic 1d86d826-e1df-4289-9c89-17ef9c381ae2 Ubuntu, with Linux 5.15.0-25-generic 1d86d826-e1df-4289-9c89-17ef9c381ae2 ### END /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_uefi-firmware ### ======================== nvme0n1p3/etc/fstab (filtered) ======================== # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/nvme0n1p3 during installation UUID=1d86d826-e1df-4289-9c89-17ef9c381ae2 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=1017-D283 /boot/efi vfat umask=0077 0 1 # /home was on /dev/nvme0n1p4 during installation UUID=456818fd-1781-4015-9cf2-6279e3677083 /home ext4 defaults 0 2 # swap was on /dev/nvme0n1p2 during installation UUID=d2c9d1c8-9b85-41eb-a399-39339ec6a05a none swap sw 0 0 ==================== nvme0n1p3/etc/default/grub (filtered) ===================== GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ================= nvme0n1p3: Location of files loaded by Grub ================== GiB - GB File Fragment(s) 77.360076904 = 83.064750080 boot/grub/grub.cfg 1 61.731025696 = 66.283184128 boot/vmlinuz 1 34.978511810 = 37.557891072 boot/vmlinuz-5.15.0-25-generic 2 61.731025696 = 66.283184128 boot/vmlinuz-5.15.0-40-generic 1 34.978511810 = 37.557891072 boot/vmlinuz.old 2 62.584415436 = 67.199504384 boot/initrd.img 1 62.178180695 = 66.763313152 boot/initrd.img-5.15.0-25-generic 1 62.584415436 = 67.199504384 boot/initrd.img-5.15.0-40-generic 1 62.178180695 = 66.763313152 boot/initrd.img.old 1

I've been on this for 3 weeks now and am unsure of where to go next. If this is in the wrong sub or I need to post elsewhere let me know.

Also, is there no way to hide large amounts of text in like a spoiler tag?

Laptop
CPU: Intel i7-8565U
RAM: 16GB DDR4 2400MHz
GPU: Integrated Intel UHD 620
Storage: 512GB SSD M.2 PCIe-NVME

[rab0171610]

BIOS/UEFI firmware: R0YET42W (1.25 ) from LENOVO The firmware seems EFI-compatible, but this live-session is in Legacy/BIOS/CSM mode (not in EFI mode)

Did you set up an EFI partition? I do not know if you are trying to use UEFI or legacy/csm/bios boot mode. It looks like you booted into the live session in legacy bios mode but that system supports UEFI. If you did not set up an EFI partition, that could be the problem. If you do not know what that means, you can research online to learn more about it, setting up an EFI partition Linux, Setting up an EFI partition Ubuntu, etc. I do not know what your video guide told you but it may be out of date if it does not mention this.
More can be learned about it here:
https://help.ubuntu.com/community/UEFI

[ad4869]

When I installed and set up the partitions manually? No, I don't think I did, but I when I installed normally(selecting the whole M.2 drive to erase and install) it creates. I created a new bootable usb of the installation iso. I used rufus and selected GPT and UEFI for partition scheme and target system.

After the installation the issue is still there. I then reboot and select Try Kubuntu and open up the partition manager and I see the EFI partition.

I don't think I'm allowed to post links to an image.

[rab0171610]

No, I don't think I did, but I when I installed normally(selecting the whole M.2 drive to erase and install) it creates.

Yes, going by your info I thought you created them manually. Automatic partitioning will create it indeed. I was not aware you had also done that. What you are describing sounds like the dreaded "boot loop". I do not know how to tell you to fix it. In the meantime, I would spend time trying to learn how others may have overcome this, keep searching online for: "Reset System" grub. I don't know if there is a one size fits all solution. Many people with HP and Lenovo laptops have reported these issues specifially, but I am sure it can happen to anyone. It may or may not have something to do with secure boot. I have never had this issue, so I am unfortunately not able to help you. Keep checking back here. Hopefully someone with some expertise or experience with this issue can point you in the right direction eventually. If you find a solution before then on your own or progress at all with different errors, please post back detailed info as this can help someone else with similar issues. Good luck. I look forward to seeing how you finally resolve this.

[Schwarzer Kater]

Is there a more recent firmware available from Lenovo for your machine than you have in use (you did not specify your laptop's model number…)?
Perhaps this is the solution as I had customers' Lenovo machines (laptops and desktops) that would not boot from Ubuntu installations in the past. These issues were fixed by firmware updates.

PS: Also be sure to disable "secure boot" in UEFI to exclude this setting as cause for problems.

[ad4869]

Is there a more recent firmware available from Lenovo for your machine than you have in use (you did not specify your laptop's model number…)?
Perhaps this is the solution as I had customers' Lenovo machines (laptops and desktops) that would not boot from Ubuntu installations in the past. These issues were fixed by firmware updates.

PS: Also be sure to disable "secure boot" in UEFI to exclude this setting as cause for problems.

Hi, I am using an E590 running UEFI BIOS Version R0YET42W. There is a newer version in the Lenovo support center. I will attempt to update this week and check back.

rab0171610, Thank you for trying. I am looking into the boot loop searches to see if there is anything that might work.

[ad4869]

Okay, so....I am trying to update the BIOS using the Lenovo support auto updater, but it is not working(for the BIOS portion). I may need to update it manually. Meanwhile I have been researching how the GRUB loader works and when I boot into Boot Repair I check the /boot file using the terminal.

So on the M.2(nvme0) in the path of /mnt/boot-sav/nvme0n1p1/EFI/BOOT I find three files: BOOTX64.EFI, fbx64.efi, and mmx64.efi. Isn't there supposed to be a grub folder in /boot? I use nano to check what the files there contain but I just see symbols and "This program cannot be run in DOS mode".

I did find a grub.cfg(and grubx64.eft, BOOTX64.csv, mmx64.efi, shimx64.efi) file in /nvme0n1p1/efi/ubuntu. Should I be looking into this further?

[ad4869]

Hello from my newly booted Kubuntu installation!

So I wanted to post this in case anyone later has the same issue.

I did update my bios but it did not solve the problem. It did get me to the grub menu but it kept booting me into maintenance mode and would give me an error about the target being destructive and failed to start the target. So I reinstalled Kubuntu and was back to the boot loop of the reboot system issue.

After looking through the bios menu again, I was looking at the TPM setting and remember hearing some news on some linux news channel about Lenovo making it harder to run linux and decided to disable it. I rebooted and I FINALLY booted into Kubuntu. All this time I was making sure Secureboot was disabled but I never read anything about the TPM setting.

I don't know how this will affect my laptop's security, but for now I have access to my install.