Page 1 of 1
Unpacking failed, an expected file was not unpacked
Posted: February 6th, 2015, 1:17 am
by dvdwsn
As of two Sundays ago, I've gotten the "Unpacking failed, an expected file was not unpacked" error for every file, except for one.
The weird thing is, the files are all in my "Temporary Download Folder" and unpack manually and play fine.
Also odd. Looking in the " C:\Users\Administrator\AppData\Local\sabnzbd" folder, the last log entry is from Dec. 16th 2014.
Any ideas?
Re: Unpacking failed, an expected file was not unpacked
Posted: February 6th, 2015, 3:19 am
by shypike
Are all reported files actually present?
We see the error a lot on operating systems which have non-Unicode file systems, mostly Linux system.
On Windows the cause is likely different.
Are you using an external file system?
If there's never an actual problem, you can disable the option Config->Switches->Check result of unpacking
Re: Unpacking failed, an expected file was not unpacked
Posted: February 6th, 2015, 4:55 am
by sander
shypike wrote:
We see the error a lot on operating systems which have non-Unicode file systems, mostly Linux system.
On Windows the cause is likely different.
Are you using an external file system?
I think it would be possible and wise to let SABnzbd detect the capabilities of the filesystem and directories it will be writing to (so: temp, incomplete, complete), and so pre-emptively detect write and unicode problems.
Basic example on my Linux:
Code: Select all
$ python
Python 2.7.9 (default, Dec 11 2014, 17:21:00)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> filename = unicode ("مرحبا بالعالم","utf-8")
>>> file = open(filename, 'w+')
>>> file.write("你好世界\n")
>>> file.close()
>>>
$ ll
-rw-rw-r-- 1 sander sander 13 feb 6 10:50 مرحبا بالعالم
$ cat مرحبا بالعالم
你好世界
I don't expect problems with local disks with Linux filesystems (ext*, btrfs). I think problems can occur with non-Linux filesystems (FAT) and network drives (Samba). That must be the same with Windows.
Re: Unpacking failed, an expected file was not unpacked
Posted: February 10th, 2015, 12:56 am
by dvdwsn
shypike wrote:Are all reported files actually present?
We see the error a lot on operating systems which have non-Unicode file systems, mostly Linux system.
On Windows the cause is likely different.
Are you using an external file system?
If there's never an actual problem, you can disable the option Config->Switches->Check result of unpacking
They aren't being extracted. I see an empty folder in my Sonarr's Drone Factory folder but the rar files are all in my Sabnzbd temp folder. I'm able to use 7zip to extract the files without issue.
Although for some of the folders in the temp directory, all that's inside is a _ADMIN_ folder, and nothing else.
I'm running Windows Server 2012 R2
I'm using ReFS which is the new Windows file system.
I'm also running FlexRAID.
Any ideas why the files aren't being disconnected.
Re: Unpacking failed, an expected file was not unpacked
Posted: February 10th, 2015, 4:11 pm
by shypike
Have you tried manually extracting the files with unrar?
"c:\program files (x86)\SAbnzbd\win\unrar\unrar.exe" x PATH_TO_RAR
Re: Unpacking failed, an expected file was not unpacked
Posted: February 11th, 2015, 5:42 pm
by dvdwsn
So, I deleted all the files and folders in the SABnzbd "temp" folder to clean it up and start from scratch.
When I look in there now, I see 4 new folders for episodes Sonarr and SAB tried to download, but there are no rar files inside. Just the _ADMIN_ folder.
Also I just noticed, I had a few other episodes queued, SAB downloaded them and then the disappeared. They aren't listed in the history, the temp folder, the Drone Factory folder, or anywhere I can see... That's odd, right?
Re: Unpacking failed, an expected file was not unpacked
Posted: February 12th, 2015, 3:24 am
by shypike
That's odd, but also hard to diagnose after the fact.
You don't have "cleanup failed jobs" in the Scheduler?
Re: Unpacking failed, an expected file was not unpacked
Posted: February 13th, 2015, 6:48 pm
by dvdwsn
The only thing I have in scheduler are 2 speed limit items.
Re: Unpacking failed, an expected file was not unpacked
Posted: February 13th, 2015, 7:01 pm
by dvdwsn
Just watched a transfer complete.
It was moved down to history, where SAB started to try a repair, got to "verify 1/91", after a few moments it stopped that and had a link to "retry". Now it's back up in the queue.
So this time it didn't just disappear totally. But as all the other times, it will retry, and fail again.
Any ideas?
Re: Unpacking failed, an expected file was not unpacked
Posted: February 14th, 2015, 1:27 pm
by shypike
No idea just yet.
However, should a job disappear: go to the Status page, tab Queue Repair.
There you'll find the lost job.
Re: Unpacking failed, an expected file was not unpacked
Posted: February 16th, 2015, 10:37 pm
by dvdwsn
On the Queue Repair tab I only see two buttons.
Should I press the "Repair" button?
Re: Unpacking failed, an expected file was not unpacked
Posted: February 18th, 2015, 5:47 am
by shypike
You should see a list of "orphaned" jobs, which can be sent back to the queue.
If the list is empty, it's likely that nothing can be recovered.
Double-check by looking at the content of the "temporary download folder".
Re: Unpacking failed, an expected file was not unpacked
Posted: February 18th, 2015, 11:34 am
by dvdwsn
Yeah I'm not seeing any list.
http://i.imgur.com/KuE7RUC.png
The temp folder is empty.
Re: Unpacking failed, an expected file was not unpacked
Posted: February 18th, 2015, 5:05 pm
by shypike
I can offer you the standard advise.
Set logging level to Debug on the Status page.
If it happens again, collect the log file from the Status page
and email it along with the NZB to
[email protected] (and also add the URL of this message).
