Another example: http://ubuntuforums.org/showpost.php?p=12198689&postcount=11
We can see the buggy entry created by os-prober:
### BEGIN /etc/grub.d/30_os-prober ### menuentry "Windows 7 (loader) (on /dev/sda3)" --class windows --class os { insmod part_gpt insmod ntfs set root='(hd0,gpt3)' search --no-floppy --fs-uuid --set=root 8A3A9F1B3A9F02FD chainloader +1 }
And the correct entries created by Boot-Repair:
### BEGIN /etc/grub.d/40_custom ### menuentry "Windows bootmgfw.efi, generated by Boot-Repair" { search --fs-uuid --no-floppy --set=root 18FE-69D8 chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi }
menuentry "Windows memtest.efi, generated by Boot-Repair" { search --fs-uuid --no-floppy --set=root 18FE-69D8 chainloader (${root})/EFI/Microsoft/Boot/memtest.efi }
menuentry "Boot bootx64.efi, generated by Boot-Repair" { search --fs-uuid --no-floppy --set=root 18FE-69D8 chainloader (${root})/EFI/Boot/bootx64.efi }
Another example: ubuntuforums. org/showpost. php?p=12198689& postcount= 11
http://
We can see the buggy entry created by os-prober:
### BEGIN /etc/grub. d/30_os- prober ###
menuentry "Windows 7 (loader) (on /dev/sda3)" --class windows --class os {
insmod part_gpt
insmod ntfs
set root='(hd0,gpt3)'
search --no-floppy --fs-uuid --set=root 8A3A9F1B3A9F02FD
chainloader +1
}
And the correct entries created by Boot-Repair:
### BEGIN /etc/grub. d/40_custom ### )/EFI/Microsoft /Boot/bootmgfw. efi
menuentry "Windows bootmgfw.efi, generated by Boot-Repair" {
search --fs-uuid --no-floppy --set=root 18FE-69D8
chainloader (${root}
}
menuentry "Windows memtest.efi, generated by Boot-Repair" { )/EFI/Microsoft /Boot/memtest. efi
search --fs-uuid --no-floppy --set=root 18FE-69D8
chainloader (${root}
}
menuentry "Boot bootx64.efi, generated by Boot-Repair" { )/EFI/Boot/ bootx64. efi
search --fs-uuid --no-floppy --set=root 18FE-69D8
chainloader (${root}
}