SATA hard drive not detected

I have an Asus motherboard which supports SATA. My old drive, running XP, is the old IDE type and I have bought a new SATA hard drive on which to install Vista. My problem is that the computer fails to detect it at all. The bios also complains and I have to hit <g> (for some reason) to enable the old drive to continue with the boot up.  Any ideas would be greatly appreciated.
cavayeAsked:
Who is Participating?
 
willcompCommented:
Jumper pins 5 and 6 on WD hard disk (transfer speed limited to 150MB/sec).  That will be required for SATA controller (and BIOS) to recognize hard disk.  It is a well known issue with WD SATA II hard disks and VIA 8237 southbridge chips.  Your mobo has an 8237 southbridge.
0
 
Alan Huseyin KayahanCommented:
      Hi cavaye
           I hope my suggestions in question below works for you.
http://www.experts-exchange.com/Storage/Misc/Q_22435969.html
0
 
TelnetServicesCommented:
Many motherboards have a number of ways to handle the SATA. Some operate the SATA to all intents and purposes as an IDE drive - allowing you to install OS without needing the controller driver at install time.  Other need enabling or have a number of RAID options.  

You will need to set this up appropriately to your motherboard using the BIOS and/or any RAID setup utility on the mobo.

When you start installing the OS you may also need the controller drivers on a floppy disk to provide to the installer software. you should be able to get any required drivers from www.asus.com

If you are really stuck, please post model of motherboard here.

Good luck
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
cavayeAuthor Commented:
Thanks for taking the time to reply. My problem is that I can't seem to get the computer to accept that there is a new drive there at all - apart, that is, from the complaint by the bios (above) during boot up.
My motherboard is the Asus K8V SE deluxe. Am I being expectionally stupid and missing a vital part of the installation process? The new hard dirve - Western Digital Caviar SE16 320GB S300 16MG - manufacturer code - WD3200KS didn't come with any software...
0
 
Alan Huseyin KayahanCommented:
       Hi cavaye
            You dont need any software for your HDD. Make sure that you plugged the SATA cable to first available SATA port. If this is your only SATA drive, then you should plug it to PRI_SATA (primary sata).
0
 
PUNKYCommented:
If it is Sata II or sata-300, you might need to jumper limited to 150 first to setup (you can change back later for full transfer rate). Make sure the drive detected during boot.

You also might need to press F6 during Vista or XP installation to install sata controller driver (this driver is from your motherboard cd driver).
0
 
Alan Huseyin KayahanCommented:
        PUNKY: I especially checked mainboard about your idea before and saw that it supports SATA II, so supposed to work that way m8.
0
 
cavayeAuthor Commented:
Thanks again everyone.
MrHusy - I have it plugged into PRI_SATA and my Asus manual says I should go into MBFastBuild utility. However, after pressing 1 for auto setup it still only reports - Drive(s) used in Array 1 - not 2. The bios clearly knows that there is something there otherwise it wouldn't ask me to press Ctrl F for the MBFastBuild when I boot up. But I can't seem to get any further.
0
 
Alan Huseyin KayahanCommented:
          So now it doesnt ask you to press g anymore after you plugged to PRI_SATA. Now let me ask some questions. Are there any other SATA drives installed?
0
 
PUNKYCommented:
Even so, the motherboard supports sata II, but it failed detection while installing xp. Jumper limit will help this issue. Then after installation complete , set back to full speed.

MBFastBuild Utility is for Raid setup, if you want setup raid.
0
 
cavayeAuthor Commented:
Thanks again.
MrHusty: no other SATA drives.
Willcomp: Maybe I should try this jumper pins solution... Though I thought I read somewhere that SATA drives don't need jumper pins. Maybe I was mistaken.
0
 
cavayeAuthor Commented:
Willcomp: I tried you idea with the jumper pins 5&6. Unfortunately, nothing changed. The boot up still asks for the Ctrl F for the MBFastBuild. If i ignore this it boots up using the old drive as normal. No sign of the new hard drive on the tree. If I hit Ctrl F then the MBFastBuild screen also reports only 1 drive.
0
 
