Quick Drive Test has been stuck at 90% on a My Book 3 TB drive for around 12 hours. Any idea why?
Thanks.
This can be caused by failing disk sectors, software/driver conflicts, drive sleeping settings, or outdated software. You can follow the steps to troubleshoot it:
- Cancel the process and restart the computer.
- Disable Real-time Protection and restart the test.
- Use a third-party tool to view the drive’s health.
- Try a different USB port/cable.
- Update the test software.
Thank you for taking the time to post troubleshooting steps. I greatly appreciate that.
The problem could be due to bad sectors on the hard drive, hard drive aging, or connection issues (loose USB cable or connector), and more.
Here are some possible solutions:
First, stop testing.
Secure the connection using a different port or data cable.
Use CHKDSK or other hard drive diagnostic tools to check for errors.
Immediately back up important data using software to prevent data loss. I’ve been using minitool for years and it’s excellent.
If the problem persists, you may need to contact customer service to replace the hard drive.
Canceling the test, restarting the computer, and disabling Real-time Protection worked i.e. the Quick Drive Test - and the Complete Drive Test, which had also gotten stuck at 90% - completed - both indicating completion with a status of failed.
Then I downloaded CrystalDiskInfo (free) which gave me the details on the problem. I used ChatGPT to analyze CrystalDiskInfo‘s metrics on the drive.
So, the drive is presently looking to be too much of a risk to participate as a backup drive. Well, I can’t complain. I had the drive and its still-working twin (going non-stop) since 2015.
Go into Power Options → Advanced settings → USB settings and turn off USB selective suspend, and also set your plan to High performance so the drive doesn’t keep dipping in and out of sleep mid-test. I’d also check Device Manager → Disk drives → Policies and disable write caching temporarily just to see if stability improves. Given CrystalDiskInfo already flagged issues and both tests failed, this isn’t just a false alarm. It usually points to growing reallocated or pending sectors even if the drive still “works.” At this stage I’d treat it as read-only for anything important, clone what you can while it’s still responsive, and retire it rather than trusting it for backups.
