So I was doing a large multi file download that I split into nzb's of 50 files each (each have their own parts and par2). Unfortunately the third part has 2 sub-items that refuse to par2. Now my job gets kicked to the failed status leaving the other 48 downloads repaired but not unpacked.
How do I tell Sabnzbd to ignore the 2 broken downloas and go ahead an extract the 48 that were already repaired?
edit: I tried some random options and I noticed that disabling Enable Quick Check will get the unpack process started. Still not sure what will happen when sabnzbd get's to the bad files though? Maybe it will fail? Maybe it will skip?
Single file
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Single file
Set SABnzbd to paused, then retry from History,
Subsequently go to the details page (click on job name) and remove
the "offending" parts completely.
You may need to remove the actual files manually at that time.
Alternatively use QuickPar to repair and WinRAR to unpack.
Subsequently go to the details page (click on job name) and remove
the "offending" parts completely.
You may need to remove the actual files manually at that time.
Alternatively use QuickPar to repair and WinRAR to unpack.
Re: Single file
Thanks for replying. It did manage to complete the job with the enable quick check disabled. Did not come to the deletion of the offending parts but will keep it in mind, thanks!
Re: Single file
Surprising that disabling QuickCheck solves the problem.
99.99% of the time, par2 causes such problems.
It may be a case of damaged par2 files that (in this rare case) makes QuickCheck fail, but not the par2 tool.
99.99% of the time, par2 causes such problems.
It may be a case of damaged par2 files that (in this rare case) makes QuickCheck fail, but not the par2 tool.