Hard disc errors...
Author
Discussion

NiceCupOfTea

Original Poster:

25,607 posts

282 months

Wednesday 3rd January 2007
quotequote all
Copying some big files from one machine to another over the network, having a bit of a problem with some files.

Eventually find that some of the files are apparently corrupted. Strange, it's the system disc and have had no problems since it was last formatted a year or so ago. When I try to copy the files in question, I get a CRC error.

XP Check Disk does the level 1 check, and then at the end of level 2 just says "unable to complete disk check".

I defragged the disk (it's a 120GB, NTFS formatted, about 75% full). Told me there were some files it couldn't defrag (the same ones that won't copy). They are mostly but not exclusively huge files (mostly 10-80MB, with a 4 GB and a 12 GB file) - they're mostly mp3s and big video editing files.



Doing a chkdsk from DOS came back with :

chkdsk said:
The type of the file system is NTFS.
Volume label is WINDOWSNT.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Correcting error in index $I30 for file 23584.
Correcting error in index $I30 for file 23584.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.


I've checked all the connections, and I'm now reading it in a different machine with different cables but with the same results.

All this would be fair enough, but I seem to be able to read/watch all the files in media player without drama!

What's going on? Do I risk corrupting them by letting chkdsk fix the errors?



Edited by NiceCupOfTea on Wednesday 3rd January 20:38

GreenV8S

31,027 posts

315 months

Wednesday 3rd January 2007
quotequote all
Probably the best bet, although I'd have nagging doubts about whether it was simply a large drive/BIOS/driver type problem. To be on the safe side I'd be inclined to start with the smaller files, copy to a new file and see whether that had similar errors.

SneakyNeil

9,292 posts

268 months

Wednesday 3rd January 2007
quotequote all
I'd take a backup of everything you can, then cross your fingers and do a chkdsk c: /f /r (you'l have to press 'y' and let it reboot to finish it)
chkdsk is quite good on ntfs, hardly ever makes it worse.