Almo96

I will unless unRAID support can help me within the weekend. Hopefully I'll get to restore Sonarr and Radar configurations without having to redo all that, without creating other issues with permissions or something. The rest shouldn't take too long to do, given that I know how to do it now. Edit: I misunderstood your comment. Due to new errors having shown up, I meant that I will reinstall unRAID if unRAID support doesn't help me by the weekend. See the edit in my previous comment.

This did not work. Everything else works, binhex-qbittorrentvpn won't even install or show up under "docker", despite working perfectly a few days ago. If binhex ever reads this, can you help, or do I have to reinstall unRAID and redo everything in the hopes of that fixing it? I'd rather not redo everything. Edit: I was a bit quick on the draw. It seemed like everything* was working, but after moving the shares I'm getting the same or a very similar issue on all the docker containers. I have opened a ticket with unRAID support, and I hope they will assist. Worst case scenario I'll have to reinstall unraid and redo all or at least most configuration.

I'm having zero other issues with that pool. Everything else seems to work as it should. Not that I have gotten to the testing phase of my arr-stack yet, but I've followed the trash guides with zero issues so far. Web UI for docker apps works fine, except for binhex-qbittorrentvpn. I'll try moving everything off the pool and re-creating it tomorrow. I don't want to nuke everything and have to deal with backups yet, and I'm not redoing all the profiles or whatever in sonarr and radarr. Hopefully just moving the shares won't break anything else.

Brand new user to unraid here. Trying to set up my first unraid home server. Having some issues, and I'm sure there will be more, so I'm going to be asking for some help from the kind people here willing to lend a hand. - My qbittorrent wouldn't start after working perfectly yesterday, so I restarted my machine, but it still wouldn't work. Then I checked the logs and found this: docker: Error response from daemon: exit status 2: "/sbin/zfs snapshot vms-appdata/87eb9f3b109c8cf3ad5f1064cb2275a67335cb50b2e94dec283cb9a00dcc8ec9@685562554" => cannot open 'vms-appdata/87eb9f3b109c8cf3ad5f1064cb2275a67335cb50b2e94dec283cb9a00dcc8ec9': dataset does not exist "vms-appdata" is the pool on which "appdata" and "system" is located. - Then I activated debugging on the docker image, but it failed with this error: Error response from daemon: No such container: binhex-qbittorrentvpn The docker container was then gone, and can't be reinstalled due to the first error. - When the system and appdata shares were originally created, it was automatically created on pool "main-storage". I quickly moved them to "vms-appdata", but a single "system"-folder remained on "main-storage", and I can't delete it from the file manager. I don't know if this is related to this other issue. As long as this isn't causing problems, my OCD ass can live with it. - I don't know what has gone wrong, nor how to further troubleshoot this. I don't know what commands to give docker permission to read and write to "vms-appdata". If anyone has any guides I should read, I'm more than willing to do so. If anyone has any tips or ideas, I welcome it. I would prefer not to have to delete my "vms-appdata" pool, reconfigure it, and then restore from backups (I don't even know how to restore appdata backups yet, especially when it comes to likely having to use commands to set correct permissions, but I do already have appdata backups). - edit: Seems I might have slightly misunderstood the nature of the error. It might have access to vms-appdata to some extent, but it doesn't seem like this specific docker container gets access to at least read there there, unless I'm misunderstanding something. Other docker containers still seem to work. - edit 2: Everything in the "binhexqbittorrentvpn"-folder under "appdata" was gone. I deleted the folder too since I was going to try to delete everything and see if that made it possible to reinstall. Still impossible to reinstall. This comment was originally published to the unraid subreddit on reddit.com