SATA 750 and jumpters

  • Thread starter Thread starter Terry
  • Start date Start date
T

Terry

Here is my dilemma. The people at alt.comp.hardware.pc-homebuilt
suggested that I reask the questions here.


Here is what I have done.
I reset the CMOS
I have all three boot options set to HD0
I have boot from external disabled
I have onboard RAID disabled


My computer is a Abit KT7A RAID
1G Athlon
Nvidia 5500 Video
430W PS
Sil 3112A SATA RAID 14.2.47 1997-2004 Silicon Image Inc. PCI
controller card
80 G IDE WD boot drive
IDE WD 160G
SATA WD 500


I am trying to add a SATA WD 750


Everything was working fine. I added the 750 drive. It wouldn't
work. It hangs the computer at boot. I went to WD support page and
found this:
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faq...

I installed the jumper and the drive worked! I copied all the files I
had on a 150G IDE drive to the new 750 drive. I then took the IDE
hard drive out. I mounted the 750 in its place. Well it quit working
again and started hanging at the boot screen.


When I try to boot the PCI SATA controller reports
WDC WD 5000 AAKS 00TMA 5 000 000
WDC WD 7500 AAKS 00RBA < It hangs here


I can unplug the 750 and everything boots fine.
I have tried the 750 on controller 0 and 1
If I plug the 750 into slot 0 then it hangs without reporting the 500


The 500 has been working fine without using the jumper, but I have
installed a jumper on the 500 now.


So now the 500 will work with or without the jumper. the 750 will
not work with or without the jumper.


The 750 will work fine in my other machine, but I want it in my old
KT7A machine. I have also tried using the 750 only without the 500.

What else can I try to get the 750 going?
 
Previously Terry said:
Here is my dilemma. The people at alt.comp.hardware.pc-homebuilt
suggested that I reask the questions here.

Here is what I have done.
I reset the CMOS
I have all three boot options set to HD0
I have boot from external disabled
I have onboard RAID disabled

My computer is a Abit KT7A RAID
1G Athlon
Nvidia 5500 Video
430W PS
Sil 3112A SATA RAID 14.2.47 1997-2004 Silicon Image Inc. PCI
controller card
80 G IDE WD boot drive
IDE WD 160G
SATA WD 500

I am trying to add a SATA WD 750

Everything was working fine. I added the 750 drive. It wouldn't
work. It hangs the computer at boot. I went to WD support page and
found this:
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faq...
Click to expand...
I installed the jumper and the drive worked! I copied all the files I
had on a 150G IDE drive to the new 750 drive. I then took the IDE
hard drive out. I mounted the 750 in its place. Well it quit working
again and started hanging at the boot screen.

When I try to boot the PCI SATA controller reports
WDC WD 5000 AAKS 00TMA 5 000 000
WDC WD 7500 AAKS 00RBA < It hangs here

I can unplug the 750 and everything boots fine.
I have tried the 750 on controller 0 and 1
If I plug the 750 into slot 0 then it hangs without reporting the 500

The 500 has been working fine without using the jumper, but I have
installed a jumper on the 500 now.

So now the 500 will work with or without the jumper. the 750 will
not work with or without the jumper.

The 750 will work fine in my other machine, but I want it in my old
KT7A machine. I have also tried using the 750 only without the 500.
Click to expand...
What else can I try to get the 750 going?
Click to expand...

I would suggest that your PCI contoller has a size-limit,
likely 500GB in its BIOS. If som a BIOS update of the
controller card _could_ fix this, if one is available that
extends the size limit. The other option is getting a
new SATA controller that supports drives >500GB.

Arno
 
Arno Wagner wrote in news:[email protected]
I would suggest that your PCI contoller has a size-limit,
likely 500GB in its BIOS.
Click to expand...

Yeah, it has a little camera to see what OP is doing and switches that
limit on and off when it likes to and have a little fun with the OP.

Another case cracked by the babblebot.
 
No need to introduce yourself.

It is pretty easy to recognize the group troll.

Someone correct me if I am wrong.
Click to expand...

Nope. Not wrong. There are/were a number of them here. Long since
killfilled though.
 
Franc Zabkar wrote in news:[email protected]
The OP has had his configuration working at least once, so I can't see
how it could be a capacity issue.

What I find strange, and which I mentioned in the other thread, is
that, AFAICS, the BIOS would already have enough information to
calculate the drive's capacity (the Identify Drive command would have
retrieved a 512 byte block containing model number, CHS, LBA, etc),
Click to expand...
but it hangs at this point.
Click to expand...

Who says.
I suggested that maybe the BIOS was
testing the drive's SMART status before reporting its capacity.
Maybe disabling SMART in the BIOS setup would allow the POST to
progress to the next stage ???
Click to expand...

And you posted: The OP has had his configuration working at least once ...

Sudden loss of memory? Brainfart?
 
Previously Franc Zabkar said:
On 9 Apr 2008 01:40:58 GMT, Arno Wagner <[email protected]> put finger to
keyboard and composed:
Click to expand...
The OP has had his configuration working at least once, so I can't see
how it could be a capacity issue.
Click to expand...

Opps, sorry. I also meant to ask whether there may be different
controllers involved here? If niot, then you are right, of course.

Arno
 
Terry wrote
Ah, the ever elusive context snip.
No need to introduce yourself.
Click to expand...

Looking in the mirror, are we?
It is pretty easy to recognize the group troll.
Click to expand...

No. Really, it is?
Someone correct me if I am wrong.
Click to expand...

And you are obviously a newbee, new to this group, just laying low.
Not at all trolling for the responses this kind of question always gets
by those who have been bitten and will be bitten, just because they can't help themselves. Correct me if I'm wrong.
 
The OP has had his configuration working at least once, so I can't see
how it could be a capacity issue.

What I find strange, and which I mentioned in the other thread, is
that, AFAICS, the BIOS would already have enough information to
calculate the drive's capacity (the Identify Drive command would have
retrieved a 512 byte block containing model number, CHS, LBA, etc),
but it hangs at this point. I suggested that maybe the BIOS was
testing the drive's SMART status before reporting its capacity. Maybe
disabling SMART in the BIOS setup would allow the POST to progress to
the next stage ???

- Franc Zabkar
Click to expand...

I checked the Bios for any SMART settings and didn't find any.
Because of this suggestion, I did try booting with failsafe options,
but it still hangs at boot.

I went to SI's web page to try to find a bios upgrade. I found
several drivers. I didn't download any because there were too many
choices for my small brain.

I assume that any driver I would have selected wouldn't make any
difference anyway because the boot never gets that far anyway.

I have never tried to upgrade a bios but I didn't find anything
anyway.

Thanks for everyone's suggestions.

I guess the only thing left to do is get another controller.

The cards on the bottom of the drives are not the same.
 
Back
Top