3TB WD red is not recognized by BIOS

Toggle sidebar Toggle sidebar
E

eyal20122013

Distinguished
Feb 9, 2013
56
0
18,630
Hi,
I purchased a 3TB WD RED, after my WD 2TB failed (after 2.5 years of home use) . First thing I did was connecting it to my computer and make sure the HDD was recognized, which it was. Then I downloaded WD Lifeguard and run it - Full Zero write and afterwards an extended test, which both came OK. Then I initialized the disk to GPT with NTFS file system. Then I shut down and turn my computer again and the HDD seems to be dead (is not seen by BIOS, nor can I feel it spinning, as opposed to before). I tried connecting it to my other computer, but it is the same. I must note that I bought the exact HDD 4 days ago (before this one) and the same thing happen, so I went to the store and got a new one instead, which is the one I referred. I also want to note that I have other HDD's which work fine in that computer, so I don't think the problem was made by my computer (I checked the voltages of each sata power cable and they all seem in the correct voltages). Can anyone please help ?


My system:
MB: P8H67M-Pro (don't remember which version)
OS: Windows 7 Ultimate 64bit
 
Solution
SuperSoph_WD
I'm glad to hear that everything worked out for the best with your new WD Red, @eyal20122013! :)

As for the DLG tool, running the QUICK test every once in a while shouldn't cause any damage on the HDD whatsoever. Even the EXTENDED test is most likely NOT the source of your failed drive, despite it scanning each and every sector which potentially could exhaust a mechanical HDD. Running these two tests every now and then to keep an eye on the WD Red shouldn't harm the drive.

The WRITE ZEROS feature, however, is an entirely different thing in the Data LifeGuard Diagnostic tool. It's not supposed to be run as often as the tests above. This is simply an additional feature that is only recommended when you wish the OS to be reinstalled, or...
Sort by date Sort by votes
E

eyal20122013

Distinguished
Feb 9, 2013
56
0
18,630
Because I wanted a quiet and reliable HDD for my Desktop computer. I don't care if it is aimed for NAS as long as it can serve my purpose. I am not aware of any damage that can arise by using it as a desktop HDD. Is it less reliable than the blue or green one if used in a desktop computer ?
 
Upvote 0 Downvote
why_wolf

why_wolf

Splendid
Aug 28, 2015
3,532
26
26,940
It's just not meant for them to the point that I think they rig them to not like working in Desktops out of the box. The reviews always have people complaining about them not working in desktops.

The only thing really different about them from the other lines is they supposedly have better vibration absorption to reduce their fail rate from working along other hard drives in a NAS environment.
 
Upvote 0 Downvote
E

eyal20122013

Distinguished
Feb 9, 2013
56
0
18,630
This new drive is the only 3TB I have. The others are 2TB and less. I am not sure about WD 3TB reliability yet, until I know for sure it is not a problem with the BIOS not recognizing a 3TB HDD formatted with GPT . I will go to the store and ask the support to check the HDD. I must say that I was considering to buy the HGST Deskstar 4TB H3IKNAS40003272SE , but I read the noise is much louder than WD RED, therfore I decided to buy the WD RED. The RED's are really silent which is a must for me.
 
Upvote 0 Downvote
SuperSoph_WD

SuperSoph_WD

Glorious
Jul 30, 2014
6,758
3
45,960
Hey there, eyal20122013!

I'm really sorry to hear about your bad experience with the WD drives! :( I'd suggest you to try plugging the WD Red in another computer and see how it will get recognized there. Another thing that's worth the try is swapping the SATA cable and the SATA port the Red is connected to, hopefully, it will get properly recognized elsewhere.
If the issue persists, I'd strongly advise you to check in with the reseller or our customer support for assistance.
The drive should still be within the warranty period, so you should be able to RMA it and get a replacement from us.
Here are some useful links from our website that can help you in such unfortunate situations:

Warranty Policy: http://products.wdc.com/support/kb.ashx?id=OOYnPJ
Warranty Status Check: http://products.wdc.com/support/kb.ashx?id=ocsjjG
WD Support contacts: http://products.wdc.com/support/kb.ashx?id=N5HhcD

Best of luck!
SuperSoph_WD
 
Upvote 0 Downvote
E

eyal20122013

Distinguished
Feb 9, 2013
56
0
18,630
I replaced the last one with a new 3TB WD red. I also decided to replace my 7 years old Antec Earthwats PSU (which I was very happy with) with a new Seasonic G-750 gold, just in case there was a slight chance it had something to do with that. I have succeeded to see the new hdd in windows, but I have second thoughts of applying "write zero" and "extended test" with WD lifeguard, since I still am afraid it might had contributed to those killed hdds. Data reliability is very important to me BTW.

My question to you : is it recommended to do those tests one after the other with lifeguard in DOS without damaging the HDD ?

I would also appreciate if a WD representative would answer this question to make it clear and not just a speculation.
 
Upvote 0 Downvote
SuperSoph_WD

SuperSoph_WD

Glorious
Jul 30, 2014
6,758
3
45,960
I'm glad to hear that everything worked out for the best with your new WD Red, @eyal20122013! :)

As for the DLG tool, running the QUICK test every once in a while shouldn't cause any damage on the HDD whatsoever. Even the EXTENDED test is most likely NOT the source of your failed drive, despite it scanning each and every sector which potentially could exhaust a mechanical HDD. Running these two tests every now and then to keep an eye on the WD Red shouldn't harm the drive.

The WRITE ZEROS feature, however, is an entirely different thing in the Data LifeGuard Diagnostic tool. It's not supposed to be run as often as the tests above. This is simply an additional feature that is only recommended when you wish the OS to be reinstalled, or you want to completely wipe out the hard drive so that no data can be retrieved from it (to get it back to its default out-of-the-box state).
Yes, it can also help with the blocking (remapping) of some logical (soft) bad sectors, however, it won't repair all of them. Moreover, it won't be able to fix any bad sectors especially if they are physical (hard), mostly because there's no way to repair such storage clusters.

Long story short, if running the QUICK and EXTENDED tests from the Data LifeGuard Diagnostics for DOS indicate that there are bad sectors and you want to try to fix them. You can most definitely try the WRITE ZEROS command to do so. However, if the first attempt doesn't repair them, I'd not repeatedly attempt these procedures. In such situations, you should just make sure your data is safe and sound, backed up elsewhere and contact our customer support for an RMA request.

Hope I was able to answer your question! Best of luck! :)
SuperSoph_WD
 
Upvote 0 Downvote
Solution
E

eyal20122013

Distinguished
Feb 9, 2013
56
0
18,630
Thanks



 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom