Problem with HDD - not being recognized

[Perene]

Guys, I have a WD 1 TB, that always worked just fine, for years... then, when I send to technicians, they didn't do anything to it, but installed 2 new HDDs and cleaned the computer. I ran HDTune before and after, and all discs were fine. However, for the 1st time HDTune said something different about the WD 1 TB: Interface CRC Error Count.

Before sending to technicians, I had the BIOS updated and Windows reinstalled after a format, due to this problem here:

https://www.youtube.com/watch?v=ZSlzpX9gHkw

Since the beeps stopped (and they continued even after I updated the BIOS), I assumed it was due to the PC not being cleaned.

https://goo.gl/H8yVeq (please check this link)

I used for 2 days, and suddenly the WD 1 TB wasn't recognized anymore.

While using the Windows, it was recognized again, and I saw that HDTune status remained the same (from the GOO.GL link). My guess is that the HD is perfectly healthy, however I have no idea what is causing this. Once I turned off and on again, it wasn't recognized anymore.

And besides that, I noticed the PC while starting didn't go to Windows, and was loading forever. A reset fixed that problem.

Usually when that happens it's a sign one of the HDDs is either dead or dying. I had one with a click of death, and before the actual death of the HDD, the PC was hanging at motherboard splash screen.

So what do you think I should do to fix this problem? What is causing all this?

P.S. HDTune is saying the HDD model is something else instead of WD10EZEX. I noticed it wasn't like that before.

 

[Billb2]

I would suspect the drive.

Micro Center has 1 TB drives for $40

 

[Perene]

OK, here's what just happened:

- The WD 1 TB wasn't being recognized by the OS. As you could see by the previous screenshots. Then I just inserted a pendrive in the USB port, and this software:

http://support.wdc.com/downloads.aspx?p=3

It became immediately by it! But still not by Windows itself. So I ran the diagnostics:

https://goo.gl/QdO5fi

As you can see, nothing wrong. Then the PC was restarted. Guess what happened next?

- The WD 1 TB was recognized again! In the BIOS and Windows! I am accessing the driver now!

And this is the picture from this HDD prior to sending to the technicians:

https://goo.gl/qKhVRy

As you can see, no problem. The Interface CRC Error only happened AFTER I received from them.

Look at the HD recognized as of this moment:

Also:
https://goo.gl/kLo9i2

What does it mean??????? And HDTune just said the number increased:

It was 48, now it's 122.

 

[Elixer]

Try a new SATA cable.

 

[Perene]

The HDD was being recognized again before I send it to technicians. However, I replaced the current SATA cable for another one. I also saw that there's no other cable to be replaced, since the power cable comes from the PSU.

So, if the problem repeats again, I'll send the drive to WD immediately for a replacement. I don't think that will be necessary, considering all tests came negative when it comes to defects in the HDD itself. But it could be very well a defect that doesn't show in surface scan, but is related to not being recognized often.

 

[VirtualLarry]

The HDD was being recognized again before I send it to technicians. However, I replaced the current SATA cable for another one. I also saw that there's no other cable to be replaced, since the power cable comes from the motherboard itself.

There should be two cables connecting a 3.5" HDD. A SATA data cable, that runs between the drive and a mobo's SATA port, and a SATA power cable, which comes from the PSU.

If the SATA power cable is not connected, then it's quite possible and likely that the drive will only be sporadically detected.

 

[corkyg]

OP said the power cable came from the motherboard. That is odd - should come directly from the PSU as Larry said.

 

[Perene]

OP said the power cable came from the motherboard. That is odd - should come directly from the PSU as Larry said.

Ops, sorry, I meant the PSU. Since it comes from the PSU, I can't replace. And if the problem happens again, what are the odds of this being a flaw in the MB?