hello all maybe some one can help I installed emby through portainer , no errors states running, when I try to log into my emby server using my IP address :8096 I get message on multiple browser site can not be reached
please help
emby site can not be reached
-
- OMV 5.x
- boris431
-
It just isn't possible to help when the only information provided is that it doesn't work.
You need to provide the docker configuration you entered into Portainer.
-
here is the log time
In portainer when you select the log option there is a 'button' -> copy that will copy the contents to the clipboard, in the reply on the menu there is an option -> Spoiler open that and paste the contents from the clipboard.
But this -> System.IO.IOException: System.IO.IOException: No such device appears to be the problem.
What did you follow to install Emby was it this I have Emby running on OMV4
-
Any idea how to fix problem
You can't the only way top do this is to stop the container and delete it and start again.
had to reflash omg
You had to reinstall? Why?
-
I just put it together and the raid 5 i was running was not working correct so i decided to start from zero , nice I only put this system together this week there was nothing on it
So i stopped emby and erased it from portainer
and them reinstalled the container and have the say result
attached are screen shots of the information I added
also I switched to union file system probably does not affect this but putting it out there that is the only difference I can see between this and the old system
please advise on what you would do -
also I switched to union file system probably does not affect this
Yes it does, tried and tested, the config that's /config cannot be put on the fuse mount point it simply will not work!!
I have OMV5 both in a VM and on laptop as a test, the VM is configured with a raid5 purely for testing purposes, so on that VM I have installed both the mergerfs and the unionfilesystem plugin. Looking at the options this has changed between OMV4 and OMV5.
In OMV4 one of the options was direct_io in OMV5 that has been changed to cache.files=off look at this section from mergerfs on github it may help, because to get this work cache.files=off may have to changed, there is a lot of information on that page but there is an answer.
I have not amended my setup, I have installed an additional drive (a small 2.5") purely for docker container configs, this prevents the problems you are seeing.
So my Emby config is on /srv/dev-disk/by-label-Docker/AppData/Emby and this works! all the shares point to the fuse mount point.
TBH I saw your thread re raid, as far as I am concerned if someone wants to use raid that's fine, but a user needs to understand it, or rather understand mdadm.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!