Alan Huseyin KayahanCommented:
             Sata drives dont need jumpers because they dont have the option to be a master or slave. Because interface is directly dedicated to single device, and as you know SATA cable has only 2 ends which is able to connect only 1 drive. Only jumper setting exist is the drive speed limitation jumper which has to be set if motherboard doesnt have the auto negotiate property. Normally there is no need to do this since your motherboard supports SATA II and your HDD is SATA II. But if there is a known issue as willcomp mentioned, then you should set the jumper.
0
 
PUNKYCommented:
You still have that message might be the boot sequence set to boot from RAID or SCSI, try different boot order such as default see if it helps. Also, you might disconnect IDE hard drive during this time see if that makes different.
0
 
willcompCommented:
To clear up a misconception  --> Asus K8V mobos use VIA K8T800 chipsets with 8237 southbridge chip that has an integrated SATA controller which is 150 MB/sec SATA I not SATA II.  Mobo also has a Promise SATA RAID controller (2 installed SATA controllers) which is also SATA I.  There is no SATA II support on mobo.

Which one of the SATA controllers do you have drive connected to?  Whichever one it is, set controller to IDE mode in BIOS rather than RAID mode.  Leave jumper on drive --> required for VIA controller and won't matter when connected to Promise controller.
0
 
Devario JohnsonSoftware EngineerCommented:
drivers drivers drivers
0
 
ComplyCommented:
If you skipped the F6 Third Party driver part in windows setup, you will need to add them first. DL the MB drivers for SATA chip set.

Open Device manager and look for the SCSI Raid Controller. Update the driver for your MB chipset that you DL for OS you are using.
0
 
cyberpranavCommented:
You can try connecting some other SATA HDD and see if it gets detected without any problems. Also upgrading to the latest BIOS may solve this problem.

::Pranav::
0
 
robstaceyCommented:
2 ways to proceed that I see.  
One is comply's suggestion at installation of supplying the SATA drivers after an F6 during install.   Trouble is that this only accepts floppies as far as I can remember.  If you have  a floppy drive, great but what if not?  
Most motherboards with SATA that I've seen allow you to configure the SATA in the BIOS to operate in compatibility mode which fools the MB and OS into thinking it's an IDE interface and doesn't need drivers!

You could install the OS using that and then install the drivers for the SATA from the source CD after the install and reconfigure the BIOS to the correct setting for full performance.
If your SATA controller supports RAID of any kind you might need to make an "array" even if you're only using 1 disk, I don't count it as an array of one but it's more a container which then shows as a disk for the OS.
I know this is rambling but hope it helps some.
0
 
cavayeAuthor Commented:
A solution at last! I had the hard drive plugged into the wrong socket on the m/b. It was in the Raid socket instead of the Serial ATA connector. The device then showed up in device manager but still not in My Computer (the only thing I was checking at first). In order to see the drive in My Computer I had to format it by right clicking My Computer and use Manage followed by Disk Management utility. Now it works. Thanks to everyone one who took the time to reply.
0
 
cyberpranavCommented:
Glad that your problem was solved. :)

Cheers...

::Pranav::
0
 
willcompCommented:
"Which one of the SATA controllers do you have drive connected to?  Whichever one it is, set controller to IDE mode in BIOS rather than RAID mode.  Leave jumper on drive --> required for VIA controller and won't matter when connected to Promise controller."

Refund if you like, but question was answered.
0
 
Devario JohnsonSoftware EngineerCommented:
I agree, the question was answered, it was the author who was negligent in picking an expert for assisting  the best.
0
 
VenabiliCommented:
See the last comment from the Asker - he found the solution himself. If you think a comment above is the same as the answer or is pointing to it - please let me know which and I will rethink. But from how I read it the Asker found this alone
0
 
willcompCommented:
He changed to a non-RAID controller. The quote I provided above specifically stated to set controller mode to IDE instead of RAID. Swapping controllers accomplished the same result.

Ask for assistance from a moderator in the Hard Drives and Storage Zone or Motherboard Zone if you are not familar with hardware and settings involved.

As an alternative - just delete.
0
 
VenabiliCommented:
>>Ask for assistance from a moderator in the Hard Drives and Storage Zone or Motherboard Zone if you are not familar with hardware and settings involved.

More familiar than I would like to be. Just somehow missed the actual comment and never realised you copied part of your old response.

I will review this one.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.