File.Copy freezes on damaged file

Question

I am trying to copy files from an old drive to a new drive. The problem is that on the old disk there are (I can only guess) some damaged disk spaces, and any attempt to read from some of these files leads to what seems like some kind of endless loop. There are a lot of problematic files in the files I want to copy, and when it gets to the first one, my application just sits there, doing nothing until I stop it. I was hoping that I could get around this by writing a special program for recursing through directories, copy the files one by one and catch any errors that occur in separate copy operations, but never get to that — it just sits there and sits there and sits there. The only way to stop this is to physically disconnect the problematic hard drive - do not stop the program,trying to finish a process or something like that.

I am somewhat puzzled by how to proceed. Given that such an error occurs, is there a way to automate this process? Does anyone have experience with this?

Answer 1

I assume that you are using copy methods on the standard System.IO classes (Directory / DirectoryInfo / File / FileInfo)?

Have you tried copying files from FileStream? To prevent these errors, you can set ReadTimeout in the stream (stream.ReadTimeout). This way you get exceptions when the Read () operation takes too much time. And you should also get errors if the file cannot be opened.

Answer 2

, HD , HD . , CRC, , .

, .

, , , , ( google ). , . ..

Answer 3

, , #...

( clung clung noise), chkdsk.

, chkdsk , , ddrescue ( Google "" ").

Answer 4

, CBD (Copy Bad Disk) - , : , - ..