Force downloading on a torrent I started

[zeens]

Hey, I've been using torrents for years and I've never seen this happen, and I'm stumped on how to fix it.

I started a torrent- there is nothing for me to download because I originated it. I shared it on the tracker I use. It went fine for a few hours, and then I suddenly noticed it said it had zero seeds on the tracker. I check Vuze and see this:
[Image: nQZHpnn.png]
[Image: MgtmzQR.png]

Nothing has changed in the files or the drive since I started the torrent. The folder and files are NOT read only. I forced re-check. I stopped the torrent, copied my backup of the file over it, and started the torrent again; in this case, it was fine for a bit, then did this again. I'm stumped and have no idea what's going on, and none of the peers can properly finish it because of this.
It's thrown no errors at me, and resetting both Vuze and my computer provide no improvement. Any help would be appreciated.

[parg]

So when you force-rechecked it it came up as 99.x% and you had to copy the backup over, recheck it again and then it went to 100%? And then it subsequently failed and went back to incomplete?

Maybe you've got a failing hard drive? When seeding a torrent Vuze runs a low-priority recheck in the background looking for corrupt blocks and if it finds any it will kick the download back into a downloading mode in an attempt to recover.

[zeens]

So when you force-rechecked it it came up as 99.x% and you had to copy the backup over, recheck it again and then it went to 100%? And then it subsequently failed and went back to incomplete?

Maybe you've got a failing hard drive? When seeding a torrent Vuze runs a low-priority recheck in the background looking for corrupt blocks and if it finds any it will kick the download back into a downloading mode in an attempt to recover.

 

While that's a good theory, it's not it- I know the drive isn't failing and this is the only torrent that's doing it. I should have said that before. Other torrents I've made aren't doing this, neither is anything I'm seeding that I didn't create. I even tried moving the torrent data to a different drive to be sure though and it does the same thing.

[GaryE]

Every time I have heard of a story similar to this it is that some file changed for some reason.

However, that is clearly not the case here because you recovered the file from a backup.

My first thought would be a failing HD as well.

It has got to be something along those lines.  But what would only effect one file . . . not a bad bit of memory . . . nothing other than a HD with bad sectors.

If it is not your HD I do not know.

Just to completely rule out the HD try running a S.M.A.R.T. test on your drive and see what happens.  I suspect it will show no major problems but a S.M.A.R.T. test will for sure tell everyone for sure if there is a problem with the HD or not.

If it is not the HD then we can try to think of something from there.

[zeens]

Ran a test. No problems.
[Image: VmME3kk.png]

[fields]

That is one thing which I myself wanted report long time ago, I've got one that ostensibly problematic disk drive, which causes seeding torrents goes to downloading.

S.M.A.R.T. on this drive also good. I think it's really disk drive issue, or maybe the RAM problem, didn't yet kicked a RAM with GoldMemory tool (have an opportunity to do that), also didn't made an complete chkdsk for that bad drive, only partial, 'cause it take a long time.

I'm not sure, but can be there an probability that thing causes by client itself? Or maybe by some destructive, hidden and implicit activities of anti-bittorrenting agencies & their workers over downloading contents, user's disk drives and even some stealthy on the fly, realtime & mass editing and manipulations over client's code & behaviors?

I do not rule out literally everything.

[parg]

Is it always the same pieces in the same file that become corrupted?

[fields]

Bad, never haven't taking a look to that important thing, but now will try see and track.