• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

CRC error in one file

Kyohe

Weaksauce
Joined
Aug 28, 2004
Messages
97
So I try to go to one folder on my HDD, whenever I do it starts to chug and makes some intereting sounds. I eventually tracked it down to this one file that when I try to delete it, it gives me a "CRC error". I'm hoping if I can delete that file then the slowing down will go away, but it won't let me delete it! What can I do to get rid of the file? Is there a program that can ignore the CRC stuff and delete it?
 
problem is that it's a CRC error which means that the filesystem itself isn't sure how large the file is or what the contents of it are. I honestly am not sure how to go about tackling that...the only times I've seen CRC errors pop up are when a hard drive is about to fail.

Have you tried deleting it from the command line? Or perhaps from linux using captive?
 
Well it's not on C:, it's on a third HDD that I just put into my brand new computer. I really think that just that one file is corrupt, since the rest of the drive runs perfectly, but hey you never know. As for a command line, the XP recovery console is the only way to get to anything resembling DOS these days that I know of. And that only let's you browse C right...? How would I get to drive F:?
 
windows xp has a normal dos command shell that you can run inside of windows.

start ----> run -----> type "cmd" and hit enter.

From there it's just a normal dos shell. Try from there and see what happens...I don't think it will work but it's worth a shot.
 
Yeah it is a good sign the drive is starting to fail. One method that has worked for me is to run check disk on Windows and have it fix any errors.
 
Back
Top