Serious hard drive problems

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
Here's the problem:
I got an SATA HDD to replace my old PATA HDD, but the original PATA hard drive won't boot windows anymore and when I boot off of the SATA drive, the PATA drive isn't detected in Windows. Any idea what's wrong with this? Also when the PATA drive is attached, performance is very sluggish during POST. Thanks in advance.
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
Originally posted by: cprince
Check the BIOS boot sequence.

Should it read removable, cdrom, hard drive? Because it just read hard drive in there. What worries me is that the PATA(IDE) hard drive won't even get picked up by the bios anymore.
 

cprince

Senior member
May 8, 2007
963
0
0
It should read hard drive, but it should still picked up the PATA hard drive. Check for a BIOS update.
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
Okay, I managed to get the BIOS to pick up that the IDE hard drive is on the master channel on the ribbon cable now, but when I try to boot off of the IDE drive, it'll hang for a few minutes, then boot from the SATA drive. When I booted from the SATA drive, I looked in my computer hoping that the IDE drive would be there, but it's not. I also noticed that the computer takes noticebly longer to boot than before. Any ideas? Thanks.
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
If the IDE drive is set to master, could that be causing the problems? I'm pretty sure the SATA drive is set to master as well, could this be causing a problem even though they're not connected on the same wire?
 

r2dtwo85

Junior Member
Jun 8, 2007
2
0
0
have you changed the configuration of the jumpers on the hard drives? set one as primary and the other as secondary you can do that by placing the black or blue jumpers to the specific direction. I would have the SATA as primary since It's a lot faster than the PATA.
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
Originally posted by: effee
Dont some boards need SATA drivers installed first as well?

It booted off of the SATA drive just fine, so I doubt that's the problem. I think that r2dtwo85 nailed it. I'll give it a try.
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
Originally posted by: r2dtwo85
have you changed the configuration of the jumpers on the hard drives? set one as primary and the other as secondary you can do that by placing the black or blue jumpers to the specific direction. I would have the SATA as primary since It's a lot faster than the PATA.

Secondary as in slave right?
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
If the HDD is a Western Digital, pull the jumper cap off the pins completely and leave it that way. That's the special Single Master setting. This is often the cure for no-POST or hanged-POST.

I would have the SATA as primary since It's a lot faster than the PATA.
I have similar SATA and PATA drives, and even a cutting-edge perpendicular-recording SATA jobbie with the 16MB cache, NCQ etc etc, and my finding is that they're all rather slow :evil: But whatever ;)
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
Originally posted by: mechBgon
If the HDD is a Western Digital, pull the jumper cap off the pins completely and leave it that way. That's the special Single Master setting. This is often the cure for no-POST or hanged-POST.

I would have the SATA as primary since It's a lot faster than the PATA.
I have similar SATA and PATA drives, and even a cutting-edge perpendicular-recording SATA jobbie with the 16MB cache, NCQ etc etc, and my finding is that they're all rather slow :evil: But whatever ;)

They're both Seagates actually. I set it to slave, but it still won't appear in Windows, it will appear in the BIOS though.
edit: When I try to boot right off of th PATA disk, it will wait a few minutes then say "Disk boot failure, insert system disk and press enter", even though Windows is on it with all of the correct drivers.
 

Smartazz

Diamond Member
Dec 29, 2005
6,128
0
76
The hard drive is not viewable anywhere in Windows, not even the disk manager. Could the drive be dead?