CRC error and strange behavior with failed jobs

[nzbtuxnews]

Hey there!  I would normally post this under the sticky CRC errors thread, but I am unsure if its 100% CRC errors related or there is some kind of bug in SAB.

Here's what happens:  

I started a job, it went all fine except at the end, when it was time to decompress (unpack), it failed with "CRC Errors".

I went to the incomplete folder and I was puzzled to realize that there were only .rar files, no par2 files or anything else...  The NZB file taken from my indexing site had comments about bad rar files and some body uploaded a new NZB file for the corrupted rar files.  I clicked on retry and SAB asked for a supplemental NZB, so I selected the new NZB file thinking it would download and replace the corrupt rar files.  No success, same story.

Then I went to look at the details of the initial NZB file and saw the list of the files that are included in it.  There is 8 par2 files.  I selected them and generated a new NZB file.  I then tried repair/retry with this new supplemental NZB file but the problem is that the job disappears from SAB's queue.  I discovered under "Status" it says:

There are orphaned jobs in the download folder.
You can choose to delete them (including files) or send them back to the queue.

If I click on Add, the job goes back in the queue, SAB retry to unpack it, but it fails again....

Is it some kind of bug?  The Warnings says:

2011-04-09 19:37:13,536 WARNING: Invalid NZB file 737142-NZB-6625.nzb, skipping (reason=not well-formed (invalid token), line=1925)

Can somebody explain what to do?

Thanks!

[shypike]

Obviously there are things wrong with the NZB file, like missing par2 files.
You find that out already.
SABnzbd has strict naming conventions for par2 files (we're working on that for a later release),
so when someone later posts par2 files they usually have the wrong names.
It also looks like the NZB file is no good, because you get a warning.
Check the NZB file with an editor. Where did you get it?

[nzbtuxnews]

Yeah I agree with you the nzb files are wrong...  Should I keep the download (it's 15gb) or it's totally useless?

Regarding the editor which one are you recommending?

I got the nzb from nzbmatrix .  I can pm it to you if you want to do some testing...

Cheers!

[shypike]

You can email the NZB to bugs at sabnzbd.org
Notepad should be sufficient, it's just to verify that it looks like an NZB and isn't just HTML with an error message.

Re-using the files isn't that hard.
Go to the job folder in "incomplete" (aka the temporary download folder).
Remove the __admin__ folder. Remove any of the RAR files that are suspected.
Make sure that your new NZB file is named exactly as the existing job folder and add it to the queue.
SABnzbd will re-use the job folder and skip any existing file in it.

You may still be hit by naming problems.
In that case run QuickPar and WinRAR manually afterwards.

[nzbtuxnews]

OK I :

1. Deleted the task in SAB's queue (only NZB file not the actual files);

2. Went to the incomplete/job folder and deleted the __ADMIN__ folder;

3. Deleted all the .rar files that "could" be corrupt;

4. Renamed the nzb file EXACTLY as the job folder in incomplete;

5. Re-added the job in SAB's queue;

But the job doesn't reappear and goes in the orphaned jobs (under queue repair)...

Does it indicate a bad nzb file?  Looks normal to me but Im not a reference in that stuff...

[shypike]

Do you get an error message when you add the NZB?

[nzbtuxnews]

I meant to click on the Add to Queue button but clicked on the little X beside and deleted all files... ............

When that happens again, I will post back.
Thanks!