CHKDSK taking too long
Solved
olarm81
Posted messages
28
Status
Member
-
Sannin_WD Posted messages 4316 Status Member -
Sannin_WD Posted messages 4316 Status Member -
Hello,
For over 13 hours, (! ) one of my faulty hard drives has been stuck at 8% in chkdsk. It started running at startup. Should I keep waiting or permanently dispose of this 2.5" HDD?
Thank you
Configuration: Windows / Chrome 46.0.2490.80
For over 13 hours, (! ) one of my faulty hard drives has been stuck at 8% in chkdsk. It started running at startup. Should I keep waiting or permanently dispose of this 2.5" HDD?
Thank you
Configuration: Windows / Chrome 46.0.2490.80
2 answers
-
Hello,
I think it's pointless to insist unless you have important data to recover.
If a chkdsk takes that long, there's a problem. Can you tell me what chkdsk is saying?
--
HDD RECOVERY INC.
Advisor and hard drive specialist.-
Indeed, it's pointless to insist. It's not a big deal... The chkdsk was triggered on rebooting the PC under Windows 10. Therefore, the classic "dos" window is not displayed, and the progress is shown in % without any other details about the situation.
Thank you.
(more information in the following post.)
-
-
Hello olarm81 :)
In my opinion, @Maco_57 is probably right … apparently a problem is starting to appear. However, it is important to note that it is not good to interrupt a CHKDSK. It is advisable to let it run its course.
By the way, @olarm81, what switches did you specify for the CHKDSK (/F, /R, etc.)? Does the 2.5" HDD contain data that you haven't backed up anywhere else? If you get back to your topic, could you share a bit more details about the issues this HDD is causing you and how it is connected to your computer (internally, directly to the motherboard, or externally, via an adapter/external enclosure) :)
Feel free to let us know what happens next :) See you on the Forum!
-----
If you found the answer to your question, please click on Resolved to help other members with the same issue ;)-
Hello.
Yes, a big issue with this HDD... During the startup check, it was correctly analyzing the disk named "G". That was indeed the right one. However, to reassure you, I successfully recovered the data via a boot from a CD with Ubuntu. Then, I connected the HDD using the internal connectors (available on this work PC!)
In conclusion, and out of resignation, the choice of a new SSD is necessary, and I would say that I have solved my problem.... New disk, clean new installation.
Thanks, friends
Have a good day. -
-
