My friend has been having issues with his PC recently. Mostly they are Mobo problems which we think have been fully resolved. The new problem is with his HDD which is a Seagate Barracuda Model: ST2000DM001. The issue is if you plug it into a PC that is running windows as an extra drive it is seen no problem but if you plug it in as the only drive it says no bootable device found. This becomes an issue because his Mobo the Asus z97 pro gamer sees the boot error as one of it's error checks and then refuses to load bios. I don't know if the drive is faulty or if it's a connection issue or what. He just dropped it off at my house and sometime when I need/feel like rebooting I'm going to power down and plug it in and see what I can find out on my machine. I figure some of you guys might have a better idea than I do what's going on. Everywhere on the internet that I've found people are having the issue where Bios will see the drive but windows will not where as this drive is doing the exact opposite. Any ideas are greatly appreciated. Also I know seagate isn't the best HDD manufacturer so he might just need to RMA it but at this point that's the last thing he wants to have to do. After having to do that with his new mobo twice he's kinda tired of RMAs.
I have a ST1000 in my system, same drive but with only 1TB instead of 2, and it works perfectly fine on my Gigabyte GA-X58-UD7 Motherboard, altrough it's my secondary drive, my boot drive is a AData SP900 128GB. Use crystal disk info to check the drive's status.
Is the disk partitioned? is it set as the boot device? if it is the boot device and has no partitions, it will show your symptoms...
I just got done plugging it into my system (glad to see some replies) and it worked fine. Put my windows 7 cd in and it was ready to install windows on the drive. So I'm guessing maybe a bad sata cable or it just wasn't fully plugged in to the power cable. Pretty sure it's properly partitioned as it was running windows before my friends mobo died, he then formatted it through windows so it should still be properly partitioned. So I was thinking about this while I was out frolfing, and came to the conclusion that I didn't go far enough into the install of windows to find out if it worked or not. I did just now and low and behold windows cannot be installed on any of the partitions. So I guess you were dead nuts correct. I didn't want to sit through a windows install so I just deleted them and made new ones and I'm gonna give it back to my buddy and he can sit through the install and it should work for him.
