PLEASE HELP - HDD Won't Initialize

Ewhitten1980

Reputable
Mar 8, 2015
2
0
4,510
Hey everyone. Ok before I begin, let me just preface this by saying that I have scoured the internet and these forums for the problem that is specific to mine. Although there are many similar cases, I can't seem to find a solution to what I'm dealing with.

Let's start. I recently purchased a brand new Western Digital Caviar Black Internal HDD. I went ahead and installed it into one of my free HDD bays and proceeded to connect the power and SATA cables to it. I booted up my computer and went to Disk Management. Upon load, the prompt comes up to initialize the drive, which I did using MBR. I went through the process in assigning a drive letter and naming the drive and then format. I've done this with hundreds of drives with no problem. As the HDD starts formatting, all seems ok, until the Disk Management windows show up as "Disk Management (Not Responding)." The window continued to stay like that and I let the PC do it's thing knowing that this was taking abnormally long. Regardless I continue to let it work through hoping it would complete and it ended up failing. I restarted the PC and tried to do it again...only this time I get "Won't initialize - Data error - Cyclic Redundancy Error." This is a brand new drive. I talk to a WD rep and he says that's odd. Since the drive was brand new, they ended up sending be a swap...another brand new unit which I received the next day. I thought, ok...maybe I got one in a bad batch or something.

So...here we are with the SECOND BRAND NEW drive. Guess what....the SAME EXACT THING HAPPENS. So I'm beside myself. I've never seen this happen. On another note, I installed another HDD in my system and it installed without a problem. I've tried different cables, a different SATA port and I'm stumped. I can't get either brand new drive to initialize and both now say Cyclic Redundancy Error.

PC Specs are: MSI Z97 Gaming 5 M/B, Intel 4790K CPU, 16GB DDR3 2133Mhz RAM, MSI GeForce GTX 970 GPU, and other HDD's are: Samsung EVO 850 250GB SSD (Main OS Drive), WD Caviar Blue 1TB, Toshiba Canvio Connect 2TB External HD. EVGA 850W 80+ Gold PSU, running Windows 10 Pro.

Any ideas why I can't get these two brand new drives to initialize? Keep in mind...they aren't visible in any windows nor do they have a letter assigned to them, so i can't run any chkdsk type operations on them. Thanks!!
 
Solution
I'm truly sorry to hear about your unfortunate experience with the WD HDDs, Ewhitten1980! :( You did a really awesome job with the troubleshooting, by the way! Have you tried installing & initializing the WD Black in another computer? Just to see if the error will still be present. Even though you can't run chkdsk, you can still use WD's Data LifeGuard Diagnostics for Windows if the HDD is detected in Device Manager and Disk Management. Running the QUICK and EXTENDED tests will help us determine what is the health and SMART status of your replaced WD Black drive.

I'd advise you to get in touch with our Customer Support again and let them know about this issue.

Keep me posted with the troubleshooting, though...
I'm truly sorry to hear about your unfortunate experience with the WD HDDs, Ewhitten1980! :( You did a really awesome job with the troubleshooting, by the way! Have you tried installing & initializing the WD Black in another computer? Just to see if the error will still be present. Even though you can't run chkdsk, you can still use WD's Data LifeGuard Diagnostics for Windows if the HDD is detected in Device Manager and Disk Management. Running the QUICK and EXTENDED tests will help us determine what is the health and SMART status of your replaced WD Black drive.

I'd advise you to get in touch with our Customer Support again and let them know about this issue.

Keep me posted with the troubleshooting, though. Good luck!
SuperSoph_WD
 
Solution

Ewhitten1980

Reputable
Mar 8, 2015
2
0
4,510
Thank you for your reply. Yes, I have ran the WD Data Lifeguard utility and for both drives, I get a "too many bad sectors" message on both drives with a "Failed" status.