Comment 15 for bug 1050940

Erick, it would be helpful if you would attach relevant debug information as attachments in launchpad, rather than linking to pastebins.

Your "boot info summary" shows the following menu entry:

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-30D8-159A' {
 insmod part_gpt
 insmod fat
 set root='hd0,gpt2'
 if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 30D8-159A
 else
   search --no-floppy --fs-uuid --set=root 30D8-159A
 fi
 chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}

The boot entry /after/ the boot repair seems to be identical:

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-30D8-159A' {
 insmod part_gpt
 insmod fat
 set root='hd0,gpt2'
 if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 30D8-159A
 else
   search --no-floppy --fs-uuid --set=root 30D8-159A
 fi
 chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}

So how exactly did the boot fail for you before running the boot repair?