Asrock p67 extreme4 gen3 not detecting new HDD?

[frstfire]

Dear all,

I am having a strange problem that hopefully can be solved by the experts among you. I have a brand new WD caviar black 2TB HDD that is not formatted yet and cannot be detected by the abovementioned mobo UEFI, no matter which SATA port I plug into. This is true even if I were to simply shift the SATA cable and power cable from a WD raptor 150GB which I am using to boot from the mobo to this caviar black. Pins 5 and 6 have been jumpered to enable 3Gbps transfer rate on the caviar black. All I can hear from the caviar black are very slight clicking noises as if it does not have enough power to spin up, or is not getting any signal from the SATA port to tell it to spin up(?).

I can boot the raptor HDD from any of the Intel controlled SATA ports. I can also have a brand new sony DRU880S SATA dvd drive boot from any of the remaining Intel ports or the 2 Marvell ports. I am using AHCI mode for both controllers.

I have tried the new caviar black on a Biostar P4M900 FE which has a VIA VT8237 SATA IDE / RAID controller and it is sucessfully detected in BIOS.

That means all SATA ports on the p67 mobo and the new caviar black HDD are working. So are the SATA cables and power connectors.

Then why is the p67 mobo not detecting the new caviar black HDD?????

 

[itzdanielp]

More than likely your BIOS can't detect a 2TB drive...

Some of the older bios have a limit as to what the largest capacity drive they can recognize. Check your documentation to see if it is listed in there.

There is nothing wrong with the drive since it works fine on the other controller, so it probably is just the BIOS not being able to recognize such a big drive.

 

[jaquith]

The 'BIOS' and OS problems are >2TB. Try the tutorial -> http://www.top-windows-tutorials.com/format-hard-drive.html

If needed rather than reinventing the wheel see -> http://www.tomshardware.com/forum/295002-30-asus-p8z68-problem

If your installing Windows then use the Formatting option see -> http://www.youtube.com/v/JyMWz5UEgoI

Note: as mentioned 'jumper' {N/A to your NEW MOBO} - http://wdc.custhelp.com/app/answers/detail/a_id/1337

 

[frstfire]

More than likely your BIOS can't detect a 2TB drive...

Some of the older bios have a limit as to what the largest capacity drive they can recognize. Check your documentation to see if it is listed in there.

There is nothing wrong with the drive since it works fine on the other controller, so it probably is just the BIOS not being able to recognize such a big drive.

Thank all of you for the replies. However, this mobo is Asrock P67 UEFI already at the most current BIOS version. I also have a 320gb HDD containing the same OS for my old mainboard, that cannot be detected by the P67 either.

 

[itzdanielp]

The 320 GB can not be detected at all? or it won't boot off of the drive?

If the drive can not be detected at all I would suggest contacting the manufactuer as it is probably a problem with the SATA controller.

 

[frstfire]

The 320 GB can not be detected at all? or it won't boot off of the drive?

If the drive can not be detected at all I would suggest contacting the manufactuer as it is probably a problem with the SATA controller.

It cannot be detected at all in UEFI, even if it is the only device connected to the SATA ports.

I did contact Asrock 2 weeks ago, there was no reply.

 

[itzdanielp]

Bug em some more is what I say. Sound like a manafacturing defect.

 

[jaquith]

Did you Format it as shown above, see 'Try the tutorial ->'...

Also, if it's on the 'Marvell SE9120' it won't show-up, move it to one of Intel SATA ports.

 

[frstfire]

Did you Format it as shown above, see 'Try the tutorial ->'...

Also, if it's on the 'Marvell SE9120' it won't show-up, move it to one of Intel SATA ports.

Intel ports wont detect it either. It is a brand new HDD fresh out of the antistatic bag.

Come to think of it, I had to retry a fewl times (diconnect SATA power & data cables, clear CMOS) before the mobo finally detects the raptor 150GB so that I could reformat it and install win7. This is the only HDD that I can boot from now on this mobo.

Does this mean a UEFI / BIOS problem instead of hardware, since i have verified with the raptor HDD that all ports are working. What exactly is needed for a HDD to spin up and get detected during boot, SATA power and "power up" signal from the P67 chipset too? Or somehow the UEFI "prerecognizes" a list of HDD makers and models?

 

[jaquith]

You whizzed by my question, did you Try the tutorial ->http://www.top-windows-tutorials.com/format-hard-drive.html The reason I posted the video is because I don't want to write a book of step-by-step formatting.

