Can confirm. I took the original bulk of files I was attempting to hardlink, move, or copy, and nothing seems to budge them. I pointed them towards the test destination folder, nothing. They still fail "due to I/O error"...

Okay, actually one adjustment. It worked with a few of those files in the test folder. Then I attempted to hardlink in the main folders, and it's no longer working. Not sure why...

Hi Rednoah, Thanks for the response! Per your suggestion, I did some tests. I culled it down to two files to make it clear. Here's my results: Using Node, Copy works. It places them into TV Shows > [Show Title] > [Season] and grabs all the correct extra data Plex loves (posters, logos, .nfo files ...

Hi there, Title pretty much captures it. I installed FileBot, have the permissions set to read/write for the system internal user, but when I run the app I get filebot -script 'fn:amc' '/volume1/homes/IamJacksHandle/Server Ops/TransmissionToFilebot/Completed' --output /volume1/homes/plex --action ...

nevermind, I figured it out! The volume wanted to see "/volume1", THEN the rest of the directory! It didn't exist because when I open File Station, it's looking at Volume1 already. Awesome, thanks for the help!

so if it's not an issue with the permissions, what do you think is the likely issue? It still doesn't see a folder for Filebot/In, even though I've given it access to a new folder created especially for the job? What is with this Illegal argument? Is the way that I've notated directory wrong? Is ...

The homes/plex/TV Shows folder does exist, it's where my plex shows go. To try what you're suggested, I created a new shared folder, put both the in and out folders in there, gave it read/write access to every user (including guest), and it's still not running. So I'm thinking that I'm probably not ...

Hi there, I'm having some trouble with FileBot on my Synology. I'm using FileBot Node, and it can't seem to run any files. I don't know too much about coding, but from the error below it seem like there might be some issues: 1. FileBot might not be able to find the directory paths (though I just ...