Universal Blue•5d ago

Bazzite install removed Windows entry

Recently reinstalled Bazzite along side a fresh Windows 10 install as part of some testing and I noticed that after the bazzite install I no longer see my Windows entry in grub or my bios, but I still do see the drive with all files intact in the file manager. The two operating systems are on different drives, Windows on an nvme and Bazzite on an ssd. When I try to run ujust regenerate-grub I get the below error:

/usr/bin/grub2-probe: error: failed to get canonical path of `composefs'.
error: Recipe `regenerate-grub` failed with exit code 1

/usr/bin/grub2-probe: error: failed to get canonical path of `composefs'.
error: Recipe `regenerate-grub` failed with exit code 1

Any help would be greatly appreciated, thank you.

7 Replies

dreamyuki•5d ago

regenerate grub is no longer works with Fedora 42 since grub2-mkconfig can't find the real /

wolfyreload•5d ago

try run efibootmgr and see if you can see a Windows EFI entry. This is the output I get. In my case Boot0000 is Windows

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0001
Boot0000* Windows Boot Manager  HD(1,GPT,87b2127f-77ef-4d7d-bbf7-7adc688d4956,0x800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e44.....
Boot0001* bazzite       HD(1,GPT,87b2127f-77ef-4d7d-bbf7-7adc688d4956,0x800,0x82000)/\EFI\fedora\shimx64.efi

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0001
Boot0000* Windows Boot Manager  HD(1,GPT,87b2127f-77ef-4d7d-bbf7-7adc688d4956,0x800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e44.....
Boot0001* bazzite       HD(1,GPT,87b2127f-77ef-4d7d-bbf7-7adc688d4956,0x800,0x82000)/\EFI\fedora\shimx64.efi

cerealfordinnerOP•5d ago

Thank you both, yeah it's weird I dont' see it here.

cerealfordinner@fedora:~$ efibootmgr
BootCurrent: 0009
Timeout: 1 seconds
BootOrder: 0009,0001,0008
Boot0001* Fedora
    HD(1,GPT,b28dfa0b-cb71-4f7a-a6fa-c0f147bed800,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
Boot0008* UEFI:  Patriot Memory PMAP, Partition 2    PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(4,0)/HD(2,MBR,0xf4651817,0xeb00000,0x10000)0000424f
Boot0009* Fedora    HD(1,GPT,b28dfa0b-cb71-4f7a-a6fa-c0f147bed800,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f

cerealfordinner@fedora:~$ efibootmgr
BootCurrent: 0009
Timeout: 1 seconds
BootOrder: 0009,0001,0008
Boot0001* Fedora
    HD(1,GPT,b28dfa0b-cb71-4f7a-a6fa-c0f147bed800,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
Boot0008* UEFI:  Patriot Memory PMAP, Partition 2    PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(4,0)/HD(2,MBR,0xf4651817,0xeb00000,0x10000)0000424f
Boot0009* Fedora    HD(1,GPT,b28dfa0b-cb71-4f7a-a6fa-c0f147bed800,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f

wolfyreload•5d ago

please run sudo fdisk -l and check if you have an EFI partition for Windows, you should have something like this

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048    206847    204800   100M EFI System
/dev/sdb2     206848    239615     32768    16M Microsoft reserved
/dev/sdb3     239616 498800639 498561024 237.7G Microsoft basic data

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048    206847    204800   100M EFI System
/dev/sdb2     206848    239615     32768    16M Microsoft reserved
/dev/sdb3     239616 498800639 498561024 237.7G Microsoft basic data

cerealfordinnerOP•5d ago

Okay weird so I somehow deleted the EFI partition on my Windows drive during the install? I'm not sure what I could have done that would impact that:

Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000BX500SSD1 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B46BE0A1-D809-43AA-84BD-3AB8FD7A53E7

Device       Start        End    Sectors   Size Type
/dev/sdb1     2048    1230847    1228800   600M EFI System
/dev/sdb2  1230848    3327999    2097152     1G Linux extended boot
/dev/sdb3  3328000 1953523711 1950195712 929.9G Linux filesystem


Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 990 PRO 1TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 38354026-2334-4FAC-9353-F3650955A740

Device         Start        End    Sectors   Size Type
/dev/nvme0n1p1  2048      34815      32768    16M Microsoft reserved
/dev/nvme0n1p2 34816 1953523711 1953488896 931.5G Microsoft basic data

Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000BX500SSD1 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B46BE0A1-D809-43AA-84BD-3AB8FD7A53E7

Device       Start        End    Sectors   Size Type
/dev/sdb1     2048    1230847    1228800   600M EFI System
/dev/sdb2  1230848    3327999    2097152     1G Linux extended boot
/dev/sdb3  3328000 1953523711 1950195712 929.9G Linux filesystem


Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 990 PRO 1TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 38354026-2334-4FAC-9353-F3650955A740

Device         Start        End    Sectors   Size Type
/dev/nvme0n1p1  2048      34815      32768    16M Microsoft reserved
/dev/nvme0n1p2 34816 1953523711 1953488896 931.5G Microsoft basic data

wolfyreload•5d ago

I'd guess this happened. Did you have both drives plugged in while you installed Windows? I suspect that Windows probably put it's EFI folder on /dev/sdb instead of /dev/nvme0n1 since it was the first drive that it saw. Then when you installed Bazzite on /dev/sdb you cleared the drive removing the Windows EFI folder. I did that a few years ago. Installed Windows, installed Pop_OS and I formatted the one drive. Windows has just it's 100MB EFI folder on the wrong drive...

cerealfordinnerOP•4d ago

That could have definitely been it, at least I have something to go off of now so I appreciate it, I'll take a look at what I need to restore that Alright so I was able to get that EFI partition rebuilt, but it looks like I'm running into the same issue:

Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 990 PRO 1TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 38354026-2334-4FAC-9353-F3650955A740

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048      34815      32768    16M Microsoft reserved
/dev/nvme0n1p2      34816 1952909311 1952874496 931.2G Microsoft basic data
/dev/nvme0n1p3 1952909312 1953523711     614400   300M EFI System

Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 990 PRO 1TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 38354026-2334-4FAC-9353-F3650955A740

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048      34815      32768    16M Microsoft reserved
/dev/nvme0n1p2      34816 1952909311 1952874496 931.2G Microsoft basic data
/dev/nvme0n1p3 1952909312 1953523711     614400   300M EFI System

cerealfordinner@bazzite:~$ ujust regenerate-grub
/usr/bin/grub2-probe: error: failed to get canonical path of `composefs'.
error: Recipe `regenerate-grub` failed with exit code 1

cerealfordinner@bazzite:~$ ujust regenerate-grub
/usr/bin/grub2-probe: error: failed to get canonical path of `composefs'.
error: Recipe `regenerate-grub` failed with exit code 1

Gaming

Programming

Bazzite install removed Windows entry

Did you find this page helpful?