Sebastian Klausus

Hi Dave, I managed to get it work. Importing the nobara.grub.cfg added an entry but resulted in an error which is like this: BTRFS Subvol Support Is Active The path Prefix = /@ /@/boot/vmzlinuz not found I was always wondering about this "@" folder in front of root (/) and already assummed in my first post this is imporant. It turns out it is. I added rootflags=subvol=@ after I imported your file but this did not work but for the standard Fedora config using Partition UUID it worked. My working config...

Hi Dave, First I'm no expert at all. So bare with me. That said I think the information is in the grub2.cfg. There is a thing called blscfg (Boot Loader Specification Configuration) In the grub2.cfg itself it says: # The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries and # populates the boot menu. Please refer to the Boot Loader Specification documentation # for the files format: https://systemd.io/BOOT_LOADER_SPECIFICATION/. # The kernelopts variable should be defined...

Hi Dave, thanks for the support! I just sent the diagnostics and my grub2.cfg. When I import the grub2.cfg into grub2win only the Linux Mint menu entries are detected by grub2win but not Nobara. Nobara uses etx4 for boot and BTRFS for root and uses the subvol=@ in the grub2.cfg. Maybe that's why the standard configuration in grub2win does not work? if [ -z "${kernelopts}" ]; then set kernelopts="root=UUID=d73af0ff-2518-4af3-b36a-4307c85f87bf ro rootflags=subvol=@ quiet splash"

Could you resolve the issue? I have excatly the same using Nobara 39 (Which is Fedora under the hood). I useses ext 4 for boot and btrfs for root. I configured both accordingly in grub2win but then get this error during boot with grub2win. The original fedora bootloader can boot without issues. I did run the xxkernet.sh script without any errors. Any ideas how to resolve it are highly appreciated.