|This is extremely frustrating for me, but I'll try and describe it the best I can.|
I recently purchased a Seagate Barracuda XT 2TB to increase the storage space on my existing computer. (I already have an existing Maxtor 300GB drive that's getting full) I received it in a box that had a busted side, so I wasn't all that surprised when the drive did not spin up, was not recognized by the BIOS, The Boot Menu, or WinXPro SP3. I filled out an RMA with Seagate, and got a replacement drive back today with the same issue. There is absolutely no way this could have been damaged in shipping (The packaging is flawless compared to the way B&H Photo shipped the first one) and I believe the first drive I sent off may have been perfectly fine.
I've tried every jumper configuration possible listed in the manual for the drive with the same results. I've tried every SATA port with the same results.
I am absolutely sure the cables work (Data and Power) Because I swapped them around to every combination possible and the 300GB drive I currently have always worked no matter what cables were used)
Here is the detailed extent of the problem.
BIOS boots up (AMI Chipset) And does not detect the drive regardless of port used. I tried upgrading the BIOS but that did nothing, so I loaded the defaults to avoid any further issues. The Drive detection in the BIOS is set to Auto detect drives. The BIOS is set to AHCI mode. Of course, windows doesn't recognize the drive either. (By Windows I mean it does not show up in Disk Management) Tomorrow I'm going to test it on another system to see if the drive is good but I'm positive this is a problem with my motherboard and not the drive.
The Motherboard I have is a Biostar TP43E Combo.
At one point I thought it might be caused by the drive being SATA 3 and the motherboard only supporting SATA 2 but I've since then learned they are backwards compatible and I just won't be able to run at full speed which would be acceptable if the drive actually functioned at all.
The relevance of the first part is I had the exact same problem with the original drive that I'm having with the new replacement.
I'm really hoping someone out there can help.