Last week on my laptop fair few files got corrupt. I cannot rename them, copy them or delete them. Files belong to visual studio so I cannot compile some of my projects, which I need to finish by tomorrow. I get I/O device error. I have had similar issue about a month ago and running check disk utility seemed to fix it. Last time it ran for 3-4 days and on day 4 it got stuck at step 2 of the CHKDSK half way through but once I restarted my PC it had fixed all issues.
Now I am having the same issue, however this time I have had my CHKDSK running for 2 days now and it just got stuck on file 350,064 of 386,050 and hasn't progressed any further for 2 days. I tried to restart like last time but it didn't fix my files. I wonder what is wrong and why it gets stuck. Are there any other good FREE check disk utilities I can use or other switches with chkdsk that I should be trying (if so, how do I do that)? Thanks
51 Answer
This sounds a lot like you have a damaged hard drive, which is probably what caused the corruption in the first place. When a program tries to read a bad sector on a disk, it will fail, causing the disk to attempt to read it again. If the application is not designed to time out the reads and move on, they can get stuck forever.
Because very few programs, including filesystem drivers, are designed to deal with bad clusters in this manner, recovering the data is problematic.
If you just need a few files, you can try booting the system up with a linux livecd, and then mounting the disk as read-only and disable integrity checks. As long as the critical filesystem structures and the files you want are on good sectors, you should be able to recover them - from there, you can just discard the harddrive and replace it with a new one and reinstall everything.
If you don't have a good backup or the filesystem is damaged, it'll probably be easier just to re-image the data onto a new drive. You'll need a tool like dd-rescue or CloneZilla running with the -rescue option (or any of a number of other tools which are designed to handle this) to make a clone or image of the bad disk and write it out over the network or to another disk on the system. Once the data is on a properly working disk, you can then attempt proper repairs on the filesystem and recovering your files.
