1
I just got a new PC (HP P7-1380T) with Windows 7 preinstalled. The machine is set up for EFI booting without 'secure boot'. I had planned to install my old SATA drive (dual-boot XP and Linux with grub in the MBR) as a secondary drive to copy both windows and linux files over to the new drive - and then leave it in as a backup device. The problem is that I can't install the old drive in a way that both Windows and Linux can see it.
The machine came with its hard drive in SATA0 and a DVD/ROM drive in SATA2. SATA1 and SATA3 are free.
When I plug my old drive into SATA1, I can't boot Windows 7. The EFI bootloader tries to boot from the old SATA1 drive instead of the new SATA0 drive. It gets as far as loading up the grub boot menu, at which point I power off to prevent further mischief. In SATA1, the old drive shows up in the BIOS, and when I boot Linux from a live CD, it sees it as /dev/sdb.
When I plug my old drive into SATA3, it doesn't show up in the BIOS, and when I boot the live linux CD, it does not see the drive either. But with the drive in SATA3, Windows 7 boots, and it sees the old XP partition and makes it available as drive F:.
I would prefer to use SATA1, obviously, so Linux can use the drive, but so far, I can only have Windows or Linux see it, but not both. Why would the EFI Windows bootloader try to boot off of a secondary drive, when it's obviously set up to boot off of SATA0? Is there some tool I can use to change this behavior?
Can you confirm the boot order in the UEFI firmware configuration? Sometimes the actual setting has nothing to do with the port numberings. It is also quite unsual for a UEFI firmware to decide to boot from a MBR drive. With the ways the firmware work, I can't see how this is even possible without resetting the CPU each time you boot. – billc.cn – 2013-01-14T23:35:03.700
Windows Boot Manager, USB floppy, USB hard drive, ATAPI CD/DVD drive. Could it be that the Windows Boot Manager has its own boot order implemented in software once it loads? Maybe the EasyBCD bootloader management utility would shed some light. come to think of it, prior to booting the old MBR's grub, the boot manager displays a progress bar with a message like 'scanning devices'. Maybe it's detecting the drive and inserting it into its boot list. – littlenoodles – 2013-01-14T23:49:53.793
I loaded EasyBCD, and the windows bootloader shows Windows 7 at the bottom of the list, with a generic 'Hard Drive' entry above it. Maybe that's the problem, that generic hard drive boots when I'm in SATA1 (BIOS reports it), but not when I'm in SATA3 (BIOS ignores it). I can try editing the boot order with EasyBCD, if you think that's the issue (and I can't brick my system...) – littlenoodles – 2013-01-15T00:12:39.273