I don't know if this has already been answered somewhere so I apologize for the re-post. I've noticed that sometimes files that were previously downloaded and successfully completed (Azureus listed them as finished) come up in the hi-90% completed range when I go to re-seed them later on. This usually happens after disconnecting and deleting the used torrent after the files have finished downloading and I've uploaded as much as I can at that time. This is especially common with mp3 files. Does anyone know how to fix this problem? It's really frustrating when I try to seed a file I know was downloaded completely but can't. Thanks!

I used to be a hardcore Azureus fan in the past and never experienced anything of that sort. But unless it's a fault in their recent versions, then I wouldn't know.
To give it a quick check could you download uTorrent and try to load the files in there and see if uTorrent recognises it as 100% or not. This may tell us what the problem could be.

this happens for me sometimes. Never figured out the reason

i have answered this in detail earlier too....

in short : there is no real solution as this is not a bug in torrent client but in way OS handles file I/O... 99% we get this error in first or last section of downloaded file.. cauz at times file spans out of the OS sector (4mb)... so when we delete / move adjacent file.. some section of our torrent file looks to be deleted and hence hash fails ...

setting this value in utorrent (advanced) to true helps alot :-

prio_first_last_piece

google ^^ and you can get details...

there should be something similar in other clients also...

hi
i got a message that i got to reseed a torrent that i downloaded earlier plz can any one tell how to reseed it again.