I just swapped hard drives between two machines. I installed Ubuntu Desktop on one, and Server on the other. But when I try to boot from the HDD on the Server, it says Primary master drive fails. I thought I fried the drive, but if I put it back into the Desktop, it boots fine. And putting the Desktop HDD in the Server machine works too. But the Server HDD won't work the the Server. I've done some disk diagnostics and they all pass. It just won't boot. All the bios settings are at the default. And the initial BIOS screen seems to recognize it correctly as a SAMSUNGS SP0144. The motherboard looks to be an Asus A7v266-E (BIOS Rev 1011). I've tried changing the jumper and cables. Hope someone has some ideas, thanks!
just to clarify, are HDD SATA or IDE also try it as master, slave & CS - assuming their IDE, if SATA - have you tried different SATA ports also try different combinations of data & power cables
Are both computers close together? If so, connect the power cable of the working computer to the hard drive, when the hard drive is connected to the server. Now turn on the known working computer to provide power, and then turn on the server. This way we can see if it's a power issue.
will that work ? from what limited amount i remember about my days in eleronics, it would work if you shorted both the 12V negative & 5V negative connectors obviously with both PSUs on
Gave that a try and it doesn't seem to change anything. Like I said, other drives seem to work.. sort of. I plugged in a drive with Ubuntu Desktop 64bit, and it seems to boot, but gives me a message saying it needs a 64bit CPU. I've also tried installing USE 32bit on the drive, but while in my UDE computer, and then putting it in my USE machine, but it won't boot. I also can't load WXP or WV on the Server machine, as it gives me errors about there being no suitable partition or drive. I've also tried disconnecting all power from the mobo and removing the battery, in order to completely reset it. I reset it successfully but it did not fix the problem. Wold this happen if the mobo was physically broken somehow?
