Motherboard Ignoring Boot Priority with 2 Hard Drives

Lapys

Distinguished
Nov 7, 2011
33
0
18,540
So I have a SSD, and I cloned my old hard disk drive to it, and now I want to use my ssd as my main drive, and have the HDD as a secondary for storage. However, whenever I set the boot priority to use my SSD, it boots instead to the old drive. I even tell it to totally ignore the old drive as a hard disk drive, and it still boots straight to it every time. Disconnecting the old drive allows the SSD to boot, and everything runs fine, so I don't think it was a bad clone.

I've tried everything I can think in the BIOS, and I've even flashed the BIOS to the newest version. No luck.

Also. When I'm on the old drive, it recognizes the new drive and I can access it. So what gives? The only other thing I can think of is that the SATA cables might be set up such that the old drive is a master and the new is a slave, but shouldn't boot priority ignore this?

Any helps is appreciated, thanks.
 

Lapys

Distinguished
Nov 7, 2011
33
0
18,540
I will try that right now. I thought of something else that could potentially affect the problem, too.

When I made the switch, I let it boot without selecting options, and it defaulted to the old drive. It said installing drivers for new software, presumably for the new drive. Could it be that there is a driver that got installed that is somehow assuming the old drive is the main drive and the new one is secondary? Just wondering if this is possible since I believe drivers happen after BOOT. Updates incoming on switching cables.
 

Lapys

Distinguished
Nov 7, 2011
33
0
18,540
Switched the cables, set the boot options, and it still didn't work. So it doesn't seem to be a master slave issue. (Although the new drive is like 4th master, and the old drive is the primary slave.) Could it be an issue with me connecting them with the same power cable? I can't imagine why, but I'm just reaching for anything at this point.
 

Lapys

Distinguished
Nov 7, 2011
33
0
18,540
I unplugged the old drive and now I'm getting a windows failed to start error... what gives? The drive was working before. Is it possible that when it installed drivers to use the new drive as extra storage it messed around with the drive itself? And is there a good way to fix this without another clone?