evlcookie

In terms of updating the software (as somewhat discussed in the other thread), I imagine we need to update the images which then creates a container with the updated files. How does the config files and everything else get transferred during that process? Is it possible for end users to create a local repo, update it with the latest files, docker build ABC and start that? Or does it need to be done all from an online repo such as yours needo?

How do we go about adding files to inside a container? For example, nzbget, It would be nice to add some post processing scripts but i'm not too sure what the best way to go about it is.

Getting this in the logs with nzbget nzbget.conf(49): Invalid value for option "InterDir" (/nonexistent/downloads/inter/): could not create directory : nzbget.conf(70): Invalid value for option "TempDir" (/nonexistent/downloads/tmp/): could not create directory : nzbget.conf(67): Invalid value for option "QueueDir" (/nonexistent/downloads/queue/): could not create directory : nzbget.conf(61): Invalid value for option "NzbDir" (/nonexistent/downloads/nzb/): could not create directory : I've probably done something wrong but i'm having trouble seeing what.

I'm currently getting /nonexistant/xyz for nzbget directories, It's probably something i'm doing wrong. Also having issues with nzbdrone actually seeing my TV folder so I can import all my files. Again, Probably just me - Fixed!

Is there an issue with the permission script not actually working? When I do a chmod on any of my older files, There's nothing ticked or selected (while using MC) for any of the attributes. Which makes it hard to playback files unless i log in as root. Anything newer that's been created by sickbeard/sab works fine.

Well I have no idea what on earth is going on. For some reason, All of my original sab and sickbeard files have just randomly popped up again on my shared drive under SNAP. I deleted the shared name folder via MC and rebooted. It almost looked like a newer "Applications" folder was created on top of the old one. When i deleted the "Applications" folder the old one reappeared. That just makes no sense to me at all. I was originally using the plugin before my files mysteriously vanished and then i switched over to unmenu to see if there was an issue with the plugins. Unmenu packages still seem to overwrite the original folder even when placed outside the shared name and just being directly on the disk itself on /mnt/disk (that is still being mounted by SNAP). Although by the feel of it and with my files popping back up from the dead, It's probably not an unmenu package installation error, my unraid just seems to be full of ghosts. Ok, I've now installed both sickbeard and sabnzbd via unmenu package and pointed them to my existing installation folders. So far everything seems to be working. I will let sab grab some files just to make sure and then shutdown to see if it's still happy. I am totally at a loss for words, I have no idea what on earth just happened. Thanks for the reply though

Any idea as to why folders within the drive and the share name are deleted upon reboot or shutdown? I'm trying to store sickbeard and sab on a SNAP drive, Yet everytime I reboot it seems to simply delete the folders and files which then gives me a fresh install of every app/plugin I had installed on the drive. Edit: Ok Now this is just strange. I decided to right click on the shared name and delete it, Which didn't seem to do anything. I actually then went and deleted it from the drive itself within MC. I've rebooted to see what would happen and now all my original old file have magically returned. What the hell just happened?

Is there any reason why the plugins or even packages need to be reinstalled upon a restart? It seems to wipe everything clean here which is beyond frustrating. Even when it's not enabled for reinstall on reboot, the folders and files are still removed upon a shutdown. Is there anything I can do to stop this happening? I have an SSD that is mounted via SNAP which is used for my applications. There doesn't seem to be any issue with actually mounting the drive as SAB's wizard loads up without any issues. Everything was going great until the power went out last night, Now i've lost everything for sick and sab

Unraid is 5.0b14. Apps are installed via plugins (along with SNAP) and the data folders are just pointed towards the drive. The drive appears under /mnt/disk/<pluginfoldernamehere>. Sickbeard and sab are being run as root. I'm sure it's just me doing something incorrect or the drive died on me. It is one of my old SSDs, I'm sure it was fine when I stopped using it but who knows. Maybe lack of use for 6 months or so has just degraded it a little too much. I will run some smart tests etc once I get home. Thanks for the replies so far

The drive is essentially a unraid apps drive. Sick, sab etc all have their files stored on it and both were giving me errors since they can't write to a read only file. I don't believe any of it was shared across the network since none of it really needs to be accessed. My windows machine was off overnight and I did mount the TV user share from unraid, So maybe windows has done some voodoo magic and messed with the SNAP share when it shouldn't have. It's not a major issue, Annoying for sure but there's bound to be a solution out there. It could just be a hardware fault, drive has come loose etc. I will have to check it all tonight once I get home, Lots of trial and error stuff to check and test.

The drive that I'm currently sharing with SNAP has been working fine over the past 24 hours. However this morning I woke up to find that it has now entered a read only file system state. Unmenu seems to suggest it's mounted with read and write priv from when i first set it up. Any idea why it's done this? Or is it going to be an actual hardware issue?