Unable to boot into Ubuntu after cloning NVME drive with Macrium Reflect

[vw16v]

Also, here's a boot summary in case that helps. I'm petty sure it's the same as my other pastebin.

Thanks again.

https://paste.ubuntu.com/p/dvvzMwDZ9S/

[oldfred]

I would still check UUIDs & GUIDs.
lsblk -e 7 -o name,fstype,size,fsused,label,partlabel,mountpoint ,uuid,partuuid
And then UEFI uses partUUID to find ESP to boot from.
sudo efibootmgr -v #note that older versions needed -v, but now newer versions seems to give too much detail.
And the grub.cfg in ESP has to have uuid of / to find full grub. cfg in your install.
fred@z170-noble:~$ cat /boot/efi/EFI/ubuntu/grub.cfg
Above works from install only if ESP mounted with defaults, your fstab shows the more secure mount with 0077. So may need to manually mount the ESP in live installer to see files in ESP.

Actually bit easier with Boot-Repair's report as it combines all the necessary info in one report.

[tea for one]

Somehow, you seem to have different UUIDs for Windows and Ubuntu

Line 106 - Boot0000* Windows Boot Manager HD(1,GPT,303a4c17-90b2-4258-a536-590849804b1d,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)
Line 107 - Boot0001* Ubuntu HD(1,GPT,4c29f2dc-736f-4b76-a238-b3224e258df2,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)

Windows boots OK because the UUID is present
Line 206 - ├─nvme0n1p1 vfat D0E8-205E 303a4c17-90b2-4258-a536-590849804b1d

Here's an example of a successful dual boot with one ESP and the pertinent UUIDS for Windows and Ubuntu are identical

Boot0000* ubuntu	HD(1,GPT,ad1d7958-ab8d-427f-83e0-374660231ec7,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Windows Boot Manager	HD(1,GPT,ad1d7958-ab8d-427f-83e0-374660231ec7,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)

What were the boot UUIDs in your original disk?

[oldfred]

You can use efibootmgr to create a correct boot entry, it should overwrite the old one,but check that you do not have two ubuntu entries.
sudo efibootmgr -c -L "Ubuntu" -l "\EFI\ubuntu\shimx64.efi" -d /dev/nvme0n1 -p 1
See also
man efibootmgr
Check entries:
sudo efibootmgr -v # older versions needed -v to see partUUID, but newer version now outputs lots of other data, no -v then works a bit better.

[vw16v]

Thanks a lot for this info oldfred and tea for one!

@oldfred, I'm going to try to determine how I can obtain the partUUID by booting off a live installer and then attempt to mount my Ubuntu if I can figure that out. If I'm able to do that I will provide the output of /boot/efi/EFI/ubuntu/grub.cfg

@tea for one. That's odd that I have two different UUID's for Windows & Ubuntu. I'm not sure how that happened? It might of been when I upgraded from 22.04 to 24.04 recently?

But my /etc/fstab shows the following info per that pastebin

# / was on /dev/nvme0n1p5 during installation
UUID=f3409908-cd51-4af4-9735-c5373816ba49 / ext4 errors=remount-ro 0 1

Per pastebin results this is now an NTFS Windows recovery partition:
nvme0n1p5 998166528 1000214527 2048000 1000M Windows recovery environment

I just downloaded EsayUEFI and this is what it shows.
Description:Ubuntu
GPT partition GUID:{4C29F2DC-736F-4B76-A238-B3224E258DF2}
Partition number:1
Partition starting sector:2048
Partition ending sector:534527
File path:\EFI\ubuntu\shimx64.efi

Description:Windows Boot Manager
GPT partition GUID:{303A4C17-90B2-4258-A536-590849804B1D}
Partition number:1
Partition starting sector:2048
Partition ending sector:534527
File path:\EFI\Microsoft\Boot\bootmgfw.efi

Basically the same thing as pastebin. It has an option within this software to "Rebuild EFI System Partition"
I think I might give that a try. If it borks it I should just be able to install my original NVME drive back in.

[vw16v]

Hi guys, unfortunately to "Rebuild EFI System Partition" with EsayUEFI did not help. I even tried running boot-repair USB again but same issue.
Just to confirm, my entries for UUIDs should be Identical for both Ubuntu and Windows correct? I'm hoping I can figure out how to locate my \EFI\ubuntu\shimx64.efi file from a live boot CD. I might just have to use this drive in an external enclosure instead since I'm in over my head. Thanks

[vw16v]

i guys/oldfred. I booted off my Mint live USB and then I mounted nvme0n1p1 that gparted shows for my EFI system boot partition.

Here's what it shows for the grub.cfg
mint@mint:/mnt/EFI/ubuntu$ cat grub.cfg
search.fs_uuid f3409908-cd51-4af4-9735-c5373816ba49 root
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

Per my pastebin this entry exist on nvme0n1 under "p4" partition 4
├─nvme0n1p4 ext4 f3409908-cd51-4af4-9735-c5373816ba49 99af6c75-dddd-4346-9578-f3df55fe8ebd

Do you guys think if I change this value to either 4c29f2dc-736f-4b76-a238-b3224e258df2 or 303a4c17-90b2-4258-a536-590849804b1d that it will help load Grub and show both OS's on boot up?

EDIT: I also connected my original working Dual Boot NVME drive and it shows the same entry>

mint@mint:/mnt/EFI/ubuntu$ cat grub.cfg
search.fs_uuid f3409908-cd51-4af4-9735-c5373816ba49 root
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg



Thanks again for all your help. I can't figure out how to add beans for you guys. Any ideas?

[oldfred]

Your f34... is your UUID for / per Boot-Repair.
Do not mix up UUID and partUUID which is really the GUID that is unique to each gpt partition.

Did you do the efibootmgr entry in post #24. That will put a new Ubuntu entry with correct partUUID.

[vw16v]

Your f34... is your UUID for / per Boot-Repair.
Do not mix up UUID and partUUID which is really the GUID that is unique to each gpt partition.

Did you do the efibootmgr entry in post #24. That will put a new Ubuntu entry with correct partUUID.

oldfred, I didn't do this command yet because it was not clear to me.
sudo efibootmgr -c -L "Ubuntu" -l "\EFI\ubuntu\shimx64.efi" -d /dev/nvme0n1 -p 1

If I run this from a Live USB will it add an entry into correct spot? I'm assuming it will since you specified /dev/nvme0n1
Do I need to mount this drive from a live USB first? I currently have my Original NVME drive back in my laptop so I can dual boot. I left all the screws out so I can easily swap back to the clone. I was under the impression if I run this command from a live Mint USB it would add it to the wrong area? Much appreciated!

[oldfred]

That efibootmgr entry creates a new UEFI entry to find shim in the ESP partition specified by -d & -p parameters. If you do not have correct drive installed it will use the incorrect drive.
Since you have correct boot files & folder in ESP a new UEFI entry should work.

Otherwise you can use Boot-Repair to do a total grub reinstall from its advanced mode. You choose drive (which has an ESP) and an install. Grub then uses a similar ( or same?) command to add UEFI entry & adds the /Ubuntu folder with UEFI boot & grub's files that are in ESP. Rest of grub is in your install.