SABnzbd Forums

New folders (generated by SABNZB+, that runs in the background as a web service) will only show up in Finder once I have run a search in Finder and are not visible before. I have tried a disk repair and a permissions rebuild.

I am starting to believe it might have to do with the fact that the folders are created by the unarchiver that reassembles files after they are downloaded from my newsgroup. The strange thing is that there never used to be a problem, it started somewhere around the second update to mountain lion. But it could also be a new version of the application SABNzb+, I am not sure.

What is also weird is this: I can find the folder when doing a search in Finder, then open the folder, all files are there and the folder is then visible normally.

Note: The files are reassembled by the unarchiver on the main Macintosh HD, then moved to a different volume as final destination and deleted from the originating volume, i.e. my /complete folder is on a different volume than the OS

Any ideas anyone?

Hard to tell.
What happens when you create a new folder on the other volume, using the Terminal window?
Does Finder pick it up immediately?

I am having a similar problem. I have sabnzbd set to output all files to the same folder. Occasionally a bunch of downloads will complete successfully, but when I look at the output folder it is empty. If I then do a spotlight search, the files are found. I choose show all in Finder, and when I click on one of the files, it suddenly appears in the folder where it should have been originally. The files are all there, they are just not visible in Finder. I have also been able to find missing files by re-indexing the folder or the drive. Is this a Mac problem, or an sabnzbd problem?

I had similar problem when I first switched to linux.

My problem was that final folder was caled /download/Complete in sabnzb and it was in fact /download/complete,
when i renamed folder in sabnzb problem dispirited.

Linux (normally) has a case-sensitive file system, so "complete" and "Complete" are two
very different folders.
OSX shows case-differences, but is in fact case-insensitive.
That means that "complete" and "Complete" are the same folder.
It could be that OSX makes some trouble when you access "complete" as "Complete" or vice versa.
I'm not sure, but it's about the only "explanation" I can give.
Other than that, SABnzbd just creates files and folders like it should, the rest is up to the Finder.