No bootable drive

[MrPickles]

Howdy, hopefully a quick fix. A couple of weeks ago I transfered my Win 10 OS bootable 2TB HD to a new 840 250GB SSD. Everything was fantastic and fast. However, today I finally decided to reconnect the 2TB HD into a different SATA conection so I could start tranfering files from my old back up drive. When I fired up my computer, it did not pick up my bootable SSD or the formally bootable HD with the old Win 10 OS. I hope I didn't screw booth drives up. I'm sure it's a quick fix for you pros. I'm a rookie. Thanks for any help.

 

[MrPickles]

This shouldn't have been posted in memory
Storage would've been better but hey ho

Why did you change the 2TB harddrive slot? Couldn't you have just plugged the old drive into another SATA port?

Try putting the 2TB hard drive back in the original port and see if it boots

 

[MrPickles]

Thank you I will give it a try. I kept my SSD in the same bootable SATA slot and tried to add the 2TB HD into a new SATA slot. Now the SSD is not recognised.

 

[lodders]

I think you need to investigate in BIOS. Read your motherboard manual.

 

[MrPickles]

Okay so I reconnected the hard drive Then I turn the computer back on, still no bootable disk. Went into the BIOS the only drives it recognizes are Realtek and DVD CD. When it tries to boot up with the Realtek it shows no bootable disk. I remove the SSD hard drive and connected it to my working computer and everything reads fine that would lead me to believe that somehow when I connected the 2 terabyte hard drive to the other SATA connector I may have fried something? Kind of at 8 Los from here. Both drives are no more than two weeks old and everything was running fine until I tried to connect the 2 terabyte hard drive on the other SATA connector. FYI the two terabyte hard drive contained the mirror files that I transferred to my SSD including the operating system. Should I have formatted the two terabyte hard drive prior to connecting it to my computer?

 

[lodders]

This is a long shot, but have you accidentally formatted one disk as MBR and one as GPT.... I made this mistake once, and got similar symptoms. Google it if you need more info...

 

[MrPickles]

I think you need to investigate in BIOS. Read your motherboard manual.

 

[MrPickles]

Well after trial and error all night, I was able to discern that when I was hooking up the other hard drive there may have been some static. As a result the SATA wire may have fried? Anyway, I used a fresh SATA wire in the same port and it recognize my drive and fired up without a hitch.

 

[MrPickles]

Okay so I reconnected the hard drive Then I turn the computer back on, still no bootable disk. Went into the BIOS the only drives it recognizes are Realtek and DVD CD. When it tries to boot up with the Realtek it shows no bootable disk. I remove the SSD hard drive and connected it to my working computer and everything reads fine that would lead me to believe that somehow when I connected the 2 terabyte hard drive to the other SATA connector I may have fried something? Kind of at 8 Los from here. Both drives are no more than two weeks old and everything was running fine until I tried to connect the 2 terabyte hard drive on the other SATA connector. FYI the two terabyte hard drive contained the mirror files that I transferred to my SSD including the operating system. Should I have formatted the two terabyte hard drive prior to connecting it to my computer?

I doubt you've fried something but there's a possibility due to discharge when fiddling around with ports
Since you know they work on the other computer, you know it's not the drives
Try resetting the CMOS for what it's worth
If not, you could try an RMA since something has broke/irreversible
Formatted or not, it shouldn't have broken anything
I've connected drives with data to my motherboard and everything has been fine

 

[MrPickles]

Well after trial and error all night, I was able to discern that when I was hooking up the other hard drive there may have been some static. As a result the SATA wire may have fried? Anyway, I used a fresh SATA wire in the same port and it recognize my drive and fired up without a hitch.