TR Forums

Hello, I have a Intel 335 240gb ssd.
I think I have a bad sector on it or something, when I try to move a certain large video file I get

Error 0x80070570: The file or directory is corrupted and unreadable.

I tried running chkdsk /f, it did not find any errors.
I tried running the Intel SSD toolbox Full Diagnostic Scan, it did not find any errors.
I am also tried moving the file to different location using Defraggler, it succeeded without issues.

But the issue still persists. I have had a similar issue with another large file, and I think I never fixed it, but just deleted the file.

Anybody know what is up?

I had that issue, but with my Samsung 830. Work PC also had the same problem.

I was using Windows 8 at the time, and managed to pinpoint it to an interaction between Win8 and the Intel RST drivers (or just the Win8 version of such).

I eventually moved back to Windows 7 in my home PC, but what fixed it in the work PC was the following:

- Updating the motherboard's BIOS (really!)
- Updating the Intel INF/RST drivers to the latest versions.

Hmm, I figured out what was causing the issue.
A bug in a torrent client.
I was able to recover the file by moving it from drive to drive in Linux, which complained about errors but still kept on going.

*vitali* wrote:

Hmm, I figured out what was causing the issue.
A bug in a torrent client.
I was able to recover the file by moving it from drive to drive in Linux, which complained about errors but still kept on going.

A regular program is not supposed to be able to corrupt a file at the filesystem level.

I wouldn't consider the issue fixed

I would have tried using "unstoppable copier" first before trying to use UBCD or a linux boot disk to copy the file.

morphine wrote:

*vitali* wrote:

Hmm, I figured out what was causing the issue.
A bug in a torrent client.
I was able to recover the file by moving it from drive to drive in Linux, which complained about errors but still kept on going.

A regular program is not supposed to be able to corrupt a file at the filesystem level.

I wouldn't consider the issue fixed

Ditto. A misbehaving application should not be able to cause those types of errors. Odds are you've still got an underlying hardware problem or a buggy device driver.

http://webcache.googleusercontent.com/s ... en&ct=clnk
(link is dead but it google finds it)
According to that other people were experiencing the same problem. I think it's as solved as it's going to get, I just need to use different software.

Based on some of the replies, it sounds like it may actually a bug in the way Windows handles large sparse files (i.e., files which have been explicitly allocated with "holes" in them). The torrent client just happens to be tripping over it.

I've noticed this issue with usenet downloaders too - specifically when downloading ~20 gb files.

sid1089 wrote:

I've noticed this issue with usenet downloaders too - specifically when downloading ~20 gb files.

That would be another data point which supports the "Windows sparse file handling bug" theory. Since multi-part Usenet posts often arrive out of order, I could easily imagine a Usenet downloader utilizing sparse files in the reassembly process.

An OS which allows unprivileged user applications to cause file system corruption has a bug by definition, whether or not the application has bugs of its own.