GRUB not working properly after installing Ubuntu 24.04.1 LTS with Windows 11

Hi,
I have installed Ubuntu 24.04.1 LTS in dual boot with Windows 11 on a portable computer MSI TITAN GT77. I have followed the installation process described here. The installation process seemed to work properly, but after restart, I had no choice between Windows and Ubuntu: when Ubuntu is selected in the boot menu, at the start there is no way to choose Windows. To use Windows, I need to change the order in the “UEFI Hard Disk Drive BBS Priorities” of the BIOS.

I found on internet that the problem could come from “GRUB”. I tried to use the “Boot-Repair” tool from the bootable USB key I used for the initial installation (created with Rufus). I launched in a terminal the following command lines to install “Boot-Repair”:
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair
Then I launched it (command “boot-repair” in the terminal) and let the default options.
Unfortunately, it did not work (I tried it twice). And now, I cannot start at all Ubuntu. Since I am not at all an expert of Ubuntu, I would be really grateful if someone could help me to solve this problem.

Hereafter is the message returned by the boot-repair tool. There are some suggestions at the end of this file, but I have not understood how to apply them.

boot-repair-4ppa2081 [20250103_2211]

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

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

sda1: __________________________________________________________________________

File system:       vfat
Boot sector type:  FAT32
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  
Boot files:        /boot/grub/grub.cfg /efi/boot/bootx64.efi 
                   /efi/boot/grubx64.efi /efi/boot/mmx64.efi

md/imsm0: ______________________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 

md/RAID0IMSVolume_0: ___________________________________________________________

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

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

OS#1 (linux): Ubuntu 24.04.1 LTS on md126p8
OS#2 (windows): Windows 10 or 11 on md126p3

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

CPU architecture: 64-bit
Video: AD104M [GeForce RTX 4080 Max-Q / Mobile] Raptor Lake-S UHD Graphics from NVIDIA Corporation Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 24.04.1 LTS, noble, x86_64)

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

