New
#11
This is very nearly what my problem is.
I installed a fresh Windows 7, but not wanting to touch the rest of my drive, I made a nice 160 GB partition (of a 1TB drive) in it and went ahead with the install. But it was the 2nd hard drive used by this computer. An older version of Windows was still installed in the first (160 GB) drive. But that's cool with me, I would prefer to just keep all these partitions around and not think about it.
Problem was, somehow the Windows boot manager on drive #1 was configured to boot into Windows 7 on drive #2. Again, that shouldn't be a problem. But then I try to go directly from the BIOS to drive #2, it says that it's not bootable. Okay, so check the information... the 160 GB Windows partition is marked as logical, while the other (data only) partition is marked as the primary.
So... my BIOS is telling the truth, at least somewhat. It looked at the drive, found the primary partition, and correctly concluded that it was not bootable. As far as I can figure out, the only instructions that allow me to boot into the Windows 7 partition lie on drive #1, which is a terrible terrible policy and I'm running around trying to figure out a solution to fix it.
EaseUS partition manager has several utilities that seem like they could fix it, but none actually work. Editing the MBR seems hopeful to point the BIOS to the right partition, but this can't be used with the free version, and I have no confidence that buying it would actually solve my problem. Now, I would like to use EaseUS to just set the Windows 7 drive to primary, but it says that this property can't be changed for a bootable sector. Now I'm stuck in a big infinite loop of errors!
Now I'm trying to do this same operation with diskpart (which is likely to give the same error anyway), and I notice that it has an "Extended" sector, which seems a duplicate of the "Logical" Windows 7 partition. I guess I'll ignore that and try to make the logical sector primary. If that doesn't work, I'll give the Paragon partition manger a shot. I'm fairly sure neither of these approaches will work, and I'll post here again to continue the saga.
UPDATE: problem was solved. See my final post for this specific saga first if you are working on a similar problem. Everything between these two posts are intermediary troubleshooting steps.
Last edited by AlanJS; 13 May 2014 at 15:42. Reason: link to direct users to the solution