A secondary internal drive is starting to dissappear (until restart)!

In the last 2 months I've noticed one of my secondary internal drives starting to "dissappear". I can't seem to reproduce it on purpose but it has happened enough times to have me concerned and hoping someone can help either solve or explain what might be happening. At first I thought it was sometimes after the computer had been put to sleep... but then I noticed other times where I actually heard the sound of the "disconnection".

To fix the issue, I restart the PC.
However, when I do, I usually see a message of WDI Resolution Host on the blue restart screen.

No other drives have shown this problem, and I'd never had issues with this one before.

This is a WD 5TB 7200RPM HDD drive (WD5001FZWX).







Is the drive dying? (is that even possible or would it just stop working completely in one shot)
Or could this be an issue with the controller?
Kinda important to know because I dont want to spend a few hundred bucks to replace it if the issue is not the drive itself..

Any troubleshooting help would be greatly appreciated! :)

dalchina said:

Hi, please try reseating it/reconnecting it.

Download and run Hard Disk Sentinel (trial) - portable version available if required- SSDs too. Best instant report right on its GUI I know of- includes a connection check. Please post the result."

Seems fine doesn't it?

In terms of reseating, we are talking about just physically removing the cable and reinserting it?

How do I inspect the event viewer for "related reports"? This sounds like new territory for me...

Thanks @dalchina

I downloaded and ran Fulleventlogview and I seem to have had alot of warnings...and a handful of errors...
Now that it's installed, I'll note the time of the next "disconnect" and cross-reference in this log viewer.

I'll also open the box when I have the chance and inspect / reconnect the cable to the drive.

Will report back when the above is done.

- - - Updated - - -

I have not yet reseated the drive but will do so later today since I have to open the box to put in a new SSD.

However, the issue did happen again, and shortly after waking from sleep the PC. I used the fulleventlogview software as suggested to get a picture of what happens. I don't really understand any of this but posting here in case @dalchina can spot something that might be a larger issue than reseating.

I will reseat the drive later today nonetheless but wanted to post the screenshots.

This one is likely the one thats most relevant as I recognize references to Windows Storage



But here are other ones...

dalchina said:

Hi, I guess the obvious one here is

Event id 157
Does 'Disk 1' correspond with one you think you might have a problem with? You mentioned P...

Good eye! Indeed that is the one.

I'll see what I can do in terms of recabling when I open the tower in a few hours.
It's unfortunate that the other thread is unsolved...I really hope its just a cable thing.
Otherwise I might have to get in touch with WD... maybe they have more info? The drive will be 5 years old in September...

OK! So I reseated the drive to an entirely new spot. Whereas it was previously Disk 1, it is now Disk 2.
Taking it's place as Disk 1 is my new SSD.
I also made sure not to reconnect it using the same connector. In fact, I think I left out that specific connector since I had another option.

By the way, whats the difference between the small L shape connector on the right that "clips on" and the wider 4-colored cable connection on the left that we just push in? I'm assuming one is just to power and the other determines it's position in the disk array and transfers data- but which cable does what?