Unpacking failed, write error or disk is full

Get help with all aspects of SABnzbd
Forum rules
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.
Post Reply
jacksongls
Newbie
Newbie
Posts: 2
Joined: August 9th, 2019, 2:41 pm

Unpacking failed, write error or disk is full

Post by jacksongls »

Running Sabnzbd version 2.3.9 [03c10dc] on a Raspberry Pi 4 (4GB, Raspbianbuster) along with Sonarr and Radarr. Sab is downloading to a usb thumb drive on the pi, then the files are moved over to a network mounted folder on an external drive plugged into a Nvidia Shield TV.

On far majority of downloads, but not completely all, Sabnzbd loses connection as soon as Unpacking begins. After a couple of minutes, the connection resumes and I get these errors:

“Error: write error (in the file…mnt/shield/etc…)” and the file history says “Unpacking failed, write error or disk is full?”

Disk is not full, I have confirmed.

This seems to mostly happen with TV shows, so I have considered it a Sonarr or a Mono problem. But I am not seeing any errors in Sonarr log. I have also read there are issues with latest Mono 6.0 release and network drives, so I downgraded to Mono 5.20 per others suggestions, but that did not solve the problem, bringing me back to Sabnzbd.

The log shows this: ERROR::[newsunpack:732] ERROR: write error ( in the file /mnt/shield-usb/Downloads/Complete/TV Shows/_UNPACK_Wo…etc)

I also noticed in the log something weird that says: "Inappropriate ioctl for device"

Everything had been working perfectly for the last few weeks since I set this up until the other day, just randomly stopped working. Perhaps the drive plugged into the shield is going bad, but it seems to be functioning just fine so I'm not sure if these errors are related to that, or to Sab, or to Sonarr...etc.
User avatar
safihre
Administrator
Administrator
Posts: 5339
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Unpacking failed, write error or disk is full

Post by safihre »

Do you maybe have another usb to try?
You can switch logging to Debug in the Status window and then after it happens again, inspect the output of Unrar.
The error we give is when unrar throws errors that it can't write files. That can be for a number of reasons, mostly due to permissions or disk being full, so that's what we report as possibilities. But in this case it can be worth to see the exact unrar error.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
jacksongls
Newbie
Newbie
Posts: 2
Joined: August 9th, 2019, 2:41 pm

Re: Unpacking failed, write error or disk is full

Post by jacksongls »

I have had debug switched on and have the log up in front of me. Can you help guide me towards what specifically to look for? I can just copy/paste what looks like relevant Unrar info that surrounds this specific error in the log. But let me know if there's a better way to share info with you (im new so cant post link to pasetbin), or what to look for in the log: well nevermind it's not letting me paste anything. Says I can't post links even though I dont think theres a link in the log file. Can you help?
User avatar
jcfp
Release Testers
Release Testers
Posts: 986
Joined: February 7th, 2008, 12:45 pm

Re: Unpacking failed, write error or disk is full

Post by jcfp »

Just put it on pastebin and mention that in a reply here along with the unique id of the paste.
Oliev
Newbie
Newbie
Posts: 1
Joined: August 21st, 2019, 6:07 am

Re: Unpacking failed, write error or disk is full

Post by Oliev »

jacksongls wrote: August 10th, 2019, 6:47 am Running Sabnzbd version 2.3.9 [03c10dc] on a Raspberry Pi 4 (4GB, Raspbianbuster) along with Sonarr and Radarr. Sab is downloading to a usb thumb drive on the pi, then the files are moved over to a network mounted folder on an external drive plugged into a Nvidia Shield TV.

On far majority of downloads, but not completely all, Sabnzbd Showbox loses connection as soon as Unpacking begins. After a couple of minutes, the connection resumes and I get these errors:

“Error: write error (in the file…mnt/shield/etc…)” and the file history says “Unpacking failed, write error or disk is full?”

Disk is not full, I have confirmed.

This seems to mostly happen with TV shows, so I have considered it a Sonarr or a Mono problem. But I am not seeing any errors in Sonarr log. I have also read there are issues with latest Mono 6.0 release and network drives, so I downgraded to Mono 5.20 per others suggestions, but that did not solve the problem, bringing me back to Sabnzbd.

The log shows this: ERROR::[newsunpack:732] ERROR: write error ( in the file /mnt/shield-usb/Downloads/Complete/TV Shows/_UNPACK_Wo…etc)

I also noticed in the log something weird that says: "Inappropriate ioctl for device"

Everything had been working perfectly for the last few weeks since I set this up until the other day, just randomly stopped working. Perhaps the drive plugged into the shield is going bad, but it seems to be functioning just fine so I'm not sure if these errors are related to that, or to Sab, or to Sonarr...etc.
Did you solve this problem? I have the same and need help
DESMOND6670
Newbie
Newbie
Posts: 1
Joined: October 5th, 2019, 11:32 pm

Re: Unpacking failed, write error or disk is full

Post by DESMOND6670 »

even my unpacked failed
faysalbing
Newbie
Newbie
Posts: 1
Joined: December 26th, 2019, 11:13 am
Location: Karachi, Pakistan
Contact:

Re: Unpacking failed, write error or disk is full

Post by faysalbing »

Same for me! It's not even unpacking anymore. Guys, if you found a solution then please let me know! I need it so bad.

Regards,
Regards, Faysal
User avatar
safihre
Administrator
Administrator
Posts: 5339
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Unpacking failed, write error or disk is full

Post by safihre »

Well, maybe post some more logs?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
sammyjason12
Newbie
Newbie
Posts: 1
Joined: February 12th, 2020, 3:06 am

Re: Unpacking failed, write error or disk is full

Post by sammyjason12 »

jacksongls wrote: August 10th, 2019, 6:47 am Running Sabnzbd version 2.3.9 [03c10dc] on a Raspberry Pi 4 (4GB, Raspbianbuster) along with Sonarr and Radarr. Sab is downloading to a usb thumb drive on the pi, then the files are moved over to a network mounted folder on an external drive plugged into a Nvidia Shield TV.

On far majority of downloads, but not completely all, Sabnzbd loses connection as soon as Unpacking begins. After a couple of minutes, the connection resumes and I get these errors:

“Error: write error (in the file…mnt/shield/etc…)” and the file history says “Unpacking failed, write error or disk is full?”

Disk is not full, I have confirmed.

This seems to mostly happen with TV shows, so I have considered it a Sonarr or a Mono problem. But I am not seeing any errors in Sonarr log. I have also read there are issues with latest Mono 6.0 release and network drives, so I downgraded to Mono 5.20 per others suggestions, but that did not solve the problem, bringing me back to Sabnzbd.

The log shows this: ERROR::[newsunpack:732] ERROR: write error ( in the file /mnt/shield-usb/Downloads/Complete/TV Shows/_UNPACK_Wo…etc)

I also noticed in the log something weird that says: "Inappropriate ioctl for device"

Everything had been working perfectly for the last few weeks since I set this up until the other day, just randomly stopped working. Perhaps the drive plugged into the shield is going bad, but it seems to be functioning just fine so I'm not sure if these errors are related to that, or to Sab, or to Sonarr...etc.

If you fixed the error, please update the solution, it will help us lot. Thanks.
Post Reply