- Jul 18, 2017
- 9
- 0
- 510
Hey.
I started running chkdsk /r on a 1TB external HDD to fix some errors so I could clone the drive smoothly, but it's taking so long that I'm starting to think that it might not ever finish.
I know it can often take days to finish, and I know you're not supposed to stop it, but it's literally been running for two weeks now and it still has over 100,000 files to go through.
I heard that chkdsk runs much faster if the drive is connected to the SATA ports on the motherboard, but I don't wanna risk losing my files because there's a lot of important stuff on this drive that hasn't been backed up (hence why I wanted to clone it). Also, I'd have to break the hard drive's case to connect it to the motherboard, which would void the warranty.
At what point is it taking so long that I should just bite the bullet and cancel it? Is there enough truth to the claim that it'll run faster if connected to the motherboard rather than USB to justify restarting chkdsk?
I started running chkdsk /r on a 1TB external HDD to fix some errors so I could clone the drive smoothly, but it's taking so long that I'm starting to think that it might not ever finish.
I know it can often take days to finish, and I know you're not supposed to stop it, but it's literally been running for two weeks now and it still has over 100,000 files to go through.
I heard that chkdsk runs much faster if the drive is connected to the SATA ports on the motherboard, but I don't wanna risk losing my files because there's a lot of important stuff on this drive that hasn't been backed up (hence why I wanted to clone it). Also, I'd have to break the hard drive's case to connect it to the motherboard, which would void the warranty.
At what point is it taking so long that I should just bite the bullet and cancel it? Is there enough truth to the claim that it'll run faster if connected to the motherboard rather than USB to justify restarting chkdsk?
Facebook
Twitter
Instagram