Increasing number of errors keep file from being completed after download + can't add similiar files

[classicpix]

Twice in the last three days, I've had a rash of errors thrown one after another keeping files, having just been downloaded, from being completed. Most, if not all, have looked like the following.

Code: Select all

Failed making (location of file in incomplete folder)
Traceback (most recent call last):   File "sabnzbd/filesystem .py", line 763, in create_all_dirs
OSError: [Errno 22] Invalid argument: 'same location of file in incomplete folder'

Once the first error happens, then all consecutive files have the same problem.

Sab Version 4.4.1
Mac OS 15.3.2

Incomplete and Complete Folders are on an external HDD. Sab has the correct permissions as it's been working flawlessly for months. Though in the past two-ish weeks, I moved my HDDs to a USB enclosure. So perhaps the drives are spun down when the file download and thus causing a permission error? Though I have a hard time believing that given this computer runs 24-7 downloading files from Sab. Plus, the errors continue to happen even after I know the HDDs are spun up. That said, these issues do seem to align, somewhat at least, with the move to the HDD enclosure. (Note the HDDs itself were connected individually to Sab prior to the move and had no issues.)

Space on the HDD shouldn't be an issue. Sab's reporting over 3TB free (there's more available but Mac OS reports a reduced amount to Sab).

I'm hesitant to move to the download folder to my local drive for two reasons. One, there's not a lot of free space. Two, I have a ton of files in the queue so I'm concerned what will happen to them.

At first, I tried restarting Sab. But errors kept being thrown one after the other. The name of the folders and files look kosher, meaning there are no special characters. Though, after this happened the first time, I turned on "Make Windows Compatible" naming switch. (HDDs are ExFAT.) But then the issue happened again a day or so later. So I'm pretty sure the naming is not the issue.

The only thing that seemed to stop the errors from happening and return Sab to normal is a computer restart. After doing so, Sab returned to normal operation. Though the files that had the errors never were completed.

Two other strange things to note:
1. I'm unable to add those exact NZBs back to Sab. Doing so brings up the same error. Perhaps even more strange, I can't add a different NZB of the same file OR of a different version of the same root file (i.e., same basic root file name but with some differences) without getting the same error message. This problem thus seems to make it impossible, currently, to add any version of that file to Sab.
2. There are 3 orphaned jobs in the download folder, none of which I can retry or delete. When I hit the remove button, nothing happens. They remain in orphaned jobs. When I hit the retry button, I get the same error as before and thus remain an orphaned job. (There were far more than 3 that have run into this error.)

I'm hesitant to reinstall Sab, seeing as I have many many files in the queue.

Any thoughts / solutions would be greatly appreciated. Happy to add any additional details if necessary.

[classicpix]

This has happened two more times and is getting very frustrating. Any help please?

[jcfp]

There's isn't much to say about the sabnzbd end with only that very limited piece of logging to go by. But that error comes directly from the OS in response to an attempts to create a directory, and given that your troubles started with moving the hard drives to a usb enclosure, that's where to start. Sabnzbd itself wouldn't be the primary suspect.

Could be many things, including OS power saving bullshit, usb controller chip bugs, hardware issues with the hdd, and so on. Check the OS side (logs, smart info, "eco" settings or power saving of any kind); you could also try to test what happens if you artificially keep the disk awake by creating disk write activity every minute or so, or move the disk back to where it was (for testing purposes anyway).

[cntblazy]

Hi, wanted to flag that I'm having this issue as well. I currently save incomplete files on my local drive, then files are moved to my complete folder on a DAS. The weird thing is that this only happens to select files and not all of my files. I've had several files complete post-processing and import via Radarr while others run into the post-processing issue and are stuck in my queue. Restarting sometimes lets some files complete that were impacted, but then the issue returns one way or another. Permissions are fine as I'm able to create folders in docker terminal, even ones with filepaths that match those that fail in Sabnzbd. At a complete loss with how to progress here.

Sequoia 15.1.1
Sabnzbd 4.5.3 from lscrio-linuxserver
Docker 4.49.0

[cntblazy]

Hi, just wanted to follow up. I was able to find the root cause that was driving the error. My external disk runs on exFAT and I believe some of the folders that sabnzbd was trying to write to were corrupted, hence the OS Error.