Incomplete files on WHS again, is there a pattern?

[isofan]

Hi,

I am still having huge problems with *some* (but not all) downloads I make using Sabnzbd on my WHS machine. Last night, I had a download of multiple archives, each of the different parts was supposed to be exactly 14.649 bytes in size.

When the download finished, around 70% of the files were correct. The rest of the files was smaller, but not by a random amount of bytes, but all by certain multiples. Have a look at the explorer screenshot I made:



I noticed that most of the files were instead 13.899 bytes in size. I have seen the following filesizes:
14.649 (correct)
14.250
13.899
13.149
12.750
12.399
12.000

This can't be a coincidence, I guess there must be some reason why some files are downloaded missing some bytes. Of course, when I redownload the files, they are correct, at least most of the times.

This only happens on my WHS machine (Sabnzbd installed on C:\ downloads go to D:\, the unpacked files then are moved to shares on the WHS), never on any of my clients.

I still have no idea why this happens, but maybe these strange filesizes could give a clue to any developer?

Of course, I have tested my hardware, because I thought there might be defective RAM, but 24hours of Memtest86 and nother 24 hours of Prime 95 Torture tests didn't cause any errors.

At the same time, I get warnings in the log that look like this:

2011-02-08 19:26:30,374 WARNING: missing

Sometimes, it also says "missing from all servers" instead of only "missing". What exactly does that mean?
But when I retry, these files are there!

What may be going on here?

[shypike]

Two possible causes:
1. a bug in SABnzbd (but a very rare one to occur)
2. temporary problem at astraweb

The fact that the logging says the articles are missing means
that a) SABnzbd knows they are needed and
b) has received a message from astraweb saying it doesn't have the article.
Simple timeouts would make SABnzbd retry forever.

Normally I'd say it was caused by deletions due to DMCA notices,
but you say a retry solved it, so that's very unlikely.

[isofan]

Hi,

I have investigated this issue further. Fact is:
- it happens with ALL downloads from 2 different usenet providers. But if the single archives are bigger, the chance for a successful repair are much higher, therefore I didn't notice that in the past, because the absolute amount of missing filesize is about the same for big files, so the relative amount of missing data is much smaller with files that are each 50 or 100MB in size, as with 15MB files. These are most likely to be repaired

- about 10-20% of a download job are defective like described, i.e. the files are a few hundred bytes smaller than expected. When redownloaded, again 10-20% of the files are too small, but it's different files.

- it only happens on my WHS, same provider on my XP machine and everything is fine.

- finally, it only happens with SabNZBD, any other clients I have tried on my WHS so far produce fine results. Other download tools like JDownloader that run on my WHS don't have similar problems either, although this is another pair of shoes

Actually, it must have something to do with WHS, or with the hardware. Note that the defects occur right after downloading, i.e. there has not yet been a repair attempt when the files fail.

I am totally desperate of what is happening there, since I really want to use Sabnzbd as my favourite download tool for usenet stuff. Is there any more input I might give to help solve that problem? I am absolutely willing to provide as many data as possible.

[shypike]

I have no idea.
My WHS box with SABNzbd has downloaded many Terabytes last year.

That was with the Alpha's of 0.6.0.
I can make you a release tester for these.
It also has true Windows Service support.