SATA and IDE simultaneously?

Davroz

Junior Member
Nov 8, 2006
4
0
0
Hi, I've been having alot of problems with what should have been an "Oh so simple" hard disk addition.

I had been using a 120GB Maxtor DiamondMax Plus 9 IDE drive, but it was getting full and cluttered - like they do, so I decided to buy a nice new SATA drive - as my motherboard (a Foxconn NF4K8AC) supposedly suports both. I picked out a Seagate Barracuda 7200.9, 160GB, SATA drive - and promptly ordered it.

I installed the drive without problem. It was recognised by the Bios, and after running Seagates "Disk wizard" setup utility - windows (XP, SP2) had no trouble recognising the new drive either. The drive worked fine for hours, then I got a complete system freeze (couldn't even move the mouse). I restarted the computer, and windows wouldnt boot - it just gave a blue screen error during its loading. I unplugged the new SATA drive, and booted again, this time it worked perfectly - so I shut down, and gave the new drive another go, to find that it worked fine as before - all my files were still there, and everything was accessible. Then, I was in the middle of transfering some files from my old to new hard drives - and boom, another complete system freeze, I restarted, and lo and behold - couldnt boot windows. Unplugged drive, booted, shut down, plugged it in, booted, and all worked - until the next freeze. After a few cycles like this, the new hard drive started reporting bad sectors - and seagates self diagnostis utility "seatools" came up with bad sector errors when i ran it. I tried to fully reformat the drive using the NTFS formatter in the windows installer - but this couldnt even complete, it just gave corrupt drive errors. I duely sent the drive back to the retailer - and got a replacment about a week later - The new drive started perfect, but then, as before - about an hour into operation (i had succesfully copied accross files) - I got a complete system freeze. Rebooted, got blue screen, and had to unplug my new drive to continue. Currently, Seatools reports no errors with the drive.

So, in my great despair I came here - and was wandering if you thought the new drive might also be corrupted, or if its maybe a problem with me running an IDE drive and a SATA drive simultaneously?

I have updated my BIOS and all drives, I've tried fiddling with many different BIOS settings, and I've tried different SATA ports - and IDE ports, and different cables. The jumper settings on the drives are all correct, and I've even tried the jumpers in different positions - all leaving the same result.

Any help will be very very much appreciated - and sorry for the long post. I hope I havnt missed out any vital information - but if I have, please ask!

Thanks again.
 

RKS

Diamond Member
Oct 9, 1999
6,824
3
81
I don't have a technical answer but I run SATA and PATA drives together in both of my systems without any issues. One is an AMD (EVGA) system the other is an Intel(Intel) sytem.
 

btcomm1

Senior member
Sep 7, 2006
943
0
0
I'm thinking the same thing as Marinski, perhaps your power supply is too weak or is malfuntioning and not able to supply your whole system plus the extra drive you put in. I run PATA and SATA in the same machine and it works just fine.
 

kungsangun

Junior Member
Dec 27, 2006
5
0
0
I've recently purchased a Seagate SATA drive that has a jumper setting to set the SATA speed to 1.5Gb/sec for compatibility with legacy SATA motherboards. Perhaps your new drive is a 3Gb/sec drive and your Mobo only supports 1.5Gb/sec.. Just a guess
 

Davroz

Junior Member
Nov 8, 2006
4
0
0
Thanks for the quick feedback, my motherboard indeed doesnt support the 3GB/sec SATA-2, but the hard drive has the same jumper setting to make it work at the slower speed, which i've tried in all positions.

As for the power supply, I'm guessing this will probly be my problem. Currently, I'm using a 550W supply, but its generically branded (ran out of money!) - i know they are far from ideal, but it had been doing a good job until now, if that is the reason for my crashes! I'll have a play around, maybe unplugging some other componants to reduce the load - but if worst comes to worst i guess I'll have to fork out for a new PSU.

Thanks again for the help.