BIOS does not see new SATA drive

Gammit10

Honorable
Sep 5, 2013
7
0
10,510
I believe I have done something epically stupid. I have a set of old hardware set up as a home server using Windows Home Server 2011. The motherboard, being old, supports BIOS and not UEFI.

I added a new 2 TB internal SATA drive to my machine yesterday and began to set it up. However, I chose to set it up using GPT and not MBR. I then set up my partitions the way I wanted and rebooted.

From that point forward, my system will not boot with the new hard drive plugged in. It will boot fine if I unplug the SATA cable from the new hard drive, and I have verified the SATA cable, motherboard port, and power cable are functioning correctly. I have also pulled the CMOS battery and reseated it. But if the new SATA drive is fully plugged-in, my computer freezes during POST. I can't even get in to the BIOS settings while it's plugged in.

My current guess is either I have a bad new hard drive even though it was working fine before the reboot, or the fact that I setup the hard drive to use GPT and not MBR.

Can I attempt to connect the hard drive to another, newer computer via eSATA? What are my options, if any?
 
Solution


Before you go through the hassle of returning/exchanging why not try to attach it to the other computer that sees it and repartitioning it to be MBR partitions? If it works, it should save you a lot of trouble.

Yogi

Strange, The drive should still work as a storage drive as GPT(I have a 3TB GTP drive in my non ueif H55 board and it works fine as my storage drive). You can not boot from it most likely, but that should be the only issue.

Could your board be trying to boot from it?

Plugging it into another system to ensure the drive is not defective is a very good idea.

Please note i can NOT hot-plug my 3tb drive with e-sata on my non uefi board(just ever shows up. My 2TB works fine[it is MBR]). I have to reboot after plugging it or install it internally(what I was gong to do anyway)
 

Gammit10

Honorable
Sep 5, 2013
7
0
10,510




It's possible, because I believe my BIOS naturally attempts to place lower-numbered SATA ports before higher-numbered SATA ports in terms of boot order. While I can't get into the BIOS to check the boot order, I will try to switch the new drive to use a higher-numbered SATA port and test when I get home.
 

Gammit10

Honorable
Sep 5, 2013
7
0
10,510
I plugged the new drive into another desktop and that second desktop could see it and configure it OK. Plugged it back into my home server and everything appeared OK until I rebooted. Then drive disappeared again.

I'm returning the drive.
 

Gammit10

Honorable
Sep 5, 2013
7
0
10,510
I plugged the new drive into another desktop and that second desktop could see it and configure it OK. Plugged it back into my home server and everything appeared OK until I rebooted. Then drive disappeared again.

I'm returning the drive.
 
I would check the maker of your system to see if they have a limit for supported drives.

I did see an old HP system that would intermittently see an SSD drive. It took several reboots before it could see it, once seen it work work, but would disappear on the next boot.
 

Gammit10

Honorable
Sep 5, 2013
7
0
10,510
I plugged the new drive into another desktop and that second desktop could see it and configure it OK. Plugged it back into my home server and everything appeared OK until I rebooted. Then drive disappeared again.

I'm returning the drive.
 


Before you go through the hassle of returning/exchanging why not try to attach it to the other computer that sees it and repartitioning it to be MBR partitions? If it works, it should save you a lot of trouble.

Yogi

 
Solution

TRENDING THREADS