What's wrong with my hard drive? (100% active time, no usage)

[DarkEnergyNetwork]

Since the 27th my 1tb WD hard drive I use for storage has been having issues. If I copy data to/from it, or do any extensive data accessing, it will occasionally stop copying and in task manager it will show 100% active time with and read and write speed at 0. Sometimes it disconnects as well. Sometimes it disappears from explorer and disk management. Other times it disappears from explorer and shows up in disk management as having a RAW partition. And another time it disappears from explorer and shows up in disk management as not being initialized. It's completely random. A restart usually fixes this problem but sometimes I have to restart more than once to fix it. When it shows 100% active time, I can't hear the HDD doing anything. Sometimes when copying it goes between actually copying the data and 100% active time with no data copying. Sometimes it recovers, but sometimes it disconnects. I've tried a different SATA cable AND a different SATA port. That didn't fix it. I've tried doing an Windows error check and it came out fine.
Here's where it gets random again. I've used the WD Data LifeGuard Diagnostics tool. Sometimes it passes, sometimes it fails (sometimes saying something about too many bad sectors, other times a long error summed up as "Interrupted by hard or soft reset"). And sometimes when it fails, it disappears from the computer again. In Event viewer I'm getting tens of thousands of events about the disk. They are always the same three events.
One is ID 51 "An error was detected on device \Device\Harddisk1\DR1 during a paging operation."
Another is ID 129 "Reset to device, \Device\RaidPort0, was issued." (It's not in RAID and there are no RAID drivers installed)
The last is ID 153 "The IO operation at logical block address 0x484eb300 for Disk 1 (PDO name: \Device\00000036) was retried." (The block address is different in each error for that ID)

On the 27th (the day it all started) I also was getting a 4th error in Event Viewer:
ID 140 "The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.
(A device which does not exist was specified.)"

I know this was a long read, and thanks for reading all of it (If you reached this point), I had to explain it in detail for it to make sense.

 

[Ralston18]

I think the Event Viewer logs pretty much indicate that the drive is failing/failed.

WD Data LifeGuard results seem to support that.

Hopefully you have your important files all backed up. If not, try to do so immediately.

Just out of curiousity how old and how full is the drive?

 

[DarkEnergyNetwork]

I think the Event Viewer logs pretty much indicate that the drive is failing/failed.

WD Data LifeGuard results seem to support that.

Hopefully you have your important files all backed up. If not, try to do so immediately.

Just out of curiousity how old and how full is the drive?

The drive is 3 years old. It's a 7200rpm one. It has 85.8gb free. (90% full)

 

[Ralston18]

Between the age and and the drive almost being full I suspect the drive has probably seen enough use to push it towards EOL (End of Life). As the drive fills more and more mechnical work is done to write and read files into any remaining spaces (fragmentation).

Have you ever run any disk cleaning or defragmentation on the drive? Doing so might clean things up enough to stablize its operation and performance.

However, if the drive is truly, physically failing such actions may administer the final blow.

For the moment just go "on hold" and see if anyone else offers further comment or suggestion. I have seen a few postings within this forum from WD folks. Hopefully one of them will note and respond to your post.

 

[amtseung]

Between the age and and the drive almost being full I suspect the drive has probably seen enough use to push it towards EOL (End of Life). As the drive fills more and more mechnical work is done to write and read files into any remaining spaces (fragmentation).

Have you ever run any disk cleaning or defragmentation on the drive? Doing so might clean things up enough to stablize its operation and performance.

However, if the drive is truly, physically failing such actions may administer the final blow.

For the moment just go "on hold" and see if anyone else offers further comment or suggestion. I have seen a few postings within this forum from WD folks. Hopefully one of them will note and respond to your post.

If possible, back up your suspected failing drive to another drive. If it lives through the back up, then defrag the suspect drive. If it dies, seizes up, and goes silent during the back up, then you know your drive was failing, post hoc. If it dies during the defrag, then you're still safe with the back up.

 

[DarkEnergyNetwork]

Between the age and and the drive almost being full I suspect the drive has probably seen enough use to push it towards EOL (End of Life). As the drive fills more and more mechnical work is done to write and read files into any remaining spaces (fragmentation).

Have you ever run any disk cleaning or defragmentation on the drive? Doing so might clean things up enough to stablize its operation and performance.

However, if the drive is truly, physically failing such actions may administer the final blow.

For the moment just go "on hold" and see if anyone else offers further comment or suggestion. I have seen a few postings within this forum from WD folks. Hopefully one of them will note and respond to your post.

I've run a defrag on this drive a few times. I know for a fact it wasn't over 5% fragmented. I have most of it backed up but I can't back up everything because I don't have another 1tb laying around. I will be getting another hard drive soon, probably a 2tb.