Otherwise, the most likely problems:
1. WD Firmware see if available - http://support.wdc.com/product/download.asp?lang=en
2. MOBO is bad or improperly installed and has a shorting problem; unscrew all of the MOBO & PCIe screws dangle the MOBO away from anything conductive and supported by a towel. Otherwise if the HSF has a metal backplate this too can short.
3. WD HDD is bad, run Data Lifeguard Diagnostic from WD downloads.

I seriously doubt it's a BIOS problem. However, I always recommend on any new, especially P67/Z68, to only use the latest BIOS.

All fails above then full Breadboarding.

 

[frstfire]

You whizzed by my question, did you Try the tutorial ->http://www.top-windows-tutorials.com/format-hard-drive.html The reason I posted the video is because I don't want to write a book of step-by-step formatting.

Otherwise, the most likely problems:
1. WD Firmware see if available - http://support.wdc.com/product/download.asp?lang=en
2. MOBO is bad or improperly installed and has a shorting problem; unscrew all of the MOBO & PCIe screws dangle the MOBO away from anything conductive and supported by a towel. Otherwise if the HSF has a metal backplate this too can short.
3. WD HDD is bad, run Data Lifeguard Diagnostic from WD downloads.

I seriously doubt it's a BIOS problem. However, I always recommend on any new, especially P67/Z68, to only use the latest BIOS.

All fails above then full Breadboarding.

I didnt skip through. That is about formatting a new HDD once in windows OS. In my case the HDD is not even detected in UEFI. If I dont have my old mainboard still I would not evven know if the HDD is actually working.

No firmware avail for this model.

Strange you mention shorted, my old mainboard that is still with me now used to display almost the same symptoms as this new one, i.e. not able to detect a second HDD in BIOS even with breadboarding. Now that it is outside the case it detects the 2nd HDD.

How do I clear a suspected short if I already have the board on a antistatic bag, but still not reading the HDD?

 

[jaquith]

You know the thing that's driving me crazy is 2 MOBO's in 1 discussion and then problem solving to confuse it even further.

First, regarding the " formatting a new HDD once in windows OS" correct I thought you had both a 150GB & 2TB HDD and you were indeed 'booting' into Windows.

-- Shorting --
Regardless, the problem is a short. Verify that ALL, count them, standoff's are 100% lining-up with the MOBO's screw holes. As standard practice I add thin plastic washers to the tops of the standoffs secured with a dab of silicone; kill 2 birds quieter and no shorting. Further, the I/O shield - make certain none of the 'prongs' are overly bent inward nor bent angularly (off axis).

-- P67 --
Don't have the MOBO on the plastic, place it on 'cardboard.' I also mentioned the HSF backplate, if it's metal the remove it and use the stock HSF. IF a full breadboard, on cardboard, with ONLY the following:
1. Stock HSF
2. One stick of RAM in the DIMM slot 2nd from the CPU
3. NO HEADERS -> NONE; short PWR+ & PWR-/Ground to boot
4. New/different Keyboard or PS/2 Keyboard
5. GPU try 2nd PCIe slot and known good GPU
6. Adequate and Known Good PSU: 24-pin, 8-pin, and 'GPU's' PCIe __-pin
7. Jumper - Clear CMOS
8. Intel SATA2 ports: HDD and DVD
9. Monitor

Then IF that FAILS then RMA the MOBO <or> bad HDD IF Data Lifeguard Diagnostic fails on BOTH MOBOs.

BTW - just format the 2TB if it shows-up on the old MOBO -- use it -- NTFS is NTFS there's no magical difference. Format it again once in the new P67.

 

[frstfire]

You know the thing that's driving me crazy is 2 MOBO's in 1 discussion and then problem solving to confuse it even further.

First, regarding the " formatting a new HDD once in windows OS" correct I thought you had both a 150GB & 2TB HDD and you were indeed 'booting' into Windows.

-- Shorting --
Regardless, the problem is a short. Verify that ALL, count them, standoff's are 100% lining-up with the MOBO's screw holes. As standard practice I add thin plastic washers to the tops of the standoffs secured with a dab of silicone; kill 2 birds quieter and no shorting. Further, the I/O shield - make certain none of the 'prongs' are overly bent inward nor bent angularly (off axis).

-- P67 --
Don't have the MOBO on the plastic, place it on 'cardboard.' I also mentioned the HSF backplate, if it's metal the remove it and use the stock HSF. IF a full breadboard, on cardboard, with ONLY the following:
1. Stock HSF
2. One stick of RAM in the DIMM slot 2nd from the CPU
3. NO HEADERS -> NONE; short PWR+ & PWR-/Ground to boot
4. New/different Keyboard or PS/2 Keyboard
5. GPU try 2nd PCIe slot and known good GPU
6. Adequate and Known Good PSU: 24-pin, 8-pin, and 'GPU's' PCIe __-pin
7. Jumper - Clear CMOS
8. Intel SATA2 ports: HDD and DVD
9. Monitor