BIOS/UEFI firmware: E17Q2IMS.102(1.2) from American Megatrends International, LLC.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot enabled according to mokutil - Please report this message to boot.repair@gmail.com.
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0002,0000
Boot0000* Windows Boot Manager HD(1,GPT,49d74213-8900-427e-89f0-5dd30632eb5f,0x800,0x96000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000031000100000010000000040000007fff0400
Boot0002* Ubuntu HD(7,GPT,07cbaacd-fcfc-46c5-b1eb-ac0cc87d3310,0x159e85800,0x219800)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* UEFI: Corsair Voyager 1100, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(7,0)/HD(1,GPT,06b5e068-e90f-4f04-a308-25bd6151ef99,0x800,0x1df2ed0)0000424f

39bc76ff6662f4fbe9aa116e4c997b41 md126p7/BOOT/fbx64.efi
4ba5a5aad43c197e9fb58b76b404d287 md126p7/BOOT/mmx64.efi
66f69798ad23240e43b7ba0044a914c4 md126p7/ubuntu/grubx64.efi
4ba5a5aad43c197e9fb58b76b404d287 md126p7/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e md126p7/ubuntu/shimx64.efi
07e25dcaf57c776875f78fa36827c58e md126p7/BOOT/BOOTX64.efi
17b3fa127f74e0189c6192a80c3fe28f md126p1/Boot/bootx64.efi
23837e7f81b5b729c2cc673d3da56273 md126p1/Microsoft/Boot/SecureBootRecovery.efi
17b3fa127f74e0189c6192a80c3fe28f md126p1/Microsoft/Boot/bootmgfw.efi
3134a3c759cae87284e8e37d6b841318 md126p1/Microsoft/Boot/bootmgr.efi

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

Disks info: ____________________________________________________________________

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

Partitions info (1/3): _________________________________________________________

md126p7 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
md126p5 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
md126p3 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
md126p1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
md126p8 : is-os, 64, apt-get, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
md126p6 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
md126p4 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB

Partitions info (2/3): _________________________________________________________

md126p7 : is—ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat
md126p5 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
md126p3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
md126p1 : is—ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat
md126p8 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4
md126p6 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ntfs
md126p4 : is—ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat

Partitions info (3/3): _________________________________________________________

md126p7 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
md126p5 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
md126p3 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
md126p1 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
md126p8 : not–sepboot, with-boot, fstab-without-boot, not-sep-usr, with–usr, fstab-without-usr, no–grub.d, sda
md126p6 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
md126p4 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda

fdisk -l (filtered): ___________________________________________________________

Disk nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk identifier: 0x00000000
Boot Start End Sectors Size Id Type
nvme0n1p1 1 4294967295 4294967295 2T ee GPT
Disk nvme1n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk md126: 3.73 TiB, 4096811597824 bytes, 8001585152 sectors
Disk identifier: E3AB6275-2ACD-4CC4-96CD-41D4A9918921
Start End Sectors Size Type
md126p1 2048 616447 614400 300M EFI System
md126p2 616448 878591 262144 128M Microsoft reserved
md126p3 878592 5801164799 5800286208 2.7T Microsoft basic data
md126p4 5801164800 5803366399 2201600 1G EFI System
md126p5 7948648448 7950491647 1843200 900M Windows recovery environment
md126p6 7950491648 8001583103 51091456 24.4G Windows recovery environment
md126p7 5803366400 5805567999 2201600 1G EFI System
md126p8 5805568000 7948648447 2143080448 1021.9G Linux filesystem
Partition table entries are not in disk order.
Disk sda: 14.98 GiB, 16079781888 bytes, 31405824 sectors
Disk identifier: 5E5062A3-9420-4CE7-AB01-9EC0BCEF63DA
Start End Sectors Size Type
sda1 2048 31405775 31403728 15G Microsoft basic data

parted -lm (filtered): _________________________________________________________

sda:16.1GB:scsi:512:512:gpt:Corsair Voyager:;
1:1049kB:16.1GB:16.1GB:fat32:Main Data Partition:msftdata;
nvme0n1:2048GB:nvme:512:512:unknown:SAMSUNG MZVL22T0HBLB-00B00:;
md126:4097GB:md:512:512:gpt:Linux Software RAID Array:;
1:1049kB:316MB:315MB:fat32:EFI system partition:boot, esp;
2:316MB:450MB:134MB::Microsoft reserved partition:msftres;
3:450MB:2970GB:2970GB:ntfs:Basic data partition:msftdata;
4:2970GB:2971GB:1127MB:fat32::boot, esp;
7:2971GB:2972GB:1127MB:fat32::boot, esp;
8:2972GB:4070GB:1097GB:ext4::;
5:4070GB:4071GB:944MB:ntfs:Basic data partition:hidden, diag, no_automount;
6:4071GB:4097GB:26.2GB:ntfs:Basic data partition:hidden, diag;
nvme1n1:2048GB:nvme:512:512:unknown:SAMSUNG MZVL22T0HBLB-00B00:;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
└─sda1 vfat DA8C-6615 06b5e068-e90f-4f04-a308-25bd6151ef99 UBUNTU 24_0 Main Data Partition
nvme0n1 isw_raid_member
├─md126
│ ├─md126p1 vfat 7E42-219B 49d74213-8900-427e-89f0-5dd30632eb5f SYSTEM EFI system partition
│ ├─md126p2 80bdc700-4e91-496b-915d-fc8b82f65c65 Microsoft reserved partition
│ ├─md126p3 ntfs 527042D27042BD0B bd98120d-3766-44e9-88d5-c40489eb4af2 Windows Basic data partition
│ ├─md126p4 vfat 06F8-6EC1 86885ade-e297-4cfd-ac68-fff91b2b8fb3
│ ├─md126p5 ntfs 1C5E43705E4341AE 25c2c9c1-46d8-422c-a7a3-6bda1589625e WinRE tools Basic data partition
│ ├─md126p6 ntfs 6860457A60454FCC d871fda5-8df1-4e8f-9857-c0e8ee24b6d4 BIOS_RVY Basic data partition
│ ├─md126p7 vfat DE65-93B7 07cbaacd-fcfc-46c5-b1eb-ac0cc87d3310
│ └─md126p8 ext4 9fc5100f-dbe3-48a7-afec-bb9cea97918d 523c8838-f154-46f7-975e-c3905d61a917
└─md127
nvme1n1 isw_raid_member
├─md126
│ ├─md126p1 vfat 7E42-219B 49d74213-8900-427e-89f0-5dd30632eb5f SYSTEM EFI system partition
│ ├─md126p2 80bdc700-4e91-496b-915d-fc8b82f65c65 Microsoft reserved partition
│ ├─md126p3 ntfs 527042D27042BD0B bd98120d-3766-44e9-88d5-c40489eb4af2 Windows Basic data partition
│ ├─md126p4 vfat 06F8-6EC1 86885ade-e297-4cfd-ac68-fff91b2b8fb3
│ ├─md126p5 ntfs 1C5E43705E4341AE 25c2c9c1-46d8-422c-a7a3-6bda1589625e WinRE tools Basic data partition
│ ├─md126p6 ntfs 6860457A60454FCC d871fda5-8df1-4e8f-9857-c0e8ee24b6d4 BIOS_RVY Basic data partition
│ ├─md126p7 vfat DE65-93B7 07cbaacd-fcfc-46c5-b1eb-ac0cc87d3310
│ └─md126p8 ext4 9fc5100f-dbe3-48a7-afec-bb9cea97918d 523c8838-f154-46f7-975e-c3905d61a917
└─md127

Mount points (filtered): _______________________________________________________

                    Avail Use% Mounted on

/dev/md126p1 261.9M 12% /mnt/boot-sav/md126p1
/dev/md126p3 808.4G 71% /mnt/boot-sav/md126p3
/dev/md126p4 1G 0% /mnt/boot-sav/md126p4
/dev/md126p5 85.5M 91% /mnt/boot-sav/md126p5
/dev/md126p6 750.8M 97% /mnt/boot-sav/md126p6
/dev/md126p7 1G 1% /mnt/boot-sav/md126p7
/dev/md126p8 937.2G 2% /mnt/boot-sav/md126p8
/dev/sda1 9.2G 39% /cdrom
efivarfs 67.3K 62% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/md126p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/md126p3 fuseblk ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/md126p4 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/md126p5 fuseblk ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/md126p6 fuseblk ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/md126p7 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/md126p8 ext4 rw,relatime,stripe=64
/dev/sda1 vfat ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

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

Try or Install Ubuntu
Ubuntu (safe graphics)
Boot from next volume
UEFI Firmware Settings
Test memory

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

       GiB - GB             File                                 Fragment(s)
        ?? = ??             boot/grub/grub.cfg                             1

=================== blkid (filtered) before raid activation ====================

/dev/nvme0n1: TYPE=“isw_raid_member”
/dev/nvme1n1: TYPE=“isw_raid_member”
/dev/sda1: LABEL=“UBUNTU 24_0” UUID=“DA8C-6615” BLOCK_SIZE=“512” TYPE=“vfat” PARTLABEL=“Main Data Partition” PARTUUID=“06b5e068-e90f-4f04-a308-25bd6151ef99”
/dev/md126p7: UUID=“DE65-93B7” BLOCK_SIZE=“512” TYPE=“vfat” PARTUUID=“07cbaacd-fcfc-46c5-b1eb-ac0cc87d3310”
/dev/md126p5: LABEL=“WinRE tools” BLOCK_SIZE=“512” UUID=“1C5E43705E4341AE” TYPE=“ntfs” PARTLABEL=“Basic data partition” PARTUUID=“25c2c9c1-46d8-422c-a7a3-6bda1589625e”
/dev/md126p3: LABEL=“Windows” BLOCK_SIZE=“512” UUID=“527042D27042BD0B” TYPE=“ntfs” PARTLABEL=“Basic data partition” PARTUUID=“bd98120d-3766-44e9-88d5-c40489eb4af2”
/dev/md126p1: LABEL=“SYSTEM” UUID=“7E42-219B” BLOCK_SIZE=“512” TYPE=“vfat” PARTLABEL=“EFI system partition” PARTUUID=“49d74213-8900-427e-89f0-5dd30632eb5f”
/dev/md126p8: UUID=“9fc5100f-dbe3-48a7-afec-bb9cea97918d” BLOCK_SIZE=“4096” TYPE=“ext4” PARTUUID=“523c8838-f154-46f7-975e-c3905d61a917”
/dev/md126p6: LABEL=“BIOS_RVY” BLOCK_SIZE=“512” UUID=“6860457A60454FCC” TYPE=“ntfs” PARTLABEL=“Basic data partition” PARTUUID=“d871fda5-8df1-4e8f-9857-c0e8ee24b6d4”
/dev/md126p4: UUID=“06F8-6EC1” BLOCK_SIZE=“512” TYPE=“vfat” PARTUUID=“86885ade-e297-4cfd-ac68-fff91b2b8fb3”
/dev/md126p2: PARTLABEL=“Microsoft reserved partition” PARTUUID=“80bdc700-4e91-496b-915d-fc8b82f65c65”

==================================== dmraid ====================================

dmraid -si -c
no block devices found
dmraid -ay:
no block devices found
dmraid -sa -c:
no block devices found

==================================== mdadm =====================================
mdadm --assemble --scan

mdadm --detail --scan
ARRAY /dev/md/imsm0 metadata=imsm UUID=e6a4cded:f379a8ce:a8b3e382:11b32573
ARRAY /dev/md/RAID0IMSVolume_0 container=/dev/md/imsm0 member=0 UUID=6dbb259b:039780d7:cea12b4b:43d99029
mount -t ntfs-3g -o remove_hiberfile /dev/md126p3 /mnt/boot-sav/md126p3

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of
md126p8,
using the following options: md126p7/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your UEFI firmware boot on the Ubuntu 24.04.1 LTS entry (md126p7/efi//shim.efi (**** will be updated in the final message) file) !

The boot files of [md126p7 (end>100GB)] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a ESP partition (FAT32, 100MB~250MB, start of the disk, boot flag). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot/efi partition:] option of [Boot Repair].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*\shim*.efi (**** will be updated in the final message)

you show RAID & UEFI Secure Boot on. We nee to be careful with your RAID as version of RAID makes a difference. Normally desktops do not have RAID, but servers do. But those with servers use software RAID nor “FakeRAID” provided by UEFI/BIOS. I do not know RAID, but if RAID 0, to give speed, you cannot separate drives without losing everything.
I do not know RAID, but you need good backups and cannot use many tools for standard installs.

Review I saw said expensive system, but blazingly fast. I then suspect RAID 0, which is not normally suggested and with NVMe drives may not add a lot to speed.

Do not use gparted on RAID.
http://www.howtoforge.com/how-to-resize-raid-partitions-shrink-and-grow-software-raid
Don’t bother with RAID 0 unless you have a specific need for speed without data redundancy, since if one drive goes out, you lose the whole array.

Normally Ubuntu/grub boot files are in Windows ESP - efi system partition, but you are showing a separate ESP for Ubuntu. On many systems that does not work.

Have you tried this? With os-prober on.
sudo update-grub
That often finds Windows entry and adds it to grub.
You can check if os-prober is on with:
cat /etc/default/grub
Will be either true or false:
GRUB_DISABLE_OS_PROBER=

Just a bit curious…?
You have two nvme disks in your PC, did you ever consider Windows 11 on one disk and Ubuntu 24.04 on the other disk?
Does RAID in a dual boot system provide any benefit?

1 Like

We have seen users with two RAID drives break RAID to make two separate drives. But if RAID 0, you have to backup Windows & totally reinstall it. If RAID 1, it should work with one drive, just reformatted. RAID is more for uptime, not backup.

What is reason for Ubuntu? Your hardware is highly optimized for Windows & Windows gaming.

Another alternative which I use, is to have (K)Ubuntu on an external drive. When I upgraded desktop with new NVMe drive, I put old M.2 SSD into an USB3 to M.2 adapter. Ended up needing for old laptop and now use it with newer laptop. But I do not game, just Internet, and desktop apps.

2 Likes

Thank you for your answers. I will need to take some time to better understand all this, since I am not expert about it.
To answer your questions:

  • I have had a look at the computer characteristics and for the disk reader, it is written “Intel RAID 0 Volume”.
  • When I look at the disk characteristics in Windows, there is just one global disk of 4 TB that is displayed (see image below) not 2 of 2TB each, so, even if there are 2 disks, I don’t see how I could affect one to Windows, and one to Ubuntu.
  • I use this computer for professional use, not at all for gaming. I needed a computer with good performances (CPU and a lot of RAM) and this one fitted my needs. Unfortunately, Windows does not work properly, that is why I would like to try using Ubuntu instead.

The reason you probably see it as only one global disk is because you are using RAID. The fdisk output from boot repair clearly shows you have 2 physical drives in addition to the usb of Ubuntu your are using.

/dev/nvme0n1: TYPE=“isw_raid_member”
/dev/nvme1n1: TYPE=“isw_raid_member”

I’ve never used RAID so have no advice but as pointed out above, you have multiple vfat and EFI partitions??

I don’t know why there are so many partitions, I just created one space of 1TB dedicated to Linux.