SABnzbd Forums

I've redownloaded the same nzb today and no error ::

OOOOOOOOK this one was fun (not)

I queue this nzb which includes an entire season of 22 eps.
It starts downloading and all seems fine.... 1 hour late I see it has only unpacked ep 1 and it goes on downloading the rest with par files included or not. Besides the no unpacking as it goes everything seems fine.
3 hours late:
Retry blah blah Corrupt rar file.

StatusFailed
Size51.0 GB
Categorytv
PathC:\Users\............\complete\_FAILED_...............S06.....................
Source..................S06.......................nzb
DownloadDownloaded in 2 hours 33 mins 56 seconds at an average of 5.7 MB/s
Age: 637d
1 articles were missing
Serverssecure.news.easynews.com=4.0 GB, reader.easyusenet.nl=46.8 GB
Repair[12-285707] Verified in 28 seconds, repair is required
[12-285707] Repaired in 5 seconds
[10-285707] Verified in 35 seconds, repair is required
[10-285707] Repaired in 4 seconds
Unpack[.....................s06e21.....................][C:\Users\..........................\incomplete\...................S06......................\..................s06e21....................r09] Corrupt RAR file
..................s06e21......................][C:\Users\.....................\incomplete\.................S06.....................\.....................s06e21............................r09] Corrupt RAR file

I check the complete folder and only ep 1 is in there
I check the incomplete folder and there is only a few pars mostly for the subs proof etc.
The 51GB are nowhere to be found ::poof::

..... and with this I'm sorry but I'm back to that 2.3.0 that I downloaded by mistake but seemed fine so far...............

This will not be fixed until really 2.3.0. Season packs where many of the file sets have the base name are horrible. How can sabnzbd distinguish what sets and par2 belong too each other when they all have the same names?
Your 2.3.0 is the same as 2.2.1RC1 when it comes to this.

Could you send me that NZB for testing for 2.3.0? safihre@sabnzbd.org

It should be fixed in 2.2.1RC2.