SABnzbd Forums

For the last few weeks I have been getting "Unpacking failed, write error or disk is full? " when downloading large files (8GB+)

When I Google this error I come up with a bunch of results but none of them really provide a solution; mostly people that legit ran out of space.

My Setup:
Version: 0.7.17Beta3
I run Sabnzbd on a Ubuntu server which has NAS storage (QNAP).
Sabnzbd's incomplete folder and complete folders exist on the NAS.

First off, there is plenty of space on the NAS.
I can manually run unrar on the server and extract the contents of the package.
Sabnzbd does create an "_UNPACK" directory in the complete location and does write other files there normally.

I also want to add that after a failure I can re-initiate the unpack phase by adding the NZB back into SAB and copying the downloaded files back into the new directory it creates. Sabnzbd will see that it has all the files it needs, go through the verify and unpack just fine.

Being that all of these things are true, can anyone help me to determine why I'm randomly getting this error?

The error from the log files is this:
ERROR: ERROR:: write error ( in the file /complete/_UNPACK_this_is_a_file/this_is_a_file.mkv [R]etry, [A]bort)

The only thing I can think of is maybe couchpotato is getting to the mkv file BEFORE it's completely unpacked? Is that possible?

A search from the couchpotato logs tells me that it is skipping "_unpack" directories.

DEBUG[tato.core.plugins.scanner] Ignored "/complete/_UNPACK_this_is_a_file/this_is_a_file.mkv" contains "_unpack".

Further to this point, during a sab "Unpack" I ran a couchpotato rename scan and it did not cause the unpack to fail.

Still at a loss.

CP is supposed to skip _unpack_ folders, because it means that the content is still incomplete.
It depends very much on what kind of errors the OS returns.
There are generally two possibilities.
1. The OS reported back some error when writing files. Out of scope for SABnzbd
2. After the unpack, SABnzbd cannot find all of the files that are supposed to have been unpacked.
The latter can fail on some platform, that's why we have the option Config->Switches->"Check result of unpacking".

I enabled "check result of unpacking"; I'll see if I get a different result.

My suggestion was that you disable it.
Even so, "write error or disk is full" cannot be caused by the unpack check.
It's the result of an error message coming from the OS.
What can do is enable "debug" logging and check the log file (Status page) after this problem occurs.
Possibly SABnzbd logs the actual error message coming from the OS.

I'm still receiving this error.

sabnzbd runs on an Ubuntu server and saves via an NFS share to my QNAP NAS.
The unpack is essentially occurring over the network. Since I can log into the QNAP and manually unrar and copy the files without incident I'm wondering if the network is causing the write error to occur.

I'm just not sure how to test that... any suggestions?

What happens if you run unrar manually from the local drive to the network drive?
(That's the way SABnzbd lets unrar do it.)

shypike wrote:What happens if you run unrar manually from the local drive to the network drive?
(That's the way SABnzbd lets unrar do it.)

This was going to be my next thing to do. Basically have Sab download locally and then unrar accross the network to the NAS. My only issue here is the server has limited space so if that's the solution then I'm into $$$ for upgrades. But such is life right?

I'll see if I can get that change done this weekend.

Thanks for your help as always!

** EDIT **

A representative from Qnap suggested I ditch NFS mounts for Samba. So I have remapped everything using Samba and am going to run like that for a bit to see if it makes a difference.

shypike wrote:What happens if you run unrar manually from the local drive to the network drive?
(That's the way SABnzbd lets unrar do it.)

As a follow-up i would like to say that after switching my mappings to Samba I have not had any more write errors.
At the moment I'm willing to take this as fixed.

Thanks for your assistance!

I have this error too. I have the incomplete file set in the normal location but the complete file is on a 3tb drive that is also in the pc. i have changed it back so the complete file is on the OS hdd with the incomplete file and the error has gone. it only happens about 50% of the time but it s annoying. i can also unpack the file in its incomplete location using 7zip and the files extract fine. is there a way to set sab to unpack in the incomplete file location and then move the unpacked file.

whatwentwrong81 wrote:is there a way to set sab to unpack in the incomplete file location and then move the unpacked file.

There is, if you're willing to write your own user script.

The basic problem is an unreliable connection to a mounted drive.
There's nothing I can do to solve the underlying issue.
I do know that some versions of unrar have more problems than others with mounted drives.
It likely just exposes the underlying OS issue more, rather that having an actual bug.
Have you examined upgrading unrar?

Hi All,

I'm experiencing the same issue as jeffwscott as I see the same error in SABNZBD.

This stood out from the logs of SABNZBD:

2015-01-22 21:55:44,563::INFO::[newsunpack:428] Extracting rarfile /home/admin/Downloads/incomplete/Veronisoft.Get.IP.and.Host.v1.5.7.Portable-BEAN.1/6c7dbbb75f655ccc35e04c3c182fe18c75173eca.rar (belonging to 6c7dbbb75f655ccc35e04c3c182fe18c75173eca) to /nas/movies/_UNPACK_Veronisoft.Get.IP.and.Host.v1.5.7.Portable-BEAN
2015-01-22 21:55:44,570::ERROR::[newsunpack:639] ERROR: write error ( /nas/movies/_UNPACK_Veronisoft.Get.IP.and.Host.v1.5.7.Portable-BEAN/buv0lu01.zip)

I've tried shypike suggestion in extracting from the Ubuntu server to the NAS, but no luck. Throws me this error:

tar: /nas/movies: Not found in archive
tar: Exiting with failure status due to previous errors

This leads me to believe it's some permissions related issue? I could be totally off..

I currently have a mount set as the following in /etc/fstab (10.x.x.x is of course masked):

//10.x.x.x/.movies /nas/movies cifs credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0

I can extract locally fine.. If I set the completed folders to somewhere on the Ubuntu server, it extracts perfectly..

I'm not a Linux expert. May someone please point me in the right direction?

Thank you.



I

I dug a bit deeper and I have more reasons to believe it's related to permissions...

admin@jumpbox:/nas/movies$ touch testing.txt
touch: cannot touch `testing.txt': Permission denied
admin@jumpbox:/nas/movies$ mkdir testing
admin@jumpbox:/nas/movies$ ls -lsh | grep testing
0 drwxrwxrwx 2 1024 users 0 Jan 23 10:50 testing
0 -rw-rw-r-- 1 1024 users 0 Jan 23 10:50 testing.txt

But why is it that I'm able to create a directory but not "touch" successfully?

Hi All,

As soon as I switched the user to root for SABNZBD, it works fine...

Thanks!