Then IF that FAILS then RMA the MOBO <or> bad HDD IF Data Lifeguard Diagnostic fails on BOTH MOBOs.

BTW - just format the 2TB if it shows-up on the old MOBO -- use it -- NTFS is NTFS there's no magical difference. Format it again once in the new P67.

My bad for the confusion as I thought the problem was only the new mobo's UEFI.

Tried breadboarding, this time the new mobo UEFI detected the 2TB HDD, win7 even found this new HDD and installed the AHCI driver. BUT, seconds later after appearing in win7 the new HDD spun down (yes there is a spinning down noise) and did not show up again under disk management. The 150gb raptor is the OS HDD and continues to operate normally together with the SATA dvd drive under win7. On subsequent cold reboots, the new 2TB HDD sometimes spin up upon POST, make some clicking noises to show that UEFI is attempting to initialize it, but spins down again and UEFI fails to detect it. Sometimes it does not even spin up at all during cold boot.

The best part is that the Marvell controlled SATA ports on the mobo fails to detect this 2TB HDD too. Unless the short circuit is not anywhere near the P67 chipset?

 

[jaquith]

The next 'try' is to verify that BIOS = AHCI = Windows = Start = 0; review the following link -> http://support.microsoft.com/kb/922976 you can either use 'Fix It' or change the Start Value = 0 in either case verify in the registry - see -> http://i1013.photobucket.com/albums/af254/Jaquith/AHCI_Start_0.jpg

Then as above, 3. WD HDD is bad, run Data Lifeguard Diagnostic from WD downloads. If the diagnostic fails or doesn't detect the 2TB then RMA the WD HDD

However, I did mention the HSF and IF it has ANY metal to MOBO then that isn't good:
Screw -> | Backplate | Plastic Washer | [MOBO] | Plastic Washer | etc...

{yes every HSF is different the 'idea' is to keep metal off the MOBO!} and no I don't give a rip what the HSF manual says. Otherwise use the stock HSF.

 

[frstfire]

The next 'try' is to verify that BIOS = AHCI = Windows = Start = 0; review the following link -> http://support.microsoft.com/kb/922976 you can either use 'Fix It' or change the Start Value = 0 in either case verify in the registry - see -> http://i1013.photobucket.com/albums/af254/Jaquith/AHCI_Start_0.jpg

Then as above, 3. WD HDD is bad, run Data Lifeguard Diagnostic from WD downloads. If the diagnostic fails or doesn't detect the 2TB then RMA the WD HDD

However, I did mention the HSF and IF it has ANY metal to MOBO then that isn't good:
Screw -> | Backplate | Plastic Washer | [MOBO] | Plastic Washer | etc...

{yes every HSF is different the 'idea' is to keep metal off the MOBO!} and no I don't give a rip what the HSF manual says. Otherwise use the stock HSF.

Breadboarding doesnt work. Im RMAing the mobo. Many thanks to all the replies, especially from Jaquith.

 

[jaquith]

When you get the replacement MOBO also spend $5 on a wrist strap e.g. Rosewill RTK-002 http://www.newegg.com/Product/Product.aspx?Item=N82E16899261005

Then breadboard first. No sense in baking {building} a pie with rotten Apples {bad components}.

Let us know & Good Luck!!!

 

[frstfire]

When you get the replacement MOBO also spend $5 on a wrist strap e.g. Rosewill RTK-002 http://www.newegg.com/Product/Product.aspx?Item=N82E16899261005

Then breadboard first. No sense in baking {building} a pie with rotten Apples {bad components}.

Let us know & Good Luck!!!

Thank you for your troubles. The mainboard was fine. I rmaed the psu instead as it was the faulty component causing all this.

 

[frstfire]

When you get the replacement MOBO also spend $5 on a wrist strap e.g. Rosewill RTK-002 http://www.newegg.com/Product/Product.aspx?Item=N82E16899261005

Then breadboard first. No sense in baking {building} a pie with rotten Apples {bad components}.

Let us know & Good Luck!!!

 

[frstfire]

When you get the replacement MOBO also spend $5 on a wrist strap e.g. Rosewill RTK-002 http://www.newegg.com/Product/Product.aspx?Item=N82E16899261005

Then breadboard first. No sense in baking {building} a pie with rotten Apples {bad components}.

Let us know & Good Luck!!!