Cloning drive with ddrescue in Linux (using log so I can continue) and the drive stops reading after 3300 megabytes. Every time! What's going on here?

The drive is WD5000AAVS. Doesn't make any noise. Windows just stopped recognizing it one day. Shows RAW in Windows after who-knows how long it takes to show in disk manager.

​

What would make it read 33xx MB then stop? It reads at \~100MB/s for around 30 seconds, then just quits. I'm using a USB adapter because Linux also won't recognize it using the SATA cables. The SATA light on my adapter goes off and it's like the drive no longer exists. So, I "CTRL+C" to stop ddrescue, then turn off the drive and repeat the process.

​

I've recovered around 170GB so far with this method. No bad sectors, or any other errors. Just the fact that it(the drive) runs long enough to net me 33xx additional MB and then quits.

​

Another weird thing is, as I chip away at this drive, the read speeds have slowed to low 90s MB/s, but the drive just reads a little bit longer (40 some seconds) and it still gives me the same 33xx MB haha! So weird.

​

One more thing I just noticed, I have to run the command as soon as the SATA light comes on. If I wait even a few seconds, it'll either not read any data, or read at 65,536B/s and then quit after a few seconds.

​

​