Try leaving everything connected, then reset the bios.
I don't understand why you disconnected anything at all before resetting? I have never done that.
crunchie
Most Valuable Poster
20,095 posts since Feb 2004
Reputation Points: 1,142
Solved Threads: 985
BIOS tends to shuffle the HD boot priority order, so it is possible that it tries to boot from 1.5 Tb drive first when it detects it.
What you should do is plug everything in, and access BIOS settings, making sure you are booting from the right drive.
Chaky
Postaholic
2,017 posts since May 2006
Reputation Points: 230
Solved Threads: 47
You say "Unplug SATA, and everything is fine, and I can plug it in, in both XP and Ubuntu and the drive works perfectly."
As in you plugg it in while PC is running?
I don't think that is a good practice.
Anyway, it seems to me that the drive is not in question here, but the controller. (in other words: mobo)
Chaky
Postaholic
2,017 posts since May 2006
Reputation Points: 230
Solved Threads: 47
I think that the power consumption is the same whether or not the data cabel is plugged in. (the power cable is plugged in all the time, right?)
You should try smartmon tools (or alike) to see what S.M.A.R.T. has to say about it.
Now, thinking about S.M.A.R.T., I could think of one or two effects that plugging the drive in while PC is running could have on the S.M.A.R.T. monitoring itself. I think that it ispossible that it could generate some false-positive readings of slow spinups ans such, that can accumulate and eventualy give you a warning on every single time you try to boot with that drive pluggd in, telling you that "it will fail soon".
Maybe, you should disable the S.M.A.R.T. for the time being. (no need to have it enabled, I think, to collect the data with smartmon tools)
Chaky
Postaholic
2,017 posts since May 2006
Reputation Points: 230
Solved Threads: 47