FUBARinSFO Posted August 14, 2008 Report Posted August 14, 2008 Hi:I'm migrating 150+ 100% complete torrents from Azureus/Vuze to utorrent. Most of the torrents are migrating OK: "checking" proceeds to 100%, then torrent is seeded or seed queue. But some of them fail the hash check and start downloading the files all over again from zero. The check thinks it may have 37, say, out of 650 pieces for example. I've reinstalled Azureus, loaded an offending 1.7 GB file set (torrent) and it checked it out OK, loaded and started ready to seed. I've checked and rechecked paths, etc, and the path pointers all look OK (esp since I can see no diff between the 5-10% that are failing and the ones that proceed to 100%). Needless to say, I've had to abort this migration before I lose all my good files.Can't seem to come up with the magic set of keywords in search which would reveal the answer to this problem in prior posts (migration, hash check, checking). Thank you in advance for your help.-- Roy Zider
thelittlefire Posted August 14, 2008 Report Posted August 14, 2008 ... If they don't recheck to 100%, they are incomplete... or you're running http://utorrent.com/faq.php#Incompatible_software which is corrupting the reading of data from disk.
FUBARinSFO Posted August 14, 2008 Author Report Posted August 14, 2008 Yes, I'm using utorrent 1.8, under Windows 2003 Server.Clearly from my post they are not "incomplete", as Azureus would not have verified them as 100% -- nor would the .rar and .sfv checked as well.As for "incompatible software", Azureus doesn't have that incompatibilty, evidently.Further to this -- I set up a little test structure and was able to get the original problematic .torrent to hash its files to 100% OK. At the moment I have no explanation for the discrepancies. It may have to do with an overload of 50+ .torrents being migrated at the same time, but that would only be a guess. Or with some sort of interference from a background task such as disk defrag that it doesn't recognize as denying access to the cluster and throws an error instead.Update: problem confirmed again. Attempted migration of 20 folders over to utorrent, in 10-folder batches. Two of the torrents had early failures in the hash check, and opened up for downloading. Same .torrents that failed in earlier larger original migration attempt. These are complete .torrents that pass Azureus hash check.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.