Could not unpack due to renamed archive files

Get help, report and discuss bugs.
dgcurtis
Posts: 28
Joined: 09 Sep 2014, 15:11

Could not unpack due to renamed archive files

Post by dgcurtis » 02 Aug 2017, 01:54

I am running 19.1 on Centos 7 and having an issue with certain nzb files. The health check on the downloads are fine but it fails the par check and won't unrar. I've downgraded to 19.0 and 18.1 but it still has the same issues with these certain nzb files. The only error in the logs is "Could not unpack *REMOVED* due to renamed archive files". Looking at the incomplete download directory, it seems like nzbget is running into issues with some of the obfuscated file names. It isn't happening with every download though; only a few here and there.

For thoroughness, I installed sabnzbd on the same server and added the nzb files to it. It was able to download and unpack the files properly so it's not my usenet providers.

I can provide the nzb files in question.

Thanks

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Could not unpack due to renamed archive files

Post by hugbug » 02 Aug 2017, 05:20

Click on an item in history, then button "Log", then button "Save to file". Post the file here (via pastebin.com).


hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Could not unpack due to renamed archive files

Post by hugbug » 02 Aug 2017, 16:08

Thanks, please send me the nzb to nzbget@gmail.com.

Can you also make another test? Activate option DirectRename and try the file again.

dgcurtis
Posts: 28
Joined: 09 Sep 2014, 15:11

Re: Could not unpack due to renamed archive files

Post by dgcurtis » 02 Aug 2017, 16:26

I sent the nzb files a few minutes ago.

I enabled DirectRename and restarted but no luck. It seems better because all of the files exist (previously there were many missing files). I tried manually verifying the par file and this is the result:

Repair is required.
27 file(s) exist but are damaged.
You have 868 out of 2000 data blocks available.
You have 1 recovery blocks available.
Repair is not possible.
You need 1131 more recovery blocks to be able to repair.

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Could not unpack due to renamed archive files

Post by hugbug » 02 Aug 2017, 17:07

Both files work OK for me, tested with and without DirectRename.

It seems the files get corrupted when written to disk. That would explain why par-rename can't rename and why external par2 reports errors.

Please post your config file (via pastebin), remove logins/passwords first.

What's your OS and device? Are you using nzbget installer from nzbget download page?

dgcurtis
Posts: 28
Joined: 09 Sep 2014, 15:11

Re: Could not unpack due to renamed archive files

Post by dgcurtis » 02 Aug 2017, 17:26

It's a Centos 7 VM (kvm) and the download directory is an nfs mount. I use the installer from the nzbget site. I pointed the sabnzbd install to the same directory for downloading.

Here are the nfs options:

(rw,relatime,vers=4.0,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,port=0,timeo=14,retrans=2,sec=sys,local_lock=none)

Here is my config with server info and passwords removed:
https://pastebin.com/kxCxsALy

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Could not unpack due to renamed archive files

Post by hugbug » 02 Aug 2017, 17:40

The config looks OK. Please delete log-file, redownload test nzb, then send me the log-file (option LogFile). It contains more info than nzb-log from history; maybe sonething useful.

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Could not unpack due to renamed archive files

Post by hugbug » 02 Aug 2017, 17:43

Do you have spare 500GB disk space on VM? Can you try downloading to local disk for option InterDir?

And as another try disabling option DirectWrite (when using NFS).

dgcurtis
Posts: 28
Joined: 09 Sep 2014, 15:11

Re: Could not unpack due to renamed archive files

Post by dgcurtis » 02 Aug 2017, 18:53

I've emailed the log file.

I tried disabling DirectWrite but the same thing happens. I'll see if I can get some more local disk space for the VM.

Post Reply

Who is online

Users browsing this forum: No registered users and 58 guests