After getting the machine dual-booting both Ubuntu 13.04 and Windows 7, I realized this machine is booting much much differently than any of my other machines.
It's using a UEFI chip, not a BIOS chip. It's currently booting both Windows 7 and Ubuntu in EFI mode (With SecureBoot disabled, since Win7 fails the certificate check) and here's what's very interesting, which I think is why Ubiquity did what it did (To me as well as the original poster, posting about Windows 8.. Which would also have been booting in EFI mode.) When I boot Ubiquity in EFI mode, with the disk using a GUID Partition Tables, Ubiquity cannot see Windows 7's EFI bootloader. If I boot the machine with F2 and go into the EFI firmware settings, under the Boot tab my options include "Windows Boot Loader (P0: hddserialnumber)" and "Ubuntu (P0: hddserialnumber)" If I select "Windows Boot Loader" as the primary boot device, it boots up the Windows Vista+ BOOTMGR and shows Windows... But it can *not* see GRUB. If I reboot the machine, goto EFI firmware setup and set "Ubuntu" as the primary boot device, the machine boots straight to GRUB... But GRUB can *not* see the Windows 7 BOOTMGR. Sorry for 3 long posts. Just trying to put as much information as possible here, since neither of us have any kind of report to show for. Hopefully this extra info will help to correct this behavior. I think the problem is that, with these new EFI machines, the EFI boot loaders can't see each other, even though they're all stored in the same sda1 partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073968 Title: Install over Windows 8 partition erased whole HDD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1073968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
