A few incompletes but Quick Check OK

[dikkiedirk]

I have SABNZBD 0.6.15 installed on my unraid server. Two servers are set-up Giganews as main and pureusenet.nl as fill/backup server. Las week I downloaded a DVD which consisted of 48 RAR files. It finished downloading and went directly to unpacking resulting in: unpacking failed CRC-error. I looked in the History and saw Quick Check OK.

When I downloaded the same NZB in Newsleecher I immediately saw there were 3 RAR-files incomplete. So how can SABNZB say Quick Check OK when there are 3 files incomplete? I looked in the download folder of SABNZB and saw all RAR-files being 68.360 KBytes except the bad ones which were a lot smaller. I also saw none PAR2 file. Can I change SABNZB's behaviour when dealing with such files. Not doing a Quick Check but a full Check. Newsleecher downloaded all files incl. PAR2s and the bad files could be repaired.

[shypike]

Upgrade to 0.7.0.
If you don't trust QuickCheck, disable it in Config->Switches.
It will still do the check, but will also run par2 and give a warning about a difference in conclusions.
So far there have been a few reports like yours, but nothing was ever reproducible
(or just false alerts). That's why we introduced this change in 0.7.0.

[dreamscene]

Every now and again I've been having the exact same problem.
Most recently today with 0.7.4RC2 and an nzb that was not even an hour old. The log shows nothing of significance:

Code: Select all

2012-10-11 09:23:00,774::INFO::[postproc:534] Par2 check starting on Random.Show.S02E22.720p.HDTV.x264-SomeGroup
2012-10-11 09:23:00,774::INFO::[postproc:549] Running repair on set Random.Show.s02e22.720p.hdtv.x264-SomeGroup
2012-10-11 09:23:00,780::INFO::[newsunpack:787] Quick-check for Random.Show.s02e22.720p.hdtv.x264-SomeGroup is OK, skipping repair
2012-10-11 09:23:00,781::INFO::[newsunpack:849] Deleting /media/sabtmp/Random.Show.S02E22.720p.HDTV.x264-SomeGroup/Random.Show.s02e22.720p.hdtv.x264-SomeGroup.par2
2012-10-11 09:23:00,782::INFO::[postproc:563] Par2 check finished on Random.Show.S02E22.720p.HDTV.x264-SomeGroup
2012-10-11 09:23:00,782::INFO::[misc:784] Creating directories: /media/complete/Random.Show.S02E22.720p.HDTV.x264-SomeGroup
2012-10-11 09:23:00,783::INFO::[postproc:330] Running unpack_magic on Random.Show.S02E22.720p.HDTV.x264-SomeGroup
[...]
2012-10-11 09:23:42,924::WARNING::[newsunpack:599] ERROR: CRC failed in "Random.Show.s02e22.720p.hdtv.x264-SomeGroup"
2012-10-11 09:23:42,941::INFO::[newsunpack:205] Unrar finished on /media/sabtmp/Random.Show.S02E22.720p.HDTV.x264-SomeGroup
2012-10-11 09:23:42,943::INFO::[postproc:332] unpack_magic finished on Random.Show.S02E22.720p.HDTV.x264-SomeGroup

Of course most of the time the quick check results are accurate. So I would not want to completely renounce this feature.
I could provide the nzb file, but judging from other board posts regarding this topic I doubt it would do much good.

What does the quick check rely on? The size of the files? Because while manually checking the files of the above mentioned download, I noticed that the file sizes are correct - even for the damaged parts.

Am I right in the assumption that sabs default verification process goes like this (only going to the next level if the previous fails): 1. Quick Check, 2. SFV Check, 3. PAR2?

While not solving the random quick check fails, would it be possible to work around the issue by altering post-processing procedures - i.e. kicking a download that quick checked OK, but failed on unpacking with a CRC error back into the PAR2 stage? That way one would not have to manually interfere.
I noticed from the log that the par2 of positively quick checked files is deleted before the unpacking stage - so I guess something like the above mentioned work around would require some code rewrites :/

[shypike]

Just disable QC.
SABnzbd will still check with QC and par2 and will file a warning
when there's a difference.
QC does the same check as par2.