Hello friends,
I'm having a bit of an issue here. I'm running SABnzbd 3.4.2 (linuxserver docker) on my Synology NAS on DSM 7.
I have my incomplete, complete and watched folders on an external USB drive (Samsung T7 Portable SSD) connected to the NAS.
Now sometimes when I download files through Sonarr/Radarr, one file loads to 99% then SABnzbd pauses and gives me this error for the next file in qeue:
Disk error on creating file /incomplete-downloads/Series.S01E05.mp4
I don't know how to paste the log. it tells me "new users aren't allowed to post links". log says something about: OSError: [Errno 22] Invalid argument
Hope you guys can help. thx.
Disk error on creating file
Forum rules
Help us help you:
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.
Re: Disk error on creating file
That is what the NAS' operating system is telling to SABnzbd. SABnzbd cannot do anything about that.
As a workaround: Let SAB point incomple to an internal disk.
Oh, wait: the USB disk is not full, I hope?
As a workaround: Let SAB point incomple to an internal disk.
Oh, wait: the USB disk is not full, I hope?
Re: Disk error on creating file
Thx for your reply!
No, the USB drive is not full, there is still plenty of free space.
So it's not possible to have the incomplete folder on an external disk, without having this error?
When I resume the download it downloads without problems.
Here is the log from SABnzbd:
https : // pastebin . com / 74Pj5P7H
maybe there's some more information that helps in there.
No, the USB drive is not full, there is still plenty of free space.
So it's not possible to have the incomplete folder on an external disk, without having this error?
When I resume the download it downloads without problems.
Here is the log from SABnzbd:
https : // pastebin . com / 74Pj5P7H
maybe there's some more information that helps in there.
Re: Disk error on creating file
It is possible, but an external disk has a higher chance of causing a problem.So it's not possible to have the incomplete folder on an external disk, without having this error?
https://pastebin.com/74Pj5P7H ... that shows quite a different problem:
Code: Select all
OSError: [Errno 22] Invalid argument: '/incomplete-downloads/Series.Name.S03E07.1080p.BluRay.x265.mp4-xpost/[N3wZ] \\OF6UE8257053\\::[PRiVATE]-[WtFnZb]-[newz[NZB].nfo]-[2+2] - "" yEnc 13 (1+1)'Worth trying: SABnzbd: Config -> Switches -> "Make Windows compatible"
Re: Disk error on creating file
The disk is indeed formatted as EXFAT.
Maybe i should try to reformat it as EXT4. Do you think that would solve the issue with the forbidden characters?
Maybe i should try to reformat it as EXT4. Do you think that would solve the issue with the forbidden characters?
Re: Disk error on creating file
No, no format: first try the SAB option I gave you.
And, I'm not 100% sure about what that webpage says about illegals chars on exFAT: on my external USB drive (which I think is exFAT), I can create weird characters:
Oh, can you try that touch command against your external disk? As you say "ext4", I'm assuming you run linux & know how to run that touch command
And, I'm not 100% sure about what that webpage says about illegals chars on exFAT: on my external USB drive (which I think is exFAT), I can create weird characters:
Code: Select all
sander@brixit:/media/zeegat$ touch 'bla bla :: \\ * "this" and that.txt'
sander@brixit:/media/zeegat$ ll bla\ bla\ \:\:\ \\\\\ \*\ \"this\"\ and\ that.txt
-rwxrwxrwx 1 root root 0 jan 31 20:33 'bla bla :: \\ * "this" and that.txt'*Re: Disk error on creating file
I'm running SAB as a docker container in Synology DSM 7, so i don't really know how to run that command.
I'll try the setting "Make Windows compatible" and see if that solves it.
I'll report back, if i still encounter the error.
Thx for your help.
I'll try the setting "Make Windows compatible" and see if that solves it.
I'll report back, if i still encounter the error.
Thx for your help.
Re: Disk error on creating file
For the record: a VFAT disk indeed has problems with special characters
The illegal chars:
From python:
Code: Select all
sander@stream13:/media/sander/LINUX MINT$ mount | grep MINT
/dev/sda1 on /media/sander/LINUX MINT type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
sander@stream13:/media/sander/LINUX MINT$ touch 'ddd bla bla.txt'
sander@stream13:/media/sander/LINUX MINT$
sander@stream13:/media/sander/LINUX MINT$ ll ddd\ bla\ bla.txt
-rw-r--r-- 1 sander sander 0 Jan 31 20:56 'ddd bla bla.txt'
Code: Select all
sander@stream13:/media/sander/LINUX MINT$ touch 'ddd "bla" bla.txt'
touch: setting times of 'ddd "bla" bla.txt': No such file or directory
sander@stream13:/media/sander/LINUX MINT$ touch 'ddd bla *** bla.txt'
touch: setting times of 'ddd bla *** bla.txt': No such file or directory
sander@stream13:/media/sander/LINUX MINT$ touch 'ddd bla \\ bla.txt'
touch: setting times of 'ddd bla \\ bla.txt': No such file or directoryCode: Select all
>>> os.open('bla * bla.txt', os.O_CREAT)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OSError: [Errno 22] Invalid argument: 'bla * bla.txt'Re: Disk error on creating file
So it seems the "Make Windows compatible" setting did the trick.
I downloaded the same files from before, without any errors.
I'll leave the disk as exFAT for now, since it's working. If I encounter the error again, I will try another file system.
Big thx for the awesome help!
I downloaded the same files from before, without any errors.
I'll leave the disk as exFAT for now, since it's working. If I encounter the error again, I will try another file system.
Big thx for the awesome help!
