Originally posted by: fleflikr
anyone know what i am missing?
There's your problem - two active partitions.
"Active" tells your system which drive is the boss during bootup. You have one too many in charge.
Originally posted by: fleflikr
disk 0 (D) is the terrabyte hd used for storage only and is marked as (active, primary drive)
guess i did a poor job installing os.
Originally posted by: Billb2
Originally posted by: fleflikr
anyone know what i am missing?
Yeah, punctuation and grammar................
yes the boot loader for some reason your W7 install can't find it's boot loader on the HDD a repair install, BCDedit or EastBCD may fix your problem are you sure that you have the drive that was set as the boot drive when you installed W7 still set as the boot device in your BIOS
...see?
Ummm, right. Linux is better, got it. But, he's running windows so that's really not relevant here.
My point still stands, the OP's problems are almost certainly caused by two active partitions. I've seen the exact same behavior. If you have something constructive to add, feel free to post it.
Originally posted by: Nothinman
The default one from MS just blindly jumps to the active partition, but it doesn't even look at other drives so they won't interfere.
Originally posted by: Nothinman
The BIOS determines which drive's MBR gets loaded and then unless it's a smart boot loader like GRUB the other drives don't matter.
The best possbility mentioned so far. Computers are good at doing the same thing over and over. If you aren't getting the same boot result each time, then something mechanical is probably interfering.Originally posted by: Nothinman
That sounds like either a drive is taking to long to spinup and isn't ready when the BIOS tries to boot or the drive is dying and just happens to find the file on the second try over those sectors.
So the MS boot loader is blindly jumping to the first active partition, right? Isn't that drive 0?
You didn't mention Linux? True, you did not say "Linux," but what about Grub, the boot loader that is pretty much never used with basic windows installs. You even called it a "smart boot loader" after implying that the windows boot loader was less smart ("blindly jumps").
His issues still appear to be two active partitions with the wrong one as drive 0. Marking drive 0 as not active will probably solve the problem. Even better would be to mark it as non-active, and swap the SATA cables to make the boot drive first. The Win7 DVD is very good at fixing the boot process with minimal knowledge.
Originally posted by: RebateMonger
Why not just disconnect the data drive and see if it fixes the boot problem?
Any idea why it's booting on the second try?Originally posted by: myocardia
Because then it won't boot at all, ever. His NTLDR is on his drive 0, which is his storage drive, and not on his drive 1, which is where Windows is installed.Originally posted by: RebateMonger
Why not just disconnect the data drive and see if it fixes the boot problem?
