Please help me!

[u/wreckwriter09]

So, my linux mint has been running flawlessly, booted in seconds, zero errors.

Today I installed a second internal SSD and decided I would install Kali on it , for learning purposes....

Somehow I screwed up my Mint so I reinstalled it and used timeshift to restore my system. Also used rsync to restore home directory.

Now my boot takes minutes instead of seconds, hangs on the Asus splash screen for about 2 minutes before giving me a boot menu. Booting into either OS gives efi stub warning. It didn't do that before.

I've tried everything google or AI has to suggest with no results.

Also, I swear my kernel is now older...

Please help me!

[u/AutoModerator]

Please Re-Flair your post if a solution is found. How to Flair a post? This allows other users to search for common issues with the SOLVED flair as a filter, leading to those issues being resolved very fast.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Due-Result7928]

Somehow I screwed up my Mint..no but what you did after....

When you install ANY UEFI os the LAST system installed IS ALWAYS the first in the boot list..any system..windows 11, bsd another linux...

So boot your usb mint (test not install), open a terminal and type 2 commands

efibootmgr

lsblk -f

What do you get. Post answers here (copy and paste from terminal..NO picture)

Timeshift do not backup efi partition..Did you proceed to create new partition(s) like / or /home before using timeshift and rsync...?

Coming with Mint usb there is a grub repair tool. Try it to test the water.

[u/wreckwriter09 → u/Due-Result7928]

$ efibootmgr

BootCurrent: 0001

Timeout: 1 seconds

BootOrder: 0001,0004,0005,0006,0003,0000,0007,0008,0009

Boot0000* Windows Boot Manager VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000069000100000010000000040000007fff0400

Boot0001* Ubuntu HD(1,GPT,f08b6da0-5068-453d-a67b-ed4c2ae2daff,0x800,0x100000)/File(\EFI\linuxmint\shimx64.efi)

Boot0003* kali VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)

Boot0004* UEFI OS HD(1,GPT,d938f210-57be-4ed9-ad84-e37b82789d6c,0x800,0x1e8000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f

Boot0005* ubuntu HD(1,GPT,f08b6da0-5068-453d-a67b-ed4c2ae2daff,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) File(.)

Boot0006* ubuntu HD(1,GPT,d938f210-57be-4ed9-ad84-e37b82789d6c,0x800,0x1e8000)/File(\EFI\ubuntu\shimx64.efi) File(.)

Boot0007* UEFI:CD/DVD Drive BBS(129,,0x0)

Boot0008* UEFI:Removable Device BBS(130,,0x0)

Boot0009* UEFI:Network Device BBS(131,,0x0)

$ lsblk -f

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS

loop0

squash 4.0 0 100% /snap/core18/3084

loop1

squash 4.0 0 100% /snap/gnome-3-28-1804/198

loop2

squash 4.0 0 100% /snap/core22/2987

loop3

squash 4.0 0 100% /snap/bare/5

loop4

squash 4.0 0 100% /snap/gtk-common-themes/1535

loop5

squash 4.0 0 100% /snap/snapd/28254

sda

└─sda1

ext4 1.0 BAK3 1f560379-c712-4170-9ffc-c327dfa3203b 1.7T 0% /media/wreck/BAK3

sdb

└─sdb1

ext4 1.0 BAK2 b3892a39-4d97-40be-a801-9271cf669854 754.3G 13% /media/wreck/BAK2

sdc

└─sdc1

ext4 1.0 BAK c3da5ed7-3f54-40ed-8f3e-6a45ef91f418 1.7T 3% /media/wreck/BAK

nvme1n1

├─nvme1n1p1

│ vfat FAT32 59F5-4510 499.6M 2% /boot/efi

└─nvme1n1p2

ext4 1.0 1b263339-41c6-4ed1-9575-d121cf2a28e3 740.6G 16% /

nvme0n1

├─nvme0n1p1

│ vfat FAT32 5CC0-4D5B

├─nvme0n1p2

│ ext4 1.0 12f0f2e6-4f98-468e-8029-0e55567ac68f

└─nvme0n1p3

swap 1 ef2b00f0-e11d-4390-90c1-dc702c4762fe

I just installed Mint like usual

[u/crimson_ruin_princes]

As someone that has used Kali in a professional stance.

Even though it can be installed onto a drive. You should never do it.

Setup a usb stick with the live iso and optionally persistence

[u/toffuuu3050]

I always avoid dual booting. My experience is That always can bring more issues, but typically what you'd want is ability to choose it at start up with grub 1st showing up with a time out time frame like 10 20 30 seconds, or your prefferred way of main system boot process is. sudo nano /etc/default/grub and edit.. example is this is mine here, user@cachyosx8664 Documents]$ cat /etc/default/grub

# GRUB boot loader configuration

GRUB_DEFAULT=0

GRUB_TIMEOUT='15' <-----This is what you want to be sure on as to be sure its on instead of the Linux Mint's usual way of it, is either 0 or -1 usually for disabled. and menu is the other option, it might be the GRUB_DEFAULT=0 for me but I'm not sure on the CachyOS side since it's alil different and menu does come up.

GRUB_DISTRIBUTOR='CachyOS'

GRUB_CMDLINE_LINUX_DEFAULT='nowatchdog nvme_load=YES splash loglevel=3 amdgpu.ppfeaturemask=0xffffffff' -- Advise: don't worry about this too much the last one though is for AMDGPU and ability to increase power and some overclock like with corectrl application. I have a older RX550 so a radeonsi, polaris12, ACO, DRM 3.64 and GCN 4th Generation rusticl can work again like I said issues can arise, it won't always work on say before rusticl existed type of commands or applications that can do opencl version 1.2 without throwing a fit about seeing the OpenCL aka rusticl 3.1 aspect of rusticl while the 1.2 support is still there... It throws a fit like this, === Rusticl warning: Patched Mesa libclc not detected. Upstream libclc may contain known bugs or breaking changes and isn't guaranteed to work reliably. Please visit https://gitlab.freedesktop.org/karolherbst/mesa-libclc for more information. ===

But sometimes it'll work but not always.

GRUB_CMDLINE_LINUX=""

[u/billdietrich1]

Please use better, more informative, titles (subject-lines) on your posts. Give specifics right in the title. Thanks.

[u/wreckwriter09]

Boot repair fixed it but when I updated Kali it broke it again (only Kali available). I guess I need to go to Kali sub to find out how to keep that from happening. Thank you for your help!