SABnzbd Forums

Hey all,

I recently changed my storage from HW raid on a Windows machine to FreeNAS, but kept Sab on my Windows VM. I'm connecting to it the share via CIFS.

I'm getting a few different errors that cause the queue to pause and am met with a variety of outcomes. Sometimes the download fails to repair and other times it fails to unpack.

2016-07-19 18:55:43,914 ERROR: Disk error on creating file Z:\dl\temp\xxxxxx.xxxxxxx.xxxxx.xxxxxx.xxxxx.xx.xxxxxx.xxx.x.xxxx\xxxxxx.xxxxxxx.xxxxx.xxxxxx.xxx.xxxx.xxxx.xxxxx.xx.xxxxxx.xxx.x.xxxx-xxx.part049.rar
2016-07-19 18:55:43,306 ERROR: ERROR:: write error ( in the file Z:\dl\tv\_MHKH6~G/WgVQ1vB91BqkkKFtNsln9wxhlo3ZRj7.mkv [R]etry, [A]bort)
2016-07-19 18:54:44,782 ERROR: Loading \\?\Z:\dl\temp\xxxxxx.xxxxxxx.xxxxx.xxxxxx.xxxxx.xx.xxxxxx.xxx.x.xxxx\__ADMIN__\SABnzbd_article_gkhltx failed
2016-07-19 18:51:03,812 ERROR: Saving \\?\Z:\dl\temp\xxxxxx.xxxxxxx.xxxxx.xxxxxx.xxxxx.xx.xxxxxx.xxx.x.xxxx\__ADMIN__\SABnzbd_nzo_5uuuce failed
2016-07-19 18:50:30,582 ERROR: Saving \\?\Z:\dl\temp\xxxxxx.xxxxxxx.xxxxx.xxxxxx.xxxxx.xx.xxxxxx.xxx.x.xxxx\__ADMIN__\SABnzbd_nzo_5uuuce failed
2016-07-19 18:49:18,265 ERROR: Loading \\?\Z:\dl\temp\xxxxxx.xxxxxxx.xxxxx.xxxxxx.xxxxx.xx.xxxxxx.xxx.x.xxxx\__ADMIN__\SABnzbd_article_szbxny failed

I set par2 to always download and reduced the max folder size to 64 from 128 to no avail. I tried switching over to an NFS share, but a lot of permission issues cropped up and I couldn't figure them out.

I also ticked Make Windows Compatible. Not sure if that is required or not.

Any help would be greatly appreciated!

SABnzbd doesn't know about file systems.
It just tells the operating system what it wants to do to a file.
This problem is completely outside of SABnzbd.
Try some intense copy actions to the NAS, copy a couple of Gigabytes to it
with some other software.

Could it be a permissions thing?

I moved all the downloading/unpacking to the local drive where SAB is installed and then use Sonarr to move the files to the NAS and that fixed every issue I was having. Downloads that were failing before worked without issue.

asciutto wrote:Could it be a permissions thing?

That's always a likely cause.

Actually, I'm seeing these errors quite regularly now since upgrading SAB to 1.0.3. I never saw them until I upgraded. It's been working flawlessly on the same hardware for over a year (only thing thats changed is software version). Unless my 'Temp' drive is starting to fail (no other problems with other data), its definetly a bug in 1.0.3. I'm going to try downgrading to 1.0.2 to see if the errors stop. One thing I noticed is that this particular download was fine (4gigs downloaded out of 6gigs), but then these errors showed up after I added a new NZB to the queue.

2016-07-22 19:34:16,867 ERROR: Disk error on creating file D:\Temp\some.file.rar
2016-07-22 19:34:16,861 ERROR: Saving \\?\D:\Temp\some.file.rar\__ADMIN__\SABnzbd_nzo_lnnwdr failed
2016-07-22 19:32:15,414 ERROR: Saving \\?\D:\Temp\some.file.rar\__ADMIN__\SABnzbd_nzo_lnnwdr failed
2016-07-22 19:27:53,141 ERROR: Disk error on creating file D:\Temp\some.file.rar
2016-07-22 19:27:53,138 ERROR: Saving \\?\D:\Temp\some.file.rar

Just a note, this error has stopped coming up since downgrading to 1.0.3.

I suspect this is a bug that was introduced in 1.0.3, as I've never seen it before 1.0.3, and it doesnt appear after downgrading to 1.0.2.

Although I believe you that it doesn't happen in 1.0.2 VS 1.0.3, there were no changes in the code between those versions involving anything with files
So maybe it was something to do with the packaging?

Would you be willing to try 1.1.0RC2? It's in a very mature state, shouldn't contain any bugs really. Wondering if it happens there too!
https://sabnzbd.org/downloads

I've just started seeing these after updating to 1.1.0, never seen it before.

As other posts, this happens on particular NZB only, if I shift the troublesome NZB down the queue, other NZB get saved no problem so not a permission or other disk error in my opinion.

I'm not the most technical person so don't know how much I can do to help, but just wanted to let you know I'm now seeing this for the first time ever.