GRUB Install Issues on Laptop With WIN11

I recently had to purchase a new laptop (Dell Inspiron 15-3530). It came with Windows 11 installed on a 1TB SSD. My current Ubuntu system (22.04) is installed on a 2 TB HDD. I created an Ubuntu Live USB, booted into the new laptop, ran GParted, shrank the Windows partition, created new root & home partitions along with a ntfs shared partition (data). Using GParted I copied over everything with no (apparent) problems. I changed fstab to reflect the new partition designations (nvme01n1x).

Now my problem. How do I install GRUB? My Google searches are confusing at best & everything I’ve tried has failed ('cannot find efi direstory"). After that I’m sure I’ll have to run update-grub. And would there be any further changes to fstab (there is a UUID for /boot/efi that does not match the UUID on the ssd).

Any help is greatly appreciated!

For me I like to use:

sudo fdisk -l | grep dev

Then I’ll use:

sudo grub-install /dev/sdxxx

where “/dev/sdxxx” is my drive
Then I update-grub.

Can you boot into Ubuntu?
If so, try this:-
sudo grub-install /dev/nvme0n1
sudo nano /etc/default/grub
GRUB_DISABLE_OS_PROBER=false #Remove comment symbol or add this line to find Windows 11 (if required)
sudo update-grub

There are two versions of grub. grub-pc for old BIOS systems and grub-efi-amd64 for UEFI systems.
If you have pre-installed Windows 11, it should be UEFI. many new Dell systems say BIOS, but once in BIOS it will say UEFI only.
Do not try to install to sda nor MBR. Your drive is /dev/nvme0n1 with partitions pX where X is partition number.

If UEFI system you do not want grub installed in gpt’s protective MBR for BIOS boot. You must have it installed in ESP for UEFI boot.

I typically use efibootmgr directly. But those that need a gui, can use Boot-Repair, booted in UEFI mode.

https://help.ubuntu.com/community/Boot-Repair

See
man efibootmgr

sudo efibootmgr -c -L “Ubuntu” -l “\EFI\ubuntu\shimx64.efi” -d /dev/nvme0nX -p Y
Where X is drive & Y is partition.

Ubuntu is default that Ubuntu installer uses, but I typically use version like noble by changing /etc/default/grub and distributor setting.

This is why I prefer a new clean install. With new hardware installing 24.04 would probably have been better for better support from newer kernel & drivers. And then grub is installed. It is often quicker to cp or rsync /home after install and update from your normal backup for list of installed apps.

Thank you for all the replies. I had already tried some of the suggestions with no luck. Eventually I downloaded Boot-Repair from a live session and was able to then boot from GRUB.

So a new issue. Now that I can boot into Ubuntu, I decided to reboot & choose Windows just to check. The GRUB screen blanked out & then reappeared. This happened whenever I chose the Windows option (GRUB "Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi’). In the BIOS, the boot order shows Windows Boot Manager first & no listing for Ubuntu (on my previous laptop I could choose “ubuntu” as the boot option), yet GRUB shows up on booting. I can find no such choice in the add boot option section. In addition, the bios is set for RAID. Since I only have one drive I changed it to AHCI after getting my original problem solved. Booting into Ubuntu was no problem. I thought that might be the problem wiith booting into Windows, so I changed it back to RAID & tried again with the same result as above.

Does anyone have any suggestions?

Grub only boots working Windows. You should always be able to boot Windows directly from UEFI boot menu, F12.

But changing from RAID to AHCI means you need to add AHCI drivers into Windows. My Dell worked with RAID on, and did not need change to AHCI as it only has one NVMe drive and Ubuntu installed Intel® VMD driver. from lspci & SATA mode:
Kernel modules: vmd, ahci

Ubuntu installation on computers with Intel(R) RST enabled &
Intel RST

Windows AHCI instructions - some have found safeboot method better
https://www.dell.com/community/Laptops-General-Read-Only/Dell-M-2-FAQ-regarding-AHCI-vs-RAID-ON-Storage-Drivers-M-2-Lanes/td-p/5072571 &
https://askubuntu.com/questions/1233623/workaround-to-install-ubuntu-20-04-with-intel-rst-systems &
But if you do a safe boot first to update Windows, then boot to UEFI/BIOS and change to AHCI and finally boot normally, it works

Thank you for your quick reply.

I’m not sure what you mean by “working Windows”. It came pre-installed & booted fine. I needed to use Boot-Repair to get GRUB installed after transferring my partitions from a HDD & was able to boot into Ubuntu from the GRUB menu. The Windows boot manager was detected & added to the GRUB menu. At that time the BIOS was still set to RAID. After some searching I change it to AHCI as I have only 1 SSD. Are you saying that changing to AHCI borked Windows? Wouldn’t changing back to RAID solve the problem? As it is, Windows doesn’t boot at all. Booting into the BIOS (F2 or F12) & going into boot sequence shows Windows Boot Manager first followed by something like NVME Raid… & then UEFI Firmware settings. Nothing for Ubuntu. Since I can’t boot into Windows, I can’t try the safe boot option. And since Windows worked with RAID on & Ubuntu does too, I don’t need to change to AHCI if it’s not necessary.

Working Windows means, not chkdsk required, not hibernation nor fast startup which sets hibernation flag, and no bitlocker. Windows updates like to turn some of these settings back on.

I have not dealt with RAID issue. But thought some of the links had different ways to solve it. And one was turn RAID back on, boot Windows & change settings from there.

My Dell now has an external SSD for Kuubuntu. And if not plugged in, it boots Windows and if plugged in it boots Kubuntu. I expected with external, and unplugging & replugging it in would require F12 to choose grub/Ubuntu or perhaps the drive by name,label like booting live installer.

I ran Boot-Repair again but did not commit any changes, just saved the info file:

boot-repair-4ppa2081 [20250120_1854]

============================== Boot Info Summary ===============================

=> No boot loader is installed in the MBR of /dev/nvme0n1.

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/bkpbootx64.efi /efi/Boot/bootx64.efi 
                   /efi/ubuntu/grubx64.efi /efi/ubuntu/grub.cfg 
                   /efi/dell/SOS/bootmgfw.efi /efi/dell/SOS/bootmgr.efi 
                   /efi/dell/SOS/bootx64.efi 
                   /efi/dell/SOS/SecureBootRecovery.efi 
                   /efi/Microsoft/Boot/bkpbootmgfw.efi 
                   /efi/Microsoft/Boot/bootmgfw.efi 
                   /efi/Microsoft/Boot/bootmgr.efi 
                   /efi/Microsoft/Boot/bootx64.efi 
                   /efi/Microsoft/Boot/SecureBootRecovery.efi

nvme0n1p2: _____________________________________________________________________

File system:       
Boot sector type:  -
Boot sector info: 

nvme0n1p3: _____________________________________________________________________

File system:       ntfs
Boot sector type:  NTFS
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  Windows 10 or 11
Boot files:        /Windows/System32/winload.exe

nvme0n1p4: _____________________________________________________________________

File system:       ntfs
Boot sector type:  NTFS
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  
Boot files:        

nvme0n1p5: _____________________________________________________________________

File system:       ntfs
Boot sector type:  NTFS
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  
Boot files:        

nvme0n1p6: _____________________________________________________________________

File system:       ntfs
Boot sector type:  NTFS
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  
Boot files:        

nvme0n1p7: _____________________________________________________________________

File system:       ntfs
Boot sector type:  NTFS
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  
Boot files:        

nvme0n1p8: _____________________________________________________________________

File system:       ext4
Boot sector type:  -
Boot sector info: 
Operating System:  Ubuntu 22.04.5 LTS
Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub

nvme0n1p9: _____________________________________________________________________

File system:       ext4
Boot sector type:  -
Boot sector info: 
Operating System:  
Boot files:        

sda: ___________________________________________________________________________

File system:       iso9660
Boot sector type:  Grub2 (v1.99-2.00)
Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of 
                   sda and looks at sector 0 of the same hard drive for 
                   core.img, but core.img can not be found at this 
                   location.
Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.

================================ 2 OS detected =================================

OS#1 (linux): Ubuntu 22.04.5 LTS on nvme0n1p8
OS#2 (windows): Windows 10 or 11 on nvme0n1p3

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Intel Corporation from Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 22.04.5 LTS, jammy, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 1.16.0(1.16) from Dell Inc.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0006,0003,0000
Boot0000* UEFI HTTPs Boot PciRoot(0x0)/Pci(0x1f,0x6)/MAC(000000000000,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N…YM…R,Y.
Boot0001* UEFI USB Flash Disk PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,GPT,389fbc94-38b6-4d1a-8966-87488db3d5a5,0x8dc6a4,0x2758)/File(\EFI\Boot\BootX64.efi)N…YM…R,Y.
Boot0003* UEFI RST P41PL NVMe SOLIDIGM 1024GB BTEH44560EN01P0G HD(1,GPT,d8283cd5-0751-4e2e-9c10-29dfd834202d,0x800,0xc8000)/File(\EFI\Boot\BootX64.efi)N…YM…R,Y.
Boot0006* Windows Boot Manager HD(1,GPT,d8283cd5-0751-4e2e-9c10-29dfd834202d,0x800,0xc8000)/File(\EFI\Microsoft\Boot\bootmgfw.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.}……

a1da253696a304dce6b4668b70151c0e nvme0n1p1/Boot/bkpbootx64.efi
a1da253696a304dce6b4668b70151c0e nvme0n1p1/Boot/bootx64.efi
a1da253696a304dce6b4668b70151c0e nvme0n1p1/ubuntu/grubx64.efi
960245e0c7098f964cbc215fce266067 nvme0n1p1/dell/SOS/bootmgfw.efi
6f1c3c6701144a1070e08fab3e2debdf nvme0n1p1/dell/SOS/bootmgr.efi
960245e0c7098f964cbc215fce266067 nvme0n1p1/dell/SOS/bootx64.efi
0dddc55d593fc13c3ab3cb750e1a188a nvme0n1p1/dell/SOS/SecureBootRecovery.efi
b2a346c08d9616e760ec20544fb60c41 nvme0n1p1/Microsoft/Boot/bkpbootmgfw.efi
a1da253696a304dce6b4668b70151c0e nvme0n1p1/Microsoft/Boot/bootmgfw.efi
f4ddc3c1851f57d4257e3964ec281fc9 nvme0n1p1/Microsoft/Boot/bootmgr.efi
a1da253696a304dce6b4668b70151c0e nvme0n1p1/Microsoft/Boot/bootx64.efi (is grub)
0dddc55d593fc13c3ab3cb750e1a188a nvme0n1p1/Microsoft/Boot/SecureBootRecovery.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1 : is-GPT, no-BIOSboot, has—ESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
nvme0n1p3 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p4 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p5 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p6 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p7 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p8 : is-os, 64, apt-get, signed grub-efi , grub2, grub-install, grubenv-ok, update-grub, end-after-100GB
nvme0n1p9 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB

Partitions info (2/3): _________________________________________________________

nvme0n1p1 : is—ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat
nvme0n1p3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
nvme0n1p4 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot, ntfs
nvme0n1p5 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot, ntfs
nvme0n1p6 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot, ntfs
nvme0n1p7 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
nvme0n1p8 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4
nvme0n1p9 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4

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, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, nvme0n1
nvme0n1p4 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, nvme0n1
nvme0n1p5 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, nvme0n1
nvme0n1p6 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, nvme0n1
nvme0n1p7 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, nvme0n1
nvme0n1p8 : not–sepboot, with-boot, fstab-without-boot, not-sep-usr, with–usr, fstab-without-usr, std-grub.d, nvme0n1
nvme0n1p9 : 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: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk identifier: 09D517B1-8FD6-418C-A7BB-A8AAB04C15D8
Start End Sectors Size Type
nvme0n1p1 2048 821247 819200 400M EFI System
nvme0n1p2 821248 1083391 262144 128M Microsoft reserved
nvme0n1p3 1083392 308283391 307200000 146.5G Microsoft basic data
nvme0n1p4 1956177920 1958205439 2027520 990M Windows recovery environment
nvme0n1p5 1958205440 1997463551 39258112 18.7G Windows recovery environment
nvme0n1p6 1997465600 2000408575 2942976 1.4G Windows recovery environment
nvme0n1p7 308283392 944369663 636086272 303.3G Microsoft basic data
nvme0n1p8 944369664 1294454783 350085120 166.9G Linux filesystem
nvme0n1p9 1294454784 1956177919 661723136 315.5G Linux filesystem
Partition table entries are not in disk order.
Disk sda: 29.44 GiB, 31609323520 bytes, 61736960 sectors
Disk identifier: 389FBC94-38B6-4D1A-8964-87488DB3D5A5
Start End Sectors Size Type
sda1 64 9291427 9291364 4.4G Microsoft basic data
sda2 9291428 9301499 10072 4.9M EFI System
sda3 9301500 9302099 600 300K Microsoft basic data
sda4 9306112 61736896 52430785 25G Linux filesystem

parted -lm (filtered): _________________________________________________________

sda:31.6GB:scsi:512:512:gpt:USB Flash Disk:;
1:32.8kB:4757MB:4757MB::ISO9660:hidden, msftdata;
2:4757MB:4762MB:5157kB::Appended2:boot, esp;
3:4762MB:4763MB:307kB::Gap1:hidden, msftdata;
4:4765MB:31.6GB:26.8GB:ext4::;
nvme0n1:1024GB:nvme:512:512:gpt:P41PL NVMe SOLIDIGM 1024GB:;
1:1049kB:420MB:419MB:fat32:EFI system partition:boot, esp;
2:420MB:555MB:134MB::Microsoft reserved partition:msftres;
3:555MB:158GB:157GB:ntfs:Basic data partition:msftdata;
7:158GB:484GB:326GB:ntfs:Basic data partition:msftdata;
8:484GB:663GB:179GB:ext4:root:;
9:663GB:1002GB:339GB:ext4:home:;
4:1002GB:1003GB:1038MB:ntfs::hidden, diag;
5:1003GB:1023GB:20.1GB:ntfs::hidden, diag;
6:1023GB:1024GB:1507MB:ntfs::hidden, diag;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda iso9660 2024-09-11-14-37-52-00 Ubuntu 22.04.5 LTS amd64
├─sda1 iso9660 2024-09-11-14-37-52-00 389fbc94-38b6-4d1a-8965-87488db3d5a5 Ubuntu 22.04.5 LTS amd64 ISO9660
├─sda2 vfat 4721-D641 389fbc94-38b6-4d1a-8966-87488db3d5a5 ESP Appended2
├─sda3 389fbc94-38b6-4d1a-8967-87488db3d5a5 Gap1
└─sda4 ext4 5ff9e41f-ebce-4ea6-8b3f-199b03fe939a e1d75adf-86e8-f344-8c59-fe86163009f7 writable
nvme0n1
├─nvme0n1p1 vfat 12B3-9F55 d8283cd5-0751-4e2e-9c10-29dfd834202d ESP EFI system partition
├─nvme0n1p2 4b671b38-cf3b-4f77-88bd-bae2f6375aab Microsoft reserved partition
├─nvme0n1p3 ntfs 20A4D3FBA4D3D180 e8152e41-d5b2-4023-8bff-fab90cf0c023 OS Basic data partition
├─nvme0n1p4 ntfs EC4AFE6E4AFE34C4 0ba5e8bf-7a9c-4774-b437-a3ac80d128e5 WINRETOOLS
├─nvme0n1p5 ntfs B2CAFED2CAFE91B9 9334baa3-213f-483b-885f-4ba90863dd60 Image
├─nvme0n1p6 ntfs C8288A91288A7DE6 8c03271a-04ab-4520-b04c-b64804a2a48d DELLSUPPORT
├─nvme0n1p7 ntfs 0894E1DA94E1C9F0 aa4c945f-ed18-4129-9692-65ffb4af6d02 Share Basic data partition
├─nvme0n1p8 ext4 b91e31b8-e61f-4428-afa9-5ff99f9abadc b7a12578-96e9-4860-8a36-e1095b9acaeb root
└─nvme0n1p9 ext4 2f9d6e79-e66f-49c3-a713-ac56c99214e2 e70820ca-29aa-423f-bdfa-2ef2a87de108 home

Mount points (filtered): _______________________________________________________

                                                           Avail Use% Mounted on

/dev/nvme0n1p1 243.7M 38% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p3 75.9G 48% /mnt/boot-sav/nvme0n1p3
/dev/nvme0n1p4 436.3M 56% /mnt/boot-sav/nvme0n1p4
/dev/nvme0n1p5 134.5M 99% /mnt/boot-sav/nvme0n1p5
/dev/nvme0n1p6 495.5M 66% /mnt/boot-sav/nvme0n1p6
/dev/nvme0n1p7 98.1G 68% /mnt/boot-sav/nvme0n1p7
/dev/nvme0n1p8 89.2G 40% /mnt/boot-sav/nvme0n1p8
/dev/nvme0n1p9 118.4G 57% /mnt/boot-sav/nvme0n1p9
/dev/sda1 0 100% /cdrom
efivarfs 199.4K 53% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/nvme0n1p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme0n1p3 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p5 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p6 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p7 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p8 ext4 rw,relatime
/dev/nvme0n1p9 ext4 rw,relatime
/dev/sda1 iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

=================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) ===================

search.fs_uuid b91e31b8-e61f-4428-afa9-5ff99f9abadc root
set prefix=($root)‘/boot/grub’
configfile $prefix/grub.cfg

=================== nvme0n1p8/boot/grub/grub.cfg (filtered) ====================

Ubuntu b91e31b8-e61f-4428-afa9-5ff99f9abadc
Windows Boot Manager (on nvme0n1p1) osprober-efi-12B3-9F55

END /etc/grub.d/30_os-prober

UEFI Firmware Settings uefi-firmware

END /etc/grub.d/30_uefi-firmware

======================== nvme0n1p8/etc/fstab (filtered) ========================

/ was on /dev/sda7 during installation → /dev/nvme0n1p8 on ssd

UUID=b91e31b8-e61f-4428-afa9-5ff99f9abadc / ext4 discard,noatime,nodiratime,errors=remount-ro 0 1

/boot/efi was on /dev/sda1 during installation

/home was on /dev/sda8 during installation → /dev/nvme0n1p9 on ssd

UUID=2f9d6e79-e66f-49c3-a713-ac56c99214e2 /home ext4 discard,noatime,nodiratime,defaults 0 2
/swapfile none swap sw 0 0
//192.168.1.2/Data /media/Barsoom_Data cifs auto,user,exec,rw,x-systemd.automount,username=jeff,password****[filtered]****
//192.168.1.2/Media /media/Barsoom_Media cifs auto,user,exec,rw,x-systemd.automount,username=jeff,password****[filtered]****
//192.168.1.2/Media2 /media/Barsoom_Media2 cifs auto,user,exec,rw,x-systemd.automount,username=jeff,password****[filtered]****
//192.168.1.1/g/ /mnt/XDrive cifs auto,user,nofail,exec,rw,x-systemd.automount,vers=1.0,uid=1000,gid=1000,file_mode=0777,dir_mode=0777,_netdev,iocharset=utf8, 0 0
tmpfs /var/spool tmpfs defaults,size=512M,mode=1777 0 0
/dev/disk/by-id/usb-SanDisk_Cruzer_Glide_4C530001291111104540-0:0-part1 /mnt/usb-SanDisk_Cruzer_Glide_4C530001291111104540-0:0-part1 auto nosuid,nodev,nofail,noauto,rw,x-gvfs-show 0 0
/dev/nvme0n1p7 /media/jeff/Share ntfs defaults,rw,windows_names,cache=loose,fsc,users,locale=en_US.utf8,uid=1000,gid=100 0 0
UUID=12B3-9F55 /boot/efi vfat defaults 0 1

==================== nvme0n1p8/etc/default/grub (filtered) =====================

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4”
GRUB_CMDLINE_LINUX=“”
GRUB_DISABLE_OS_PROBER=false

================= nvme0n1p8: Location of files loaded by Grub ==================

       GiB - GB             File                                 Fragment(s)

471.754219055 = 506.542235648 boot/grub/grub.cfg 1
487.957263947 = 523.940122624 boot/vmlinuz 2
469.251140594 = 503.854575616 boot/vmlinuz-5.15.0-130-generic 3
540.176013947 = 580.009578496 boot/vmlinuz-6.8.0-50-generic 2
487.957263947 = 523.940122624 boot/vmlinuz-6.8.0-51-generic 2
469.251140594 = 503.854575616 boot/vmlinuz.old 3
489.677730560 = 525.787459584 boot/initrd.img 4
458.919918060 = 492.761509888 boot/initrd.img-5.15.0-130-generic 8
462.552730560 = 496.662212608 boot/initrd.img-6.8.0-50-generic 10
489.677730560 = 525.787459584 boot/initrd.img-6.8.0-51-generic 4
458.919918060 = 492.761509888 boot/initrd.img.old 8

=================== nvme0n1p8: ls -l /etc/grub.d/ (filtered) ===================

-rwxr-xr-x 1 root root 18683 Dec 18 2022 10_linux
-rwxr-xr-x 1 root root 43031 Dec 18 2022 10_linux_zfs
-rwxr-xr-x 1 root root 14387 Dec 18 2022 20_linux_xen
-rwxr-xr-x 1 root root 13369 Dec 18 2022 30_os-prober
-rwxr-xr-x 1 root root 1372 Dec 18 2022 30_uefi-firmware
-rwxr-xr-x 1 root root 214 Dec 18 2022 40_custom
-rwxr-xr-x 1 root root 215 Dec 18 2022 41_custom

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would reinstall the grub-efi of
nvme0n1p8,
using the following options: nvme0n1p1/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file restore-efi-backups

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your UEFI firmware boot on the Ubuntu 22.04.5 LTS entry (nvme0n1p1/efi//grub.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI*\grub*.efi (**** will be updated in the final message)

Hope somebody can make sense of this. I did notice advanced options to repair Windows boot, but don’t want to touch anything without more knowlegable advice.

[& How do you attach a file here rather than paste the contents?]

Boot-Repair normally gives you a link to a pastebin site. Then you just need to post the link.

Boot-Repair is for fixing Linux systems. It can make very few if any Windows fixes.

You need to fix Windows so it directly boots from UEFI boot menu.
Report shows Windows entry in UEFI 0006 with correct partUUID/GUID.

Also, but not related to your issues.
There’s no reason to use BOTH noatime and nodiratime, using noatime implies nodiratime.

Do you have an option to enable or boot into an EFI Shell?

Thanks @oldfred…It’s frustrating because the problem only cropped up after I used Boot-Repair to get GRUB installed. I had booted into a live Ubuntu session & used GParted to shrink the installed Windows partition. I then rebooted to ensure I could boot into Windows, which I could. I then copied my Ubuntu partitions & a ntfs data partition to the ssd. On my old laptop GRUB installled an “ubuntu” boot option which doesn’t appear (that I can discover) on the new laptop. Windows Boot Manager is the first option. Yet the GRUB menu shows up on boot. This isn’t mission critical. I do most of my work on Ubuntu & use Windows as a back-up incase something in Ubuntu goes wrong or for a Windows specific program. I just don’t want to mess up & have to start all over again!

If first UEFI entry does not work, it goes to next one. So is Windows boot now broken from UEFI boot. You may need to restore a Windows UEFI boot entry. And best to use Windows tools for Windows. And better to use Windows to shrink NTFS partitions.
How did you copy partitions? The gpt partitioning requires GUIDs in primary partition table, partition & backup partition table to be in sync. What does this show? If no errors then ok.
sudo gdisk -l /dev/nvme0n1

Thinking that Windows somehow got borked, I ran the Dell recovery tool from the BIOS. It did find an issue, but on rebooting went straight to Windows. So that problem got fixed. I re-ran Boot-Repair from a live Ubuntu session, but that didn’t work; booted into Windows again.

I have manged to fix it however! In the Boot Options section, click Add Boot Option. Then Choose File. A list appears. The first option is EFI. Clicking on that opens the directory and “ubuntu” is one of the choices; opening that shows grubxf64.efi. Double-click that, give it a name and submit; commit the changes and reboot. Sure isn’t very intuitive as how to do these things!

As for how I copied the partitions-- I removed my HDD from my old laptop & put it in a USB case; booted a live Ubuntu session; ran GParted; created the partitions; connected the external drive & copied the partitons (resized as necessary) to the new drive. All partition UUIDS were transferred.

Thank you for all your suggestions!

I had to run Dell recovery image after Dell repairs.
I think Dell put a new motherboard in and did not update the Windows product code, so Windows did not recognize it. Ubuntu booted, Windows did not and no repairs worked.
I ended up using Dell image restore & then Windows worked & Ubuntu was erased. System was just like when I purchased it.

:roll_eyes: Sorry to hear that. Always